What is a Test Fusion Report in QTP?

This article gives a detailed description of what a test fusion report is. Once a test has been executed, all the aspects of that particular test report are displayed by a certain report that has been termed as the test fusion report. 

What are Test Fusion Reports?

Basically the below mentioned aspects of a test run are displayed by the test fusion report:

1. A high level overview of the results.
2. Tree view of that particular test specifying the exact point where the application software actually encountered failure and this tree view is expandable.
3. The data that was used during the test run.
4. The screen shots of the steps of the test run where the application software showed some discrepancy.
5. Explanation of each check point in high detail along with the fail and pass criteria.

- These test fusion reports can be combined along with the quick test professional. 

- The main advantage of this is that on combining these reports with the quick test professional, they can be shared among the whole development and quality assurance team. 

- The test fusion report displays at what all exact points the application software failed. 

- The test fusion report consists of a data table. 

- This data table gives a record of the whole test data. 

- A screen view is also presented in the test fusion report which provides one with the actual screen view. 

- With the aid of the test fusion report, even the success or failure of the check points can be determined. 

- The test fusion report proves to be quite a handy tool while the developer has to report to its client or customer. 

- There are some other components of the test fusion report as mentioned below:

1. Name of the test
2. Test case
3. Start of the test run
4. End of the test run
5. Name of the result
6. Iteration
7. Status

- A different aspect of the test run is displayed by the test fusion report and can also be considered to be a kind of compilation of the whole application testing process. 

- The screen shots provided by the test fusion report provides a solid support for any inconsistencies that are present within a software application. 

- The test fusion report is represented in the tree format and displays all the aspects of the test run in the same format. 

- You can find detail for each and every step of the iterations here in the test fusion report. 

- All the results of a test are collected by the test fusion report. 

- Test fusion report can also be categorized under the instances of the collecting parameter return. 

- There is a big difference between the errors and the failures which is distinguished by the test frame work. 

- Anticipated problems are called failures whereas the un- anticipated ones are the errors. 

- All these are listed by the test fusion report. 

- The results of the testing have to be reported at various stages like unit testing, integration testing and system testing and so on. 

- The test fusion report provides the state of the software product that is under development through different angles. 

- Producing this test fusion report takes around 5 – 10 percent of the total development effort. 

- This percent though being quite less is of great significance, after all an organization cannot give a certification about the readiness of the software product in just one line. 

- Producing a test fusion report becomes much more important especially when the software encounters some problem.

- There are several other aspects of the software system or application that the customer would like to know apart from the functional requirements like a few mentioned below:

1. platform
2. dependence
3. performance and so on. 

What is a Load Test Results Summary Report?

Load testing is one of the most important testing that is carried out under performance testing and involves putting demands or load on the software system or application in order to measure its response and also the quality of response. 

About Load Testing

1.Load testing forms a very convenient means for determining the behavior of the software system or application under question and under both normal as well as peak conditions. 

2.Load testing helps a lot regarding the identification of the maximum operating capacity of the software system or application plus the identification of elements which are causing degradation of the software system.

3.Load testing becomes stress testing when the load is raised above the normal usage patterns. 

4.The load is raised to such limits where the probability of expecting the errors is quite high.

5.There exists no boundary between the transition of the load testing in to stress testing. 

6.The goals of the load testing are still not so specific.

7.Load testing is actually categorized under non functional testing. 

8.Load testing involves the practice in which the expected usage of the software system or application is modeled by simulating the multiple users using the application concurrently.

About Load Test Result Summary Report

1. A good load testing report says much about the software system or application.

2. A good report is always presentable to the customer as well as the manager.

3. A load test results summary report is simply a cut short and modified version of the original load testing reports. 

4. The original load testing reports are quite lengthy and difficult to understand for a customer. Therefore, a summary of this report is prepared which is short enough and simple to understand. 

5. You cannot expect your customer to go through the whole bulky report rather you need to provide them with a glimpse of everything. 

6. A load test results summary report serves all these purposes. 

Elements of Load Test Summary Report

1. Load test goals: 

A load test differs from functional tests in the way that a load test cannot fail or pass without the inclusion of any extra conditions. We mean to say that you cannot test a software system or application stands a load in general rather you test it against some specific load having specific performance parameters.

2. Technical description of the test goals: 

Once you know what your goals are, the requirements need to be formalized and transformed in to a technical description that you can apply to the load testing tool. You need to define aspects like:

a)   Type of load to be given to the software system or application,

b)   Number of virtual users to be employed in every test phase.

c)   Acceptable response time and so on.

     3. Realistic emulation of the virtual users: 

    Most important element of the load test results summary report.  This section lays down the division of the all potential real users of the software system or application in to a number of different types based on their expected behavior. The special script developed for every user is also mentioned alongside. In addition to this the user sessions are also mentioned.

     4. Execution of the test: 

     It mentions what all tests were executed and with what load. 

   

     5. Analyzation of the test results:  

    It includes the result of the test whether pass or fail and valuable information obtained from the tests. It also mentions the following:

    a)   Number of errors

    b)   Response times 

    c)   Number of sessions or requests per second and so on.

    6. Problems and improvement suggestions. 

Validation phase - Unit Testing - how to write Unit test cases

Preparing a Unit test case document commonly referred as UTC is an important task in unit testing activity. Having a complete UTC with every possible test case leads to complete unit testing and thus gives an assurance of defect free unit at the end of unit testing stage.

While preparing unit test cases the following aspects should be kept in mind-

Expected functionality
Write test cases against each functionality that is expected to be provided from the unit being developed. It is important that user requirements should be traceable to functional specifications which should be traceable to program specifications which should be traceable to unit test cases. Maintaining such traceability ensures that the application fulfills user requirements.

Input Values
- Write test cases for each of the inputs accepted by the unit. Every input has certain validation rule associated with it. Write test cases to validate this rule.
- There can be cross-field validations in which one field is enabled depending upon input of another field. Test cases for these should not be missed.
- Write test cases for the minimum and maximum values of input.
- Variables that hold data have their value limits. In case of computed fields, it is very important to write test cases to arrive at an upper limit value of the variables.
- Write test cases to check the arithmetic expressions with all possible combinations of values.

Output Values
- Write test cases to generate scenarios which will produce all types of output values that are expected from unit.

Screen Layout
Screen/report layout must be tested against the requirements. It should ensure that pages and screens are consistent.

Path Coverage
A unit may have conditional processing which results in various paths, the control can traverse through. Test cases must be written for each of these paths.

Assumptions and Transactions
A unit may assume certain things for it to function. Test cases must be written to check that the unit reports error if such assumptions are not met.
In case of database applications, test cases should be written to ensure that transactions are properly designed and in no way inconsistent data gets saved in the database.

Abnormal terminations and Error messages
Test cases should be written to test the behavior of unit in case of abnormal termination.
Error messages should be short, precise and self explanatory. They should be properly phrased and free of grammatical mistakes.