High-Quality GUI Testing
High-Quality GUI Testing
Test Framework is an Embedded Wizard add-on allowing implementation and execution of different GUI tests, such as Regression, Integration, Acceptance and Automated unit tests.
No additional tool required - develop and test within Embedded Wizard IDE
Your GUI works properly after every change. The test results tell you if not
Animation support included
Less effort - integration within automated test systems possible
Goal: Fixing a bug should never introduce several newer ones... at least you should get noticed.
Description: While the source code grows, you have to do some test cases every time you change something to make sure you didn‘t break anything else.
Example: When you have changed a UI component on the main screen, suddenly another component on any sub screen stopped working properly. Without a regression test, this issue may remain undetected for a long time.
Result: After a component was changed, side effects will be shown immediately and can be fixed.
Goal: A GUI is generally a part of a more complex system as it responds to incoming data as well as sends data back in the specified format.
Description: Stand-alone components must also work properly in the context of the system, like a GUI together with a MW.
Example: The GUI reflects changes after a change of the data which should come from MW side. Eg. Changed temperature value.
Result: The MW interaction is simulated by the test to verify the resulting behavior of the GUI component.
Goal: Test if all requirements of a specification are met.
Description: This end-user focused test should lead to results that users expect.
Example: If a specific button was pressed, the correct screen should open. These tests can be generated by everyone with the integrated Point-and-Click Test Recorder.
Result: The component works the way users expect it to.
Goal: Ensure all actual values correspond the expected values in a component.
Description: Logic tests of classes, functions/methods to show code level correctness.
Example: If you turn the wheel of a roulette with the same power, friction and the same starting position, the result must be the same.
Result: The functionality of a component works as expected.
A test creates an original screenshot and two more if there are differences.
A test creates the screen status, which describes the screen and allowss you to see changes immediately.
Record and log your manual testing, including every touch and keystroke. Then replay this sequence of UI actions to test them.
Define your tests by coding the test sequence with all required data/user input possibilities. The coded tests can be learned to get golden device samples for all further test phases.
For a lot of project scenarios it is vital to test the GUI part independently from the underlying middleware, especially if the middleware or the related hardware is not available yet.
By testing your GUI regularly, you can detect problems or inconsistencies early on in the process and act accordingly. It is recommended to do this before committing or at the end of the day via an automated test systems like Jenkins:
Sorry, item "sidearea" does not exist.