Testing Tools

What the team checks before it ships. A test case is one scripted check numbered within the project (CRM-TC-45): what it proves, what must be true before it starts, its kind and priority, whether a person or a script runs it and which test in the automation suite, how long it takes, who owns it, the data and environment it needs, its status from draft through review to active or deprecated, the last result a run gave it, and its steps, each with what the tester does, what should happen and the data it uses; every save keeps a version, steps included. Suites are the folders the cases are filed in, nested by area and then by screen or flow. These tools read the suites as a flat tree (list_test_suites), read the cases with their filters (list_test_cases) and one case with its steps (get_test_case), write a case as a draft with its steps (create_test_case_draft), change a case or its steps or move it where the lifecycle allows by hand (update_test_case) and remove one after the person confirms (delete_test_case); a case reaches review and active through submit_for_review, and the suites are shaped by people. Plans, runs, results, defects and the traceability matrix join as the module grows.

ToolsCopy Anchor Link