This project is read-only.

BVT Tear Down Test Case


Under BVT have a Tear Down Test case - test.
This will remove all websites and database from all tests.
SCENARIO - Test case was stopped and no cleanup took place. Run this "test" and it will clean everything up for next run.


jnurse wrote Aug 30, 2010 at 4:43 PM

After further consideration, I'm not entirely sure adding this "tear down" test is the best idea. This is an extremely destructive test case.

Tests shouldn't be stopped manually as it will cause this error. If a test fails and the tear down is not run we will most likely want to further investigate the website to discover the problem. In which case we will need to look at the website folder and database that the test was run on.

Also there would be no easy way of specifying which test to clean up so instead all the website files and databases from all the BVTs run will be deleted.

nukealexs wrote Aug 30, 2010 at 5:09 PM

I would say there is a use case - test may be stopped manually regardless of what "should" or "shouldn't". Agreed you need to find out why test case failed - but if the issue is immediately identified the test case may want to be ran again straight away.
We need a "reset" button or something that does a cleanup.... Whatever way it is - or get this clearly documented for each case on how to do it (with right folder paths etc).

nukealexs wrote Aug 30, 2010 at 5:13 PM

Also please bare in mind what happens if 100's of test cases fail? Need some way of click cleanup.... Perhaps even an MS DOS batch file - something,.

jnurse wrote Aug 30, 2010 at 5:48 PM

It seems like the best option then would be to create some sort of script that will handle the clean up. Creating a test that runs a cleanup only would be inappropriate as it doesn't test anything to do with the product.

wrote Feb 2, 2013 at 5:09 AM