Allow additional values for 'Automation Status' field
Manjunatha Reddy
Users should have the ability to add custom values to the “Automation Status” field in the workspace settings, similar to other system fields. Currently, this field is restricted, which limits flexibility in categorizing test cases.
One possible reason for why this field's values are not customizable is that it's used in dashboards widgets and also, results reported via API also influence the fields status for the test case.
New values for the field requested so far:
- A 'none' value for those cases that are not meant to be automated. (complex scenarios, tests that change often etc).
- A 'Maintenance required' value for those cases that need to be modified because of a change in the component being tested.
Manjunatha Reddy
Merged in a post:
Add Automation "None" state
Nataliia Chukhrai
When adding new test case it is marked as "Not automated" (we use it to mark test cases which we are not planning to automate and they will be left for manual part).
Would be nice to have some neutral Automation state, like NONE or some similar, so that we could distinguish between newly created test case, which doesn't have Automation state indicated yet and the one, we are not planning to automate at all.
M
Mark George
Adding support for this. We are also in need of an additional value for the Automation Status field to indicate test cases we do not intend to automate. We need differentiation between Not Automated (But planned) and Will Not Be Automated.