Forum Discussion
davidcole
13 years agoOccasional Contributor
yeah essentially.
We have two web methods, a search and a retrieval - and they are called with different parameters depending on the type of document you want to return - a statement or a credit card statement.
The first step of my test case choose a random number between 1 and 100 - 60 and below will call the Search Statements Test Case, 60 to 40 will call the Search Credit Cards test case.
Then the search Statements (and credit cards test cases) is to select 100 records from the relevant table in the DB, then perform a search, then as there is one expected result with is retrieved.
With this config, I can't use the dataloop at the end of the search statement and it just stays in that test case. So I was hoping that it would pass through the statement test case, then next time the statements test case would be used that the dataset would be reused...
I think, I may have to set something else up which depending on the environment, read from the database to a known CSV file....then use the CSV file as part of the test cases. Then I'd only have to change CSV file on change on environment.
We have two web methods, a search and a retrieval - and they are called with different parameters depending on the type of document you want to return - a statement or a credit card statement.
The first step of my test case choose a random number between 1 and 100 - 60 and below will call the Search Statements Test Case, 60 to 40 will call the Search Credit Cards test case.
Then the search Statements (and credit cards test cases) is to select 100 records from the relevant table in the DB, then perform a search, then as there is one expected result with is retrieved.
With this config, I can't use the dataloop at the end of the search statement and it just stays in that test case. So I was hoping that it would pass through the statement test case, then next time the statements test case would be used that the dataset would be reused...
I think, I may have to set something else up which depending on the environment, read from the database to a known CSV file....then use the CSV file as part of the test cases. Then I'd only have to change CSV file on change on environment.