For many newcomers to testing, when doing web performance testing, after the scenario runs, we can use the Analysis component to analyze the results. Today, let's review together how to use LoadRunner to call the relevant knowledge points of Analysis components. (This method is only suitable for web performance testing)
01. What is software testing?
Let me first review the operation steps for you.
We first need to use the Controller to run the test script according to the set test scenario through LoadRunner . As shown below.
In the "Mercury Load Runner Controller" window, click the menu "Results" and select the "Analyze Results" menu item to start "Mercury Load Runner Analyze" to analyze the current test results.
Then, through "Mercury Load Runner Analyze", we will obtain the test result data automatically counted by the current test project. For example, Transaction Summary, Average Transaction Response Time, etc.
In the main window, we only need to click the catalog item in the left view, and then we can see the corresponding test results in the right data view. Here, the test result data will be displayed in tables, graphs, and histograms for our reference.
If the chart data results displayed by default are not enough to meet your needs, you can also display the report items you need by adding a new table.
Here's a quick rundown of the specific steps:
①
Click on the "Graph" menu in the main Mercury LoadRunner Analyze window, select "Add Graph" and you will see the "Open a New Graph" dialog. As shown below:
②
In the tree directory on the left side of the "Open a New Graph" dialog box, select the graph item to be displayed, click the [Open Graph] button, and the newly added display graph is completed.
Next, let's talk about how to generate the corresponding report.
After completing the result analysis of the previous step, we can use "Mercury LoadRunner Analyze" to generate test reports in various formats.
First, click the "Reports" menu in the "Mercury LoadRunner Analyze" main window;
Then, select the "HTML Report" menu item to generate a test report in HTML format;
Finally, select the "Microsoft Word Report" menu item to generate a test report in Word format.
Do you remember?
02. Summary of knowledge points
Essential Elements of a Test Report
Bug description: (what)
Where the bug occurs: (where)
Analysis Bug: (why)
Solution: (how)
Reporter: (who)
Template for software testing report
××× company
××× (product or software)/××× (module) test report
(1) Outline the purpose of the test
Briefly describe the purpose of this test, such as: to verify whether a module meets the background of the design project;
Briefly describe the background of the project where the test is conducted, such as: what stage ××× (project) is currently in, and other information.
(2) Test environment
Hardware environment: only describe the hardware environment and version information of the test object
Software environment: only describe the software environment and version information of the test object
(3) Testers
personnel
Role
(4) Actual progress
Occupancy time: describe the time span of the entire test process, such as: xxxx-xx-xx to xxxx-xx-xx
Progress and reasons: If the test is completed ahead of schedule or delayed, please explain the specific reasons
(5) Test reference documents
"××× Test Plan"
"××× Test Case"
"Document Three"
"Document Four"
Version information V1.0
(6) Test data
Test Data
Total number of test items 0
PASS0PASS rate #DIV/0!
FAIL0FAIL rate #DIV/0!
Severity - High 0 Where: High - #DIV/0!
Severity - Medium 0 Medium - #DIV/0!
Severity - Low 0 Low - #DIV/0!
Test Item Number Test Item Pass or Not Problem Description Problem Severity
Note: Definition of problem severity:
High—resulting in system crash or failure to realize the functions of some subsequent test items;
Medium—affects the integrity of the test function of this part and needs to be resolved urgently;
Low——It is only a small bug in the system, or a part that needs to be adjusted according to the test process, but it does not need to be resolved urgently.
(7) Summary of the project
Summarize the entire test project, such as: whether the test is passed or not, and the main reason for FAIL.
(8) Opinions and Suggestions
For this test work, put forward your own opinions or suggestions. "None" can be filled in if there is none.
03. Write at the end
For many novice testers, because they are not proficient in some operations, they often cannot remember how to operate them. Here I hope that everyone can diligently summarize the knowledge points, or extract the conclusions, so as to facilitate their own memory.
It is said that a good memory is not as good as a bad pen, and there is a saying that hard work can make up for one's weakness. I hope you can practice a lot and broaden your test path~
[The following is the most complete software test engineer learning knowledge architecture system diagram in 2023 that I compiled]
1. From entry to mastery of Python programming
2. Interface automation project actual combat
3. Actual Combat of Web Automation Project
4. Actual Combat of App Automation Project
5. Resume of first-tier manufacturers
6. Test and develop DevOps system
7. Commonly used automated testing tools
Eight, JMeter performance test
9. Summary (little surprise at the end)
life is long so add oil. Every effort will not be let down, as long as you persevere, there will be rewards in the end. Cherish your time and pursue your dreams. Don't forget the original intention, forge ahead. Your future is in your hands!
Life is short, time is precious, we cannot predict what will happen in the future, but we can grasp the present moment. Cherish every day and work hard to make yourself stronger and better. Firm belief, persistent pursuit, success will eventually belong to you!
Only by constantly challenging yourself can you constantly surpass yourself. Persist in pursuing your dreams and move forward bravely, and you will find that the process of struggle is so beautiful and worthwhile. Believe in yourself, you can do it!