Here is a brief description what happens when running tests using my test automation framework (and some future plans).
Each test suite has one or more test scenarios which has one or more test cases.
When running test suites, a unique test run is created which has one or more test case execution queues.
All data is in a MS SQL Server database.
In automation GUI:
1. Select run mode, New or Resume (If resume select a test run which is not completed).
2. Select one or more test suites if New.
3. For each test suite select test level, test days duration, test environment and test tool if New.
4. For each test tool instance, select global run options like reporting, e-mail etc.
5. Press run button for each test tool instance which is not aleady running.
6. Test run is started for each test tool instance via Scheduled tasks.
For each test tool:
7a. Execute each test case in queue until all is executed or cancelled (could happen if a prevoius nested test case fails).
In test run report GUI:
7b. Follow test run progress during run-time (now also reporting at step basis).
In test case dashboard GUI:
7c. Latest test case result are shown during run-time for each version och configuration.
Parallel execution is not implemented (you cannot use multiple test tool instances for a test run in order to decrease test execution time).
TestBatchRunner (home made tool for running java batch jobs)
TestAPIRunner (home made tool for Web Service, XML API and http requests)
Implement support for more tools (thinking of trying Selenium).
Learn Java and OO (natural language choice since our AUT is written in Java and allowing for more collaboration with Development).
Test in peace | A place to put my testing thoughts. I'm Hannes Lindblom, a software tester based in Sweden. Twitter handle: @hanneslindblom.
SWET8 – books, videos and other stuff - In my last blog post I tried to summarize the SWET8 conference as a whole. One thing I omitted on purpose was all the great pointers to books and other sou...
1 day ago