Test Step sorting by menu instead of drag-and-drop
We encounter a lot of frustrations with how sorting is done in Zephyr Enterprise. The responsiveness of the application is often terrible. When we need to change the order of our test steps, the only option is to drag-and-drop. The problem is when the UI is not responsive, or the performance is bad, it's frustratingly difficult to move the step more than one position at a time. Often the step is dropped at some random location due to a glitch in the connection to the server (which we then see that frustrating blue status loading bar at the top of the screen - why is the page I'm on constantly reloading anyway?). I have had to assign my Steps a step number so I can see when something is dropped in the wrong position, and then after I finally get the step where I want it, I need to edit all of my steps with the new order numbers. I'd like to see a better implementation for moving / changing the order of test steps. Jira has a nice implementation for changing the order of options on things like custom field parameters. They have "Order" buttons that allow you to move the selection up/down one position, or move it all the way to the top/bottom; and there is a "Move To Position" button so you can select exactly where you want the selections to be in the list.
Add features to collapse and preview test steps in Test Execution
When working with a test step with a lot of text or images, it creates a really long test case. It would helpful to limit the vertical size, and add an option to click to expand (adding wrapping and truncation). It would also be helpful to be able to click the image within the test step to launch the image preview. currently you have to leave the test step and scroll the bottom of the test case, preview the image, close it, then scroll back up to the test step to update the exeuction status.Make the UI more intuitive for the copy/paste options for test steps
The UI is not very intuitive when it comes to copy/pasting test steps. The top button pastes to the bottom, however you don't really know that unless you're used to it or you hover over the button. The option to paste above only exists on the test step, however you don't really know this unless you hover over the button. It would be helpful to also have the option to paste at the bottom on the test step as well.
Import new Test Steps section (Test Steps, Test Data, and Expected Results) to an existing Test Case
The user should be able to create an Import map and file to load new Test Steps (at least Test Steps, Test Data, and Excepted results) to a pre-existing Test Case in the Test Repository. Maybe by using the Test Case Id as a unique identifier for the Import processing.Better Support of Test Data Sets in Test Script
I'm going to describe a problem I'm having when utilizing Test Data sets. Example: Test Data Set - Bikes Types - 8 Total # of Steps in Test Script - 4 Steps 1 and 2 utilize the Bike Types test data set. Steps 3 and 4 do not. When this test script is executed, the following is created. 8 sets of tests with 4 steps each. Steps 1 and 2 are repeated 8 times, which is fine because I want them to repeat 8 times, each time with a different Bike Type value. Steps 3 and 4 are also repeated 8 times. This is not an ideal situation since I only want Step 3 and 4 tested once. Because of this I end up having 14 additional tests created unnecessarily. Ideally, when the Test Script is executed, Steps 1 and 2 are repeated enough times to exhaust N number of values in the Test Data set it's utilizing, Steps 3 and 4 are only printed once because they do not have a Test Data set associated with them. The way our organization sets up a Zephyr Scale Test Case, we want to have all tests for one story included in one Test Script. Is it possible for test data sets to only be executed against Steps that include them? And not against every single step, regardless of if it is using a Test Data set or not? Additionally, this gets even more complicated if you have multiple sets of test data. Example: Test Data Set 1 - Bikes Types - 8 Total Test Data Set 2 - Paint Color - 4 Total # of Steps in Test Script - 4 Steps 1 and 2 utilize only the Bike Types test data set. Steps 3 and 4 utilize only the Paint Color test data set. When the test script is executed, it creates 8 sets of tests. Steps 1 and 2 are repeated 8 times, to exhaust the total number of values in the Bike Types test data set, this is expected and wanted. Steps 3 and 4 are also repeated 8 times. This is not expected and unwanted. Unfortunately, sets 5-8 will repeat Steps 3 and 4 and will create nonsense tests, since they're basing the number of repetitions on Test Data Set 1, and not Test Data Set 2. i.e. once you reach the 5th set of tests, you're going to have a test created with something like "Count the number of bikes with PAINT COLOR" for steps 3 and 4, since there are only 4 values in the Paint Color data set. The way that Zephyr Scale prints out the test sets, it's expecting 8 values. This is only an example. This gets exponentially more complicated the more test sets you utilize. Additionally, if you attempt to create a Step that utilizes more than one set of test data, this falls apart very quickly, as it only prints the values sequentially instead of creating an actual test matrix. i.e. using the above examples, if I wanted a test step that was like "Count the number of {Bike Types} with {Paint Color}" I'm only going to get 8 tests created in the execution, and it will just print out ; Bike Type 1, Paint Color 1 Bike Type 2, Paint Color 2 Bike Type 3, Paint Color 3 Bike Type 4, Paint Color 4 Bike Type 5, Paint Color X (expecting a 5th value that doesn't exist since inheriting number of rows from Bike Type data set.) Bike Type 6, Paint Color X (expecting a 6th value that doesn't exist since inheriting number of rows from Bike Type data set.) Bike Type 7, Paint Color X (expecting a 7th value that doesn't exist since inheriting number of rows from Bike Type data set.) Bike Type 8, Paint Color X (expecting an 8th value that doesn't exist since inheriting number of rows from Bike Type data set.) This isn't expected nor is it ideal. In a perfect world, the steps of the test script would be printed out like this instead. Bike Type 1, Paint Color 1 Bike Type 1, Paint Color 2 Bike Type 1, Paint Color 3 Bike Type 1, Paint Color 4 Bike Type 2, Paint Color 1 Bike Type 2, Paint Color 2 Bike Type 2, Paint Color 3 Bike Type 2, Paint Color 4 etc etc. My expectation was that a test matrix would be created utilizing all combinations of the test data sets, not the way it's currently being created. Some feedback/advice on this would be great. We had certain assumptions on how "smart" test data sets would be utilized in regards to test scripts/test steps, and so far support around test data sets seems to be extremely limited to only super basic uses.Can I make the test details text area fields bigger?
Hi all, I use Zephyr Squad 4.6.3 on Jira 7.13. When filling out test steps for a test, the "Test Details" section is quite small, and the text areas where I enter step information (test steps, test data, and expected results) are even smaller. I need to do a lot of mouse scrolling to read or update these fields, especially if I include a Jira "noformat" section. Below is a screenshot from my browser, showing the test details area highlighted in a blue rectangle. You can see that relative to the page itself, the area where I spend much of my time is quite small: I recently discovered the "Large View" icon, which does make the Test Details area bigger, but, disappointingly, not by much. Here's as screenshot of the same page from above, where the white rectangular area is the "Large View" overlay: While an improvement over the default view, it's still quite cramped, and I find myself still needing to do a lot of horizontal scrolling. Is there a better way? How do other people deal with this issue? Am I doing something wrong, or could it be that something in JIRA is causing the test details to be rendered unexpectedly small? Is there a different tool I could use to update test steps without using a browser, or perhaps a different way to edit or read test steps? I would love to hear if others have experienced this, and if so, how to make it easier to work with test steps. Thank-you! Little-Acorn
