3.29.7 My Test Suite failed
If your test fails, you can find exact details about the problem by looking at the Test Result View 3.26. A screenshot of the AUT is automatically taken when an error occurs and can be seen in the Image View .
For other problems with test execution, check:
- That the AUT is in focus and is visible. You can automatically activate the AUT in the AUT properties 3.7.1 or you can use a Test Case to activate the AUT . You can also set your preferences to minimize Jubula when test execution begins 3.27.
||Bear in mind that different platforms have different focus behavior. You may need to specifically bring the AUT into focus by clicking into it as a part of the test.
- That the AUT is ready when the test begins. To ensure this, you can insert a Test Case at the beginning of each test which waits for the window or for the first component you want to test. This is especially important when you are running tests from the command line with the Test Executor.
||Waiting for a window to appear is generally a good idea whenever a new window or dialog is opened during the test. Waiting for the window or the component you want to test will make sure that your tests run even under different timing conditions.
- Make sure that the Test Cases and Test Steps are in the right order.
- Ensure that the data you have entered is correct.
- Check your object mapping configuration 18.104.22.168. We recommend that you set the recognition to "standard".
- If the AUT is an RCP application, make sure that the keyboard layout is correct 3.7.1. Otherwise, make sure you have the current version of the RCP Remote Control plugin (start your application with -clean to be sure).
- Check that the Test Steps preceding the failed Test Step were successful by looking at the state of the application.
||To help you analyze the reasons for Test Suite failure, you can use the pause on error option 3.19.4.
Copyright BREDEX GmbH 2013. Made available under the Eclipse Public License v1.0.