You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Out of all manual test management tools out there here is a cool way to manage your manual test cases with confluence. 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.
For a single test plan here I have used a page tree. As on above example this is a test plan created to use in JIRA version upgrade.
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.
Under that the test cases are divided based on assignee. But the logic to divide/list test cases could be defined as your wish.
Under each assignee there are test cases that are allocated to each tester.
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.
Inside single test case page, there are two tables. The first table contain general information about the test case. And that table is included inside a page property macro to use some information in summary results pages.
The other table contains test steps and results. Also you may noticed results section has 2 separate columns; by adding check boxes (tasks) it is easier for testers to mark step results. So that testers have to edit the page only once just to enter final results for the test case.
Parent page for each tester contains summery results of test cases that are allocated to that specific tester. It is really easy to find out test allocations and results using this page. Content to this page is generated through Page property report which extracts information from single test case pages.
As same as Assignee summary page; summary page (parent page of entire test plan) contains results summary which generates information through page property reports macro. To get a quick overview a chart macro is included there. Best thing about this is that testers do not need to spend time after testing to collect results and generate reports; the report generates automatically every time a tester updates test results for a single test case.
A separate page tree inside main page tree for the test plan is created to include test detail information pages. Inside this page tree Pre/Post task list info, task and time plan, test analytics, test approach information and traceability matrix sections are included in separate pages.
Also an instructions page for testers are included inside the test plan page tree. I usually takes help from my other team mates who are not Testers. It is easier this way to provide instructions in a page so that they don’t want to chase me to ask how to use this test plan 😊
We usually use some of our test plans over and over again. Since our manual test plans are now migrated to Confluence it is super easy to update test cases.
As I said before we use the same test case multiple times. Therefore it is very important to keep track on previous test attempts. To achieve this; we could use a confluence page. Executed date, final results and remarks can be enter.
Hope this way of managing your manual test cases gave you a boost and you are welcome to explore on your own and develop this concept J