Search, vote, comment and create ideas for Zephyr Scale improvements here. For more information on our review process, see here.
*As a* user
*I want to* be able to set any field as mandatory,
*so that i can* make sure my team fills every field properly
I would like to have this feature include the ability to have the text entered into mandatory fields labeled and displayed at the top of the test execution. This would allow any user, manager, etc. to quickly see the mandatory data that was created/validated during test execution. Many of our organizations test cases have a large number of test steps, and having to scroll through them to find relevant information is clunky at best. Being able to export this data for each test in a cycle into a spreadsheet would be beneficial as well.
When using the "Set all below to Pass" feature on a test step, it should stop and center the screen at the next mandatory field, prompting the user to enter the data into the mandatory field.
There is a great opportunity to tie this feature in with this one here https://zephyr-scale-server-dc.ideas.aha.io/ideas/TM4JS-I-95. Being able to set a mandatory field in a test step as a parameter for proceeding test steps would provide an excellent improvement in test case execution and options for test case creation.
I hope this feature request includes Custom fileds and Execution screens? (like executing Test Cyle)
Ability to make any field mandatory is good practice and help to have correct test data. People are just people but not robots you know... :)
We particularly need to have Environment field mandatory during Test Cycle run
We vitally need to set up environment mandatory :( during run, And it is obvious - if field is not mandatory - less than 50% will fill it despite all reminders and rules...
Test cases by status) which gives us bagel-report with information of test cases in each status visit more: Bangladesh Mobile Phones and mobile mall pk
My team is also asking for this feature, in order to ensure our Test Execution metadata is correct. Examples of fields I want to make required for a test execution are:
Version (base field)
In our case also specifically for test execution where it is currently impossible to set any field to required
AS a user, firstname.lastname@example.org, I want to set any fields mandatory so that iican make sure my team fills every field properly.
You won't be notified about changes to this idea.