Best practices | TestCases | Progress
All TestCases have a property called TestCaseWorkState, and we strongly recommend that you use it to track your progress. Especially in team environments.
![]() |
If your project uses pre-execution approval, you can't change the TestCaseWorkState. Tosca does this automatically, depending on where your TestCase is in the approval process. |
Understand why it's so important
Tracking your progress is extremely important, for several reasons:
-
It makes progress visible to your team, which lets you better organize, prioritize, and report on your efforts.
-
It ensures that Requirements show the correct test coverage. All TestCaseWorkState property values translate to a specific coverage percentage. When you check the state of your project, this tells you how far along the tests are that cover your biggest business risks.
-
It makes open items easier to track, especially in projects with messy folder structures. You can use Tosca's TQL search to find TestCases with a particular state. For example, to find all new TestCases that still need designing, use the search query =>SUBPARTS:TestCase[TestCaseWorkState=="PLANNED"].
Track your progress
Every new TestCase starts off with the TestCaseWorkState as PLANNED. Make sure to change the property value as you go along:
-
Set it to IN_WORK when you start working on the TestCase.
-
Set it to COMPLETED once you're done. Typically, you're done when the TestCase is finished enough to become part of a larger test set in an ExecutionList.
What's next
If you haven't yet, check out our other best practices articles.