Community
Participate
Working Groups
[Test Automation] Automate manual test suites using the Automated GUI Recorder. This defect is for the sustaining work required in TPTP for automating the manual test suites using the Automated GUI Recorder for the following test projects: test-results\test\org.eclipse.hyades.test.ui.logViewer.tests
Reassigning to me to be completed with the Manual Test automation.
4.4 is complete. Re-targeting to 4.4.0.1.
This defect is not stop-ship for 4.4.0.1; decreasing priority.
Retargeting to 4.4.1 to allow 4.4.0.1 Test Project resources to be allocating throughout the other sub-project to complete the patch release.
Deferring to 4.5 to smoke test 4.4.1 in preparation for 4.4.1 TP1.
Bulk update of the target field to reflect the change in iteration numbers.
Also, add the following manual tests to the Test Log Viewer manual test suite (for documentation purposes) and automate: 1) Add the following manual tests to the Test Log Viewer manual test suite and automate: File Output: 1. Create a General Project. Select File -> New -> Project -> General -> Project. Enter a name for the project: 'my_logs_project'. Click on Finish. 2. Run a junit test by right click on the test-suite, select "Open Run Dialog". In the "Create, manage and run configurations" dialog, create a test configuration. In the "Test log" tab deselect "Use Defaults" Select "Defer model Loading of Test Results" Enter a name for the Test Log eg. 'myJunit-execution-result' For the location, Select the project "my_logs_project" (created in step 1). 3. Click on "Apply" and then "Run". 4. Check to see that "my_logs_project" folder is empty (I am not sure on this one. Please confirm). 5. Check the workspace folder in the file system that two files named "myJunit-execution-result" and 'myJunit-execution-result.testlog' exist in the folder "my_logs_project". Generate_TestLog: 1. Switch to Test Perspective. 2. Create a General Project. Select File -> New -> Project -> General -> Project. Enter a name for the project: 'Logs_project'. Click on Finish. 3. Run a junit test by right click on the test-suite, select "Open Run Dialog". In the "Create, manage and run configurations" dialog, create a test configuration. In the "Test log" tab deselect "Use Defaults" Select "Defer model Loading of Test Results" Enter a name for the Test Log eg. 'myJunit-result' For the location, Select the project "Logs_project" (created in step 1). 4. Check that the file "'myJunit-result.testlog" is present. 5 . Double click on the file and see that the text file (XML) begins with a <EXECUTION> and ends with a </EXECUTION>. Check for the correct number of invocation and verdict events (e.g. if you have five invocations in your test suite, you should have five <invocationEvent> and six <verdictEvent> events - five invocations verdicts and one arbitrated test suite verdict). Import_TestLog: Switch to the Test Perspective. 1. Select File -> Import -> Test Log file. 2. Click the browse button and point to the file generated in the manual test Generate-TestLog. 3. Click the second Browse button and point to the testsuite which was run to generate the above testlog file. 4. Enter the project name 'Logs_project' in 'Enter and select the parent folder' (or any folder name where you wish to import the file) and enter the log file name 'my_logs_file' and click on finish. 5. Check that the testlog file appears in the specified folder. 6. Double click the file and check that it opens using the Test Log Viewer editor. Scalability: 1. Run the TestLogGenerator Junit Test with 5 iterations, 10 iterations and 15 iterations. 2. Run the above regression tests on these logs. Performance & memory: 1. Start eclipse. 2. Measure the current memory consumption and current time. 3. Import a testlog. 4. Double click on the teslog and open it. 5. Measure the memory usage and time. Repeat this with different size testlogs.
New manual and automated test suites checked into CVS (HEAD).
Verified in TPTP-4.5.0-200712160400. Closing.
Worked 40 hours on this defect.
Updating hours worked.
