RSS Feed

Axe Test Automation Platform

I need to create some clean-up and clean-down scripts that but I don't want to include these results into the actual test script results.
Is there anyway to exclude tests from producing results as these clean scripts are likely to fail?
I know I could create some custom/baseline scripts to do this but would still like to have these clean scripts as part of the test suite.
I was thinging maybe a dependancy flag of 'ignore'
Any ideas
Russ

Hi Russ,

I am not sure I fully understand the requirement. Surely even if the tests were setup/teardown tests you would need to validate the results? e.g. if a setup test failed then couldnt it have and adverse effect on the rest of the test run? So even though these tests are not formal test cases as such, they are still integral to the test run and would need to be reported on, especially for diagnosing any failures.

If you are using Axe with a test management tool then I guess one option would be to not import the results from these tests?

Another option would be to have separate Run tables for the setup/main/teardown tests. You could then kick off the three runs from a batch file. This would leave you with three separate sets of results.

Sam

Sam,

I didn't make very clear so here is an example, I hope

The system test (a number of test runs) run sets up some data (creates some user accounts) but failed to complete for some reason. Now the user accounts are left over but there is No way the data can be reset (revert snapshot) without a lot of hassle. So a clean-up is used to clean down the user accounts which passes ok. If the previous test run works ok and creates the accounts and then deletes them at the end then the clean up scripts will now fail because user accounts don't exist.
These are the scripts I would like to have set-up in the results as ignored.

Could I put some code in the AxeResult action map to make it skip these flagged tests?

Russ

Hi Russel,

So wouldnt the suggestions of three separate Runs work? ie.

Run1 - Setup
Run2 - run all main tests
Run3 - Teardown

That way Run2 only contains results for the tests cases themselves, but you can still view results files for Run1 and Run3 if you need to diagnose suspected problems with the test environments etc.

Sam