GUI Testing As a Kind Of Automated Testing

GUI Testing As a Kind Of Automated Testing
March 22 10:00 2013 Print This Article

What is it possible to expect from automated testing? Automated testing is always a guarantee of regular and consistent performance of testing and high testing results.

Graphical user interface testing (GUI) as a kind of automated testing is the process of testing a product’s graphical user interface to ensure it meets its written specifications. This is normally performed by using test scripts.

Is it possible to automate the GUI testing process with the help of current testing techniques? No, this process expects interaction between test engineer and GUI.

Test engineer often should record script and after the detection of bug, the process fails and the script recording process should be started from the very beginning.

As far as you understood, GUI testing expects the detection of bugs through manual script recording. But after the detection of all possible bugs, scripts will be ready to be executed.

Would not it be better if there was testing tool that could effectively find all GUI components? It would be great but for now it is not possible. There is no tool that could conduct an active survey for the existing GUI component of any application and use generated data to drive the test script generation and execution.

To find all possible bugs in the application, one created test script should be able to test against many test data sheets. Only then it will be possible to tell that software testing company has performed high-quality automated testing.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles
  • http://www.prism-informatics.com Michael Schleier

    Automated testing is a wide area. So a general answer regarding the approach an the best practice in GUI testing is not easy and can not be given.
    For example the identification of GUI elements IS possible for some GUIs, for example for SAP. There SAP provides the TAO tool and the component based testing approach. Here are not only the GUI elements identified, but also auto-correction methods are provided.
    On the other hand the approach of one test script covering a wide area of datasets is a good approach for automated testing of unit tests, but it is not a valid approach for GUI testing. Test scripts covering vast amount of test data would in this case not focus on the business process, the main benefit in GUI-level testing.
    When performing GUI level tests the approach to use more modular test scripts with a defined scope for each script and plugged together for business process testing is the better approach. We, as a software testing company, have performed many test automation projects with this approach. More than that we also have case and ROI studies, which could prove the success of this approach,

    Regards,

    Michael Schleier