Inovalon-Tester
New Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
How to make an action apply to more than a single test case.
I've created two hundred test cases before I found out that the default test case option is to stop the test case if any step fails. That's the opposite of what I want. I can set a new default behavior for any new test cases I create, but what about the two hundred I already have? I tried selecting multiple test cases and setting the option, but it only affects one test case. Do I really have to select two hundred test cases individually and manually set the option for each? There isn't even a way to use the keyboard to go to the next test case once you've clicked on the options button for a single test case. So I have to click a test case, causing it to expand, then click the option button, set it to not break on error, go back to the test case list, scroll it up because the expanded current test case has moved the next case out of the scroll window, click on the next test case, causing it to expand, 200 times? This tool is supposed to be saving me time, not forcing me to do the same thing again and again affecting one test case at a time. Is there any way to set the test case properties of more than one test case to the same value in a single operation? Seriously, this has become less about designing test cases and more about fighting a UI that doesn't seem to be able to manage collections except one at a time.Solved829Views0likes2CommentsClone Assertions UI needs some love
1) Change the Target Test Case selection from a drop-down single-selection list box to a sub-dialogue that allows multiple Test Cases to be selected and test steps to be selected for each test case. 70% of the time I spend in ReadyAPI is repetitive data entry of cloning assertions one at a time between test cases where the default test case is the one I'm using for the source. 2) Change the default selection of the Assertions from none selected to all selected. No one ever needs none cloned, that's a non-operation.475Views2likes0CommentsAssertions tab always minimized - undesired behavior
When I open a test step in ReadyAPI, the assertions tab is always minimized. Most of the time that I am going through multiple test steps in sequence, it's to examine the assertions. Every test step, I need to go to the bottom of the screen and expand the assertions tab which is auto-minimized when a test step is first opened in a session. Where is the option setting to start the assertions tab maximized when a test step is opened, or the option setting to have the behavior be "sticky" and open a test step with the assertion tab in the same state as the last test step that was examined?414Views0likes0Comments