Jun 29, 2023 12 min read
QA documentation: what and when needed
QA documentation is a set of documents created before and during testing. Mistakes made by people or unpredictable interaction of code elements can lead to defects at any stage of software development. The impact of these flaws can vary from minor to catastrophic. The QA process allows detecting and reporting defects, reduces risk, and improves product quality.
![QA documentation: what and when needed](https://luxequality.s3.amazonaws.com/Articles/QAdocumentation_+WhatAndWhenNeeded.png)
What Is QA Documentation ?
Types of QA Documentation and Their Purpose
![](https://luxequality.s3.amazonaws.com/Articles/+TypesOfQADocumentationAndTheirPurpose.png)
![](https://luxequality.s3.amazonaws.com/Articles/(2)TypesOfQADocumentationAndTheirPurpose.png)
- Test Strategy
- High-Level test plan
- Low-Level test plan
- Test Case
- Checklist
- Test Suite
- Test Coverage
- Test Run
- Bug report
![](https://luxequality.s3.amazonaws.com/Articles/(3)TypesOfQADocumentationAndTheirPurpose.png)
- Test management system
- Task (bug) management system
Test Strategy
Test Plan
A test plan is a step-by-step guide that outlines how to test something, like software or a system. It includes details on what needs to be tested, how it will be tested, and the resources required. The test plan helps ensure that everything is tested thoroughly and helps identify any issues or problems before the final product is released. Typically, high-level and specific-level test plans are used on projects. Having both types of test plans for the project is recommended. You can familiarize yourself with our articles on how to write a test plan in software testing and a typical software test plan for an in-depth understanding.
High-Level Test Plan
For more detailed information, click on the link.
Low-Level Test Plan
Test Steps
1. Click the “Registration” button
2. Enter valid user data (name, email, password)
3. Click on the "Register" button
Expected result
The registration page is displayed
Entered data is shown in name, email, and password inputs. Inputs are displayed with a green frame
The creation of the user account is successful
1. Click on the "Login" button
2. Enter valid credentials (email, password)
3. Click on the "Login" button below the login form
The login page is displayed
The entered data are displayed in the fields. Fields are displayed with green frames
The user is logged in and redirected to the home page
1. Log in to the application
2. Click on the "Create Post" button
3. Enter post details (title, content) and click the “Post” button
The user is successfully logged in
Create post page is displayed
Post is successfully created and displayed on the home page
1. Log in to the application
2. Click the user profile icon
3. Click the "Edit Profile" button
4. Modify user details (name, email, bio) and click “Save” button
The user is successfully logged in
The user profile page is displayed
The edit profile form is displayed
User details are successfully updated
1. Log in to the application
2. Click the account settings icon
3. Click on the "Delete Account" button
4. Confirm the account deletion
The user is successfully logged in
The account settings page is displayed
A confirmation prompt for account deletion is displayed
The user account is permanently deleted
Test Case
Test Steps
1. Click the “Registration” button
2. Enter valid user data (name, email, password)
Click on the "Register" button
Expected result
The registration page is displayed
Entered data is shown in name, email, and password inputs. Inputs are displayed with a green frame
The creation of the user account is successful
Writing and using test cases have a significant impact on business success. It results in happier clients, increased customer loyalty, reduced customer service expenses, and improved product reliability. As a result, the company's reputation and brand image are greatly enhanced. You can also read our article on how to write a test case in software testing.
Checklist
User Registration
User Login
Create New Post
Edit Profile
Delete Account
The user should be able to create an account
The user should be able to log in to his account
The user should be able to create and save a new post
The user should be able to edit his Profile and save changes
The user should be able to delete his account
Test Suite
- by type of test (e.g., integration tests vs. unit tests);
- by execution time (e.g., slow vs. medium vs. fast running tests);
- finally, by modules or areas in the application.
Test Coverage (e.g., matrix/table)
Step 1: Count all the lines of code in your program.
Step 2: Find out how many lines of code are covered by your current test cases.
Test Run
Test Case Name
Launch URL and login
Launch URL and login
Launch URL and login
Test Case ID
BS_01
BS_01
BS_01
Test Step
1
2
3
Description
Go to URL https://www.browserstack
Enter username password
Click on login button
Test Data
Username: Test Password: XYZ
Expected Result
Page displays
System accepts username and password
Login button should be clickable, and login should be successful
Actual Result
Page displays
Login can’t be entered
Login is impossible
Status
Passed
Failed
Blocked
- Passed
- Failed
- Blocked
- In progress
- Skipped
- Retest
- Not run
Bug Report
Let's have a look at an example of a bug report. (Read more about how to create a bug report)
Name (short description): The text field has a "NUMLOCK" value in the "Blood Product Number" control after pressing the "NUMLOCK" key
Status: Ready for QA
Project: Desktop
Affects versions: 1.0.5
Fix versions: 1.0.5
Priority: Medium
Assignee: Deepanshu Vashist
Reporter: Denis Terpylo
Description
Steps to reproduce:
- Login
- Create a new patient in DCR mode
- Open RESUS on CDS Panel
- Switch to Intake tab
- Set “Whole Blood (WB)“ into “IV Fluid“ filed
- Click on the “Blood Product Number“ field
- Press the “NUMLOCK“ button on the keyboard
- Take a look at the “Blood Product Number“ field value
Actual result: The text field has a "NUMLOCK" value in "Blood Product Number" field after pressing the "NUMLOCK" key
Expected result: The field value is clear
By reporting even seemingly minor bugs, you become a vital guardian against the emergence of interconnected complications. Imagine it as tending to a leaking pipe in your home; addressing it can save your abode from being submerged under unforeseen floods.
Test management system
Task (Bug) management system
Bug ID | Description | Application Version | Status |
---|---|---|---|
1. | Login button not functioning | 1.2.3 | Open |
2. | Incorrect data display in dashboard | 1.2.3 | In Progress |
3. | App crashes when clicking on settings | 1.2.3 | Resolved |
4. | Missing validation on input field | 1.2.3 | Open |
5. | UI alignment issue on mobile devices | 1.2.3 | Closed |
Conclusion
QA documentation is vital to successful software development by understanding its importance and utilizing appropriate documentation throughout testing. QA documentation templates are valuable resources for standardizing the creation of test plans, test cases, and bug reports. Using templates saves time and ensures consistency in documenting the testing process. Talk to us to discover how QA documentation can benefit your software development.
Was this article helpful to you?
Comments
There are no comments yet. Be the first one to share your opinion!
Looking for reliable Software Testing company?
Let's make a quality product! Tell us about your project, and we will prepare an individual solution.
FAQ
Why is QA documentation necessary?
QA documentation is crucial because it provides a structured approach to testing, promotes effective communication, and ensures the understanding of product quality throughout the software development process. It serves as a reference for stakeholders and helps to release a high-quality product to the market.
When should test documentation be used?
Test documentation should be utilized at all stages of the software development lifecycle, including requirement analysis, test case creation, test execution, defects reporting, fixes retesting, and pre-release product quality evaluation. It ensures thorough testing and aids in identifying and addressing issues early on.
What should be included in QA documentation?
QA documentation should consist of test cases, test plans, defect reports, and any other relevant documentation specific to the project. It should provide clear instructions, be well-structured, and incorporate examples and visual aids.
How is QA documentation different from technical documentation?
While technical documentation describes how a software system is designed and how to use it, QA documentation focuses on the process of verifying and validating that the software meets its intended purpose and quality standards.
How detailed should my test cases be?
The detail in test cases can vary based on the complexity of the feature being tested and the target audience. However, they should be clear enough that another tester could execute them without ambiguity.