Forum Discussion
I've been in the same situation before. The test items are immutable once you hit the "Run" button. The best thing you can do is code around the tests that may not be able to execute under certain configurations and just put a note in the log stating such.
This is why, as convenient as it is for constructing a suite of test cases quickly, I don't like using "Test Items" as the primary driver for what gets executed. You can't dynamically change things in code. Using an SQL data table, Excel spreadsheet, or CSV file to indicate the list of tests to execute is actually very flexible because then all you need to do is alter the file and click "run"... then your tests run. You could even have multiple copies of the file and, depending upon the configuration to run, you just drop in the necessary file or even have your code retrieve the file.
In very high level pseudo code, it could be something like this:
If configuration = US, then file_name = "US Test cases"
if configuration = Germany, then file_name = "Germany test cases"
ExecuteTests(file_name)
Related Content
- 10 years ago
- 11 months ago
Recent Discussions
- 4 hours ago
- 5 hours ago