Test Case & Issue (Bug) Reporting System

Explore

Hey everyone!

ā€‹

Software testing/quality analysis is important to record what you and your colleagues are checking, what worked and what didn't, how to reproduce issues and how to invite others to contribute errors that they discover.

ā€‹

This is an easy-to-use Test Case and Issue Log reporting system which provides all that and more. There's five tables:

  1. Test Cases- the themed high-level tests.
  2. Test Case steps- each test case will have a set of steps which defines the detail of what and how you're testing (links upwards to test cases).
  3. Run History- to record when the team have run the steps and and what the outcomes were (links upwards to steps).
  4. Issue Log- to make a note of issues (bugs), how to reproduce and when they're fixed.
  5. Team members- to assign people against test cases, steps, runs and issues.

ā€‹

Once issues are marked by developers as resolved then the steps can be re-run to verify.

ā€‹

Each table has multiple grid and kanban views based on the statuses, plus each table has a form to make entering items simpler for those who won't edit a table directly. For example, the Issue Log Reporting form can be shared publicly, so your users can submit items straight into the base for assignment to a team member and investigation.

ā€‹

The base is populated with some examples to show how it can be used and all the fields are completely customisable. This is fully functional on a free plan, but for those on a paid plan you can add charts and KPIs to track issue reporting and resolution over time.

ā€‹

ā€‹

ā€‹

ā€‹

Explore
Updated July 22, 2020 at 7:01 PM
Copied 428 times

Neil Rowlands

Data analyst and software tester
Explore the base
Grid view
Grid: Status = Inactive āœ–ļø
Grid: Status = Under Development āž–
Grid: Status = Under Development āž– copy
Kanban by Status
Grid: All items
Grid: Test Case Status = In Use āœ”ļø
Grid: Test Case Status = Under development āž–
Grid: Test Case Status = Inactive āœ–ļø
Grid: Step In Use = āœ”ļø
Grid: All items
Grid: Outcome = Pass āœ”ļø
Grid: Outcome = Undetermined āž–
Grid: Outcome = Failed āœ–ļø
Calendar by Run Date
Kanban by Outcome
Grid view
Grid: Severity = 1 Minimal
Grid: Severity = 3 Medium
Grid: Severity = 4 High
Grid: Severity = 5 Critical
Grid: Severity = 2 Low
Kanban by Status
Kanban by Severity
Kanban by Priority to fix
Calendar by Date Found
Calendar by Date Passed
Grid view