Make QA test cases public

[jpye-finch]

Description

Full traceability from requirements to test cases (manual / automated E2E / performance) and scenarios
Full test coverage showing the test cycles and cases fully run
Defect reports showing:
the number of defects that have been found and their severity
the number of defects that remain open (not fixed) and their severity
Test cases made publicly available for system integrators to use on their projects
We need to be able to trace from requirements through to specific test cases to ensure that we are testing all functionality (including configuration requirements, NFRs etc.), via epics, designs, user stories etc.
A test case is not static. It can be used for a number of scenarios, which together make up the full test coverage, well beyond positive and negative test cases.
We need to keep clear separation of testing from development i.e. we need to test the requirement and what was designed rather than what has been built.

Re: TestRail

• We can integrate testrail with github to identify which testcase are getting failed for which defect
• We can integrate testrail with playwright if we want our e2e reports through testrail. I dont think this is going to serve our purpose. In this case what can be done is, whenever any QA is updating or creating any testcase, they need to create a ticket mentioning to write e2e for that testcase.
• When any new testcase is added for any feature, those ticket can be placed in reference for that testcase
• For system integrators there is option to provide view only option

Full traceability from requirements to test cases (manual / automated E2E / performance) and scenarios
Full test coverage showing the test cycles and cases fully run
Defect reports showing:
the number of defects that have been found and their severity
the number of defects that remain open (not fixed) and their severity
Test cases made publicly available for system integrators to use on their projects
We need to be able to trace from requirements through to specific test cases to ensure that we are testing all functionality (including configuration requirements, NFRs etc.), via epics, designs, user stories etc.
A test case is not static. It can be used for a number of scenarios, which together make up the full test coverage, well beyond positive and negative test cases.
We need to keep clear separation of testing from development i.e. we need to test the requirement and what was designed rather than what has been built.