Extend test execution related information
To support a continuous risk-based test strategy, hereby requesting the following custom fields and possibilities to be added: -Possibility to add Build Number to an individual test case execution. Hence looking at Execution History will list Status history with associated Build Numbers. -Possibility to filter on Build Number -Possibility to sort on Executed On (I e sort on execution date)
Add test progress to Test Execution
When Test Planning is viewed, the user is able to see the execution progress in each folder/ sub folder. It would be really useful if Test Execution would also be able to show this kind of progress. Due to the complex nature of our folder structures within projects, the colour breakdown of test status is a really useful way for us to track where we have outstanding test cases that need to be completed. This change would be a very useful tool rather than having to navigate to test planning to see this information and then back to test execution to carry out the test cases.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.Lock Test Cycles and Phases to disable executions
As a test lead, I need to be able to lock or disable test cycles and phases so testers can no longer execute test cases or update their statuses. Currently, we only have the ability to Hide/Unhide Test Cycles within releases. However, this does not block any further executions from happening, as you can still find the executions via search.
Possibility to order regarding Order ID in test execution
In test planning I have the possibility to order testcases regarding Order ID. But this ordering is not taken over to test execution, in case the test phase was created by "Create New". If creating a test phase from Repository both test planning and test execution have the same order. But not if using "Create New". We need to have the possibility to order testcases and execute them in the same order, independent of how to create a phase. For more details see case #00542683.
Test Execution|| We need a feature to see the attachment in list view
Test Execution|| We need a feature to see the attachment in list view. Currently, we see tiles with cut off file names where end user can not read full name of the attachment. So can we have another view of attachments in test case execution. It's quite hard to work with such view of files. Probably, we could have a list view with sorting options for them. Here are the steps- Go to Test Executions>>Open a test case which is either executed or needs to execute Go to Execution Attachment section. Add some attachment. In the attached screenshot, we can notice tiles with cut off file names where end user can't read the full name of the attachment
Create a test phase directly from repository folder
As a tester, I get a story (requirement\new feature) to test, then: 1. I begin to design the test cases I going to run and build the test tree under the repository. 2. Map the testing to the requirement. 3. Open a test phase under the test cycle for this story. 4. Move to test execution to run the test phase. I want the option to create test phase directly from the repository folder. Furthermore, I usually, during the test execution, think of more scenarios to test, and I need to go the whole process again from 1-4 for the new scenarios. I want the option to run the test case as part of the phase, from the test case in the repository level.
Edit Test Case button always displayed on Test Execution panel
I’m executing a lengthy test script and I’m updating it at the same time. I find myself regularly pressing the Top button to access the Edit Test Case button, making then saving an edit, and then having to scroll back to the individual steps. I suggest making this button easier access by having it always visible on the interface.
