Reporting
| |
Note that this sample report includes a primitive command "Mu.replicate" that creates a string of 100 'a' characters, and the results display indicates what the actual input looked like. The Mu Test Suite automatically generates the inputs as directed by the user, and evaluates the dynamic responses from the live IP Service in real time, flagging any discrepancies as issues to be debugged later.
|
| |
On the other hand, this other sample report shows what a report looks like when all tests pass.
|
The Mu Test Suite provides extensive reporting to help the testers and their management teams understand the severity of the failures and act upon them in a meaningful way. Each report can be customized with notes, a corporate logo and information about the tester and test conditions. In addition, the Mu Test Suite can digitally sign the report for tamper-protection.
Executive Reports (Studio Zx and Protocol Fuzzing)
An Executive Summary report (in PDF format) contains detailed information about the service performance during each test. This report is designed as an easy-to-read, high-level summary of the test results. With a Grade rating system and metrics on Five 9's, the Executive report is intended for the management teams to quickly understand the test results without getting lost in the details.
Forensic Reports (Studio Zx and Protocol Fuzzing)
The Forensic Report (in a .zip format) is intended for testers and developers to understand the test results and remediate the fault conditions rapidly. This report has the following content:
- Test overview (HTML)
- Test configuration (XML)
- Engine log, fault trace from monitors, transaction information, packet captures for each of offending test cases
- Detailed statistics for each test case
- A standalone linux executable to reproduce the offending test case
Studio Fx Reports
The Studio Fx report (in PDF format) contains specific information about the test cases that were executed in either Functional or Interoperability testing. This report is designed as an easy-to-read, yet sufficiently detailed summary of the test results. In the event of a test case failing to return the expected response, in other words, the assertion failed due to the actual response from the IP Service not matching the expected
response in the test definition, this report shows the expected response and the actual response, while showing what the test was configured to expect.
|
