The GUI Approach to Automated Testing

Posted on

A graphics user interface (GUI) test focuses on testing the user-friendliness of a program, from the mouse click to access to menus. To put it simply, a single click should open up the menus and press buttons, while a mouse drag should move or highlight objects. While GUI testing is also concerned with how the buttons work, it’s also concerned with how they look.

There are three approaches to GUI testing. The statements below offer a simplified look at each approach.

Manual-Based Testing

As the name implies, manual-based GUI tests require testers to check the interface with their bare eyes. This is usually done in a single pass but has reliability issues.

One plus one is two.

Record and Replay

In record and replay, the testers record the testing process and review the footage to check the interface. This is more prevalent in automated testing systems.

One plus one is two. Playback confirms.

Model-Based Testing

Perhaps the most complex of all approaches, model-based testing requires testers to build a simulation of the program’s functionality, from input to output, to see how the program behaves. In the testing phase, testers can refer to the model to compare the model output and the actual output to determine bugs more effectively.

One plus one is two. Model confirms.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s