The other table contains test steps and results. And that table is included inside a page property macro to use some information in summary results pages. The first table contain general information about the test case. Inside single test case page, there are two tables. Instructions for testers and other details like, pre/post task list, task and time plan, test analytics, test approach and trace-ability matrix are available next. Under each assignee there are test cases that are allocated to each tester. But the logic to divide/list test cases could be defined as your wish. Under that the test cases are divided based on assignee. Parent page of this page tree contain a summary about the entire test plan which can be listed as Test case base test results at the moment, test results in a graphical view and common instructions to use the test plan. As on above example this is a test plan created to use in JIRA version upgrade.
In below structure you engage as many number of testers with your and generate final test results super-duper easily without outing effort after test execution.įor a single test plan here I have used a page tree. Out of all manual test management tools out there here is a cool way to manage your manual test cases with confluence.
0 kommentar(er)
