Forum Discussion
Hi vinniew
As you said, "delete the registered users after running the test or before you run the next iteration of tests." It's not possible when test cases
are running parallelly with CBT.
Take an Example:
Location City State
United States US US
This data is using by Chrome, Edge, Safari, Firefox Parallelly. Then it can be possible like anyone can save it first and then the script for other 3 browsers will fail because we have a validation there like: Location Can't be duplicate. So.......... Other 3 are getting failed. So, how can i handle that.
Please specify exact steps. I am trying it with table variable but i think i didn't reach to the exact path.
Also, unable to understand how can i use data generator?
Hi dikshika114
I think there is a misunderstanding.
I said to use 4 separate variable values/ Test Parameters.
This will ensure each test will use a different value
test1 - variable value 1 - parallel session 1
test2 - variable value 2 - parallel session 2
test 3 - variable value 3- parallel session 3
test 4- variable value 4- parallel session 4
With regards deleting from the data base, this is done in an iterative basis.
Either done prior to running a test, or after you run the test.
The key is when you run the test you will not be blocked from using that same variable/parameter again.
As mentioned before also would be a set variable value using a code expression mode
Using say reg ex or something similar you could add generate values to be added and avoiding the deleting from the DB but it means lots of test data in your DB.
Hope this clarifies any confusion on the approach I suggested
KR
Vincent
Related Content
Recent Discussions
- 2 days agovladd1