Status roll-ups for Test Cases, Scripts, and Test Logs now follow the defined mapping rules, ensuring each level reflects accurate execution outcomes and provides clear visibility into testing progress.
Test Case status now follows the defined rules, displaying Passed when all logs pass, Failed when any log fails, and Untested when any log remains not executed.
Script status now reflects actual execution, showing "Performed" when all logs finish, "Defect Found" when any log has a defect, "Active" when execution is ongoing, and "New" when no logs exist.
When creating an issue (defect), the priority now defaults to "Medium," providing a uniform starting priority for all new issues.
When a project SLA is defined, the Planned End Date auto-fills based on the SLA duration for each priority, with High and Critical potentially falling on the same day due to the eight-hour window.
When the Planned Start Date is changed, the Planned End Date is instantly recalculated using the SLA rules, ensuring timelines remain accurate without any manual intervention.
The "Assigned To" field is now optional across issue creation, edit, bulk edit, and when raising a defect in test logs, allowing users to proceed even when the assignment is yet to be planned.
The "Add Execution" button in the Test Case Wizard is now visible only to users with super access or designated stakeholders for that test case, ensuring execution can be added only by authorized roles.
Users can now download a structured Word document from the Test Case page that consolidates details, scripts, steps, logs, and defects in an organized hierarchy for faster review and audits.
Steps in the Test Log save instantly during navigation, ensuring smooth performance even when the log contains many steps and screenshots.
A refresh indicator confirms each step update, giving users instant reassurance that their changes are captured.
The discussions panel refreshes automatically, ensuring each test case displays its own conversation history accurately.
During script execution or log edits, valid changes save automatically when navigating across tabs, preserving all updates without requiring manual save actions.
Execution % reflects the proportion of test logs marked as Passed or Failed against total expected executions (Test Scripts × Stakeholders), offering a clear view of execution completeness.
Pass % reflects the proportion of Passed test logs against total expected executions (Test Scripts × Stakeholders), providing an accurate measure of overall test success.