How to prepare test report
The next step after a complicated and time-consuming work arranging process, test planning, defect searching is preparing a performance report.
Reporting is significant for everyone taking part in the project, as Product managers, Product owners, developers and other team members should be informed about the performance of key elements, current defects and problems to adjust some steps and resources.
USEFUL LINK: EasyQA YouTube channel
EasyQA test managenemt tool offers a simple and fast reporting process with the Test Report function which gives an opportunity to:
- generate detailed project report easily
- track test cases coverage of the functionality
- track the defect count and their types
- track team members activity
- track spent time
- receive additional info and statistic data about the project status
The team and the client are able to make right decisions concerning the next steps and plans on the basis of information provided.
How to generate test report
Making a report will not take a lot of time in EasyQA test managenemt tool.
The user should click on Test reports tab on the Testing Activities page.
All the project reports are kept in one place and users can access them any time.
With Test reports tab users can generate the reports by categories:
- test cases report
- test run report
- report on the issues count in the project
- report on the crashes count in each build version
- spent time report
Let’s talk about each report type in details.
The test cases report
To receive the above mentioned types of reports in EasyQA test managenemt tool a user has to choose a test plan from the dropdown menu and press the Generate button.
Then, the system will generate:
- the full project description
- the tester’s name
- the test cases count
- the diagram showing the test-cases types (positive, negative, integration tests, localization, authorization etc)
Each test type has its own features to be taken into consideration when conducting the testing.
For example:
- whether the website or mobile app is user-friendly
- whether a user is able to register
- what is the app’s behavior if a user has forgotten a password
- whether the app will take into consideration localization problems (translation into another language, date and numbers format, email addresses, the name and last name sequence, currencies etc)).
It is very important information for the client as they can be ensured that their product will be tested properly.
The test run report
A user chooses a Test Run they want to get a report on, and presses the Generate button in EasyQA test managenemt tool.
As a result, the system generates info with:
- the project title
- the tester’s name
- the count of modules
- and test cases passed
- a diagram with the test cases types and their results for better info comprehension
For instance, the passed test cases mean that the functionality part they covered works properly while failed test cases depict the functionality defect area.
Reports for issues in the project
This type of report can be generated in 4 categories in EasyQA test managenemt tool:
I. By bug status - a user will receive the info about:
- the project title
- a tester’s name
- as well as the defects count according to their status shown in a diagram (submitted, reopen, in progress, code review, QA review)
II. By bug priority - a user will receive the info about:
- the project title
- a tester’s name
- and the defects count according to their priority shown in a diagram (Lowest, Low, Medium, High, Highest)
III. By bug severity - a user will receive the info about:
- the project title
- a tester’s name
- and the defects count according to their priority shown in a diagram (Low, Medium, High, Critical)
IV. By bug type - a user will receive the info about:
- the project title
- a tester’s name
- and a diagram displaying the bug types and their count
For example, the report will point out:
- whether there are system crashes when the user is not able to continue the work
- if there are some document inaccuracies which cause bugs
- if there are recommendations offered on product quality improvement
- or whether there are some functional usability problems
The report on the crashes count in each build version
A user will receive the info about:
- the project title
- a tester’s name
- crashes count
- and the diagram with the amount of crashes in each test object version
Spent time reports
The user can generate two types of spent time reports in EasyQA test managenemt tool:
I. Spent time by selected user - you will receive the info about:
- the issues count
- all spent time
- a member’s name
- the diagram with the amount of hours according to type of work
- the table with detailed info
II. Spent time for all project - you will receive the info about:
- the issues count
- all spent time
- members names
- the diagram with the amount of hours according to type of work
- the table with detailed info
Additional features
A user can download or print any type of report in EasyQA test managenemt tool and use it for different purposes, such as:
- handouts for stand ups, so all team members could see the progress
- or vice verse for making decisions on changing some priorities and the methods of quality improvement
- it can be used if there is an Internet failure
- sent by email to whom it may concern and to the client who will be constantly informed about the project status and stages of development before the product is released
Analysing and using the information received from the Test Reports in EasyQA test managenemt tool may significantly assist not only in product quality improvement but in increasing the team performance efficiency.
Register new account and use EasyQA to improve software quality.
No comments