bmgriner
12 years agoFrequent Contributor
Issue when cloning assertions in assertion test step
I created an assertion test step and I was pretty excited about it. Among other design and usability problems I found a bug when cloning the assertions. When I tried to change the source and field it failed to give me all of my options in the source drop down. I had to delete it and create another new assertion. Very tedious and time consuming. I can only imagine this was because I had a lot of steps in my test case.
Usability issues:
1. Where is my play button. I don't want to run the whole test case in order to see if the assertions passed or failed. If I rerun the appropriate steps that will cause the assertion test step to pass or fail, then I should be able to run the assertion test step and have it reflect that without running the whole test case.
2. I can't right click when doing contains comparison to allow me to choose test case or other properties to compare against. Thank goodness when I type them in manually they still work.
3. Didn't notice an equals, only a contains in the assertions list.
Usability issues:
1. Where is my play button. I don't want to run the whole test case in order to see if the assertions passed or failed. If I rerun the appropriate steps that will cause the assertion test step to pass or fail, then I should be able to run the assertion test step and have it reflect that without running the whole test case.
2. I can't right click when doing contains comparison to allow me to choose test case or other properties to compare against. Thank goodness when I type them in manually they still work.
3. Didn't notice an equals, only a contains in the assertions list.