github
/
developer-roadmap
mirror of https://github.com/kamranahmedse/developer-roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Roadmap to becoming a developer in 2022
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2460 Commits
198 Branches
4 Tags
425 MiB
 
 
 
 
 
Tag: Branch: Tree: 8990f0912a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '8990f0912a'
${ noResults }
developer-roadmap/content/roadmaps/113-qa/content/106-qa-reporting
FercueNat 10bfd2be39
Adding information to Reporting node - QA Roadmap (#2838) 		2 years ago
..
100-junit.md Add content for junit (#2371) 2 years ago
101-allure.md Fixed typo in Allure node (#2595) 2 years ago
102-test-rail.md added content to 102-test-rail.md (#2500) 2 years ago
readme.md Adding information to Reporting node - QA Roadmap (#2838) 2 years ago

readme.md

QA reporting

The International Software Testing Qualifications Board (ISTQB) glossary defines a QA report as: Documentation summarizing test activities and results. By documenting the testing that was conducted and the results that were achieved, QA reports provide valuable insight into the health of the code base and critical metrics. As such, they should be generated on a regular basis to ensure the quality standards are being met. So basically, test reports should document all of the test cases that were performed during software testing, as well as the results of those tests. They should also deliver relevant information about the product and highlight any areas where improvements can be made.

Free Content

How do you write a QA report? How To Write QA Test Summary Report? [13 Easy Steps]