Categories

Netsparker Web Application Security Scanner

Software Testing Artifacts - Test Reports

What is Artifact?

An artifact is one of many kinds of tangible by-products produced during the development of software. Some artifacts (e.g., use cases, class diagrams, and other Unified Modeling Language (UML) models, requirements and design documents) help describe the function, architecture, and design of software. Other artifacts are concerned with the process of development itself—such as project plans, business cases, and risk assessments. – Source Wikipedia

 

Learn Artifact – Test Reports:

Test team sent out numerous test reports to different stakeholders for various purposes. Test reports are used to communicate the test aspects clearly among stakeholders. Test report information’s referred and analyzed in future to develop better projects in future. Information on test report is decided as per the purpose and the audience. Before preparing the test report tester should know whom the audiences for the particular test report are. Then tester should prepare the test report according the end purpose of the particular test report.

 

Why Test Reports Are Important?

  • It offers knowledge transfers and sharing experience among team members, management and client to improvement.
  • Test reports facilitate to maintain the test record with the required detail. This gives information availability.
  • Test report saves the time and effort to put on a project. The information is available to access quickly and effortless.
  • This gives the facility to keep the information and will reduce the ambiguity and distraction.
  • Versioning provide us the detail on what are the changes done on particular test matter.
  • Since we maintain test reports, the other members can review and give the feedback for betterment in the project.
  • It keeps a record on the testing activities carried out. Client will like to see the process and the test carried out.
  • We shall analyze the test report and use the lesson learn from it to the future projects.
  • It serves as a proof of evident to the testing carried out.
  • Test reports helps to make better decision.

 

Test Result Report:

In test result report, document the detailed test result. Usually test result report is sent periodically. Test result report provide the information of test execution and test result in detail. It also contain conditions, assumptions, constrain of test. Also mention which test item is tested by whom. Detail of remaining work is marked in the test result report to show how much remaining work to be done in the project.

Item Description
Test item Specific test item or software. (E.g. Software version or module.)
Description of the test item Describe the detail of test item.
Test result Whether the test items is pass, failed, blocked or on hold.
Test sate Whether the test items is completed, in progress or not started.
Defect(s) detail If the test item is failed then mention the defect detail. Add a linkage to the defect.
Total percentage completed State the completed test percentage.
Summary of the test result Mention the number of executed test cases, defect count, total test completion percentage.

 

Test Execution Report:

Test execution report contain the execution detail and the result of test execution. This is generally prepared to send to higher management from testing team to show the state of the test execution and test progress. When we deliver the software to client, we shall send the full test execution detail in brief. This would give a better understanding on the executed test and coverage to client.

Element Description
Test item Item, module or software that is been testing.
Scenario Scenario of the test.
Responsible tester Who tested the particular test item?
Date of test execution Date of the test executed.
Status Status of test execution.
Test environment Detail of test environment. Detail of hardware, software and tools.
Risk and constrain Any risk that impact the test execution and any constrain.
Test execution summary This provide detail of test execution by software section, test type, defect rage etc.
Defect summary and detail Defect count. Rate of open and closed defect. Severity and status wise defects.
Test cases detail Planned and executed test cases. Status and result of execution and test case.
Test progress Over all progress of test and which cycle the test execution is going on.

 

Test Summary Report:

Test summary report provide a detail of testing carried out throughout the software development life cycle. The items in a test summary report vary from organization to organization and also vary for different projects. Below are some common items stating in a test summary report. Information on test report is based on the audience of the test report. Audience can be client, management, business analyst, developers, testing team and organizational level members etc.

Items Content
Introduction Write the purpose of the test summary report. An introduction on particular test’s final state.
Overview Overview of testing and tested software.
Scope Explain the scope of the testing.
Out of scope Any out of scopes in testing
Test types All different type of tests executed.
Defect summary Defects count severity wise, software area wise, assigned developer wise, test category wise etc. If there is any limitation or open defect, clearly describe it.
Exit criteria Explain the exit criteria. Explain the factors considered to closure of test.
Coverage of testing Describe the covered areas in the software. State the test coverage against requirement.
Test execution summary Executed test cases and their result.
Test matrixes Detail and explanation of used test matrixes and the calculated value of those matrixes.
Lesson learn Any lesson learn in the specific project. This can be utilized in the future project.
Conclusion Conclusion of the testing and software project.

 

User Acceptance Testing:

User acceptance test report is created while conducting the user acceptance test and after conducting the user acceptance testing. It state the detail of conducted user acceptance test and the result of the user acceptance test. It also list the defect uncounted in user acceptance testing. User acceptance testing created during and after the user acceptance testing by the people who conduct the user acceptance test. This will be amazed to check test matrices like defect leakage rate, missed requirement etc.

Element Description
Test coverage
Item tested Item that tested.
Test area Tested item on which area.
Test description Describe the test item in detail.
Test date Date which test is conducted.
UAT result
UAT item Encountered item during user acceptance testing.
Type of UAT item Whether the item raised during the user acceptance testing is defect or change request or enhancement or improvement.
Date raised Date the UAT item found.
Severity Severity of the UAT item. Level of impact to the system by the identified UAT item.
Priority Priority of UAT item. How soon the UAT item should be fixed.
Raised by Person who raised the UAT item
Status Status of the UAT item. Whether it’s fixed or not fixed or need more clarification like wise.
Comment Any comment for the UAT item
Test environment Test environment detail where the user acceptance testing was done.
Defect summary Provide defect detail and count as a summary.

 

Conclusion:

Test reports are important as testing in a project. Test reports created at the begging of the project like test plan, test strategy, test cases etc. provides full detail of the testing that will be carried out on the software project. Test report that created during the testing like test execution report, test result report give the understanding on how the software is been tested. Test report created at the end of the project like test summary report, lesson learn report provides the testing and the result on the project. Creating and maintaining test report is essential, this create a visibility among stake holders. This can allow others to provide feedback on the testing that we carry out. It also provide clear understanding to other and avoid ambiguity and unwanted conflictions. Very important test reports plays a major role after the project completed. Test report and the lesson learn from those serves as an input to the new project. Maintain test report provide all the information about the testing throughout the software test development. All the information available in centralized place in easy and effortless to take and view. Test reports support to make decision. Always analyze the test report and cater the lesson learn from one project and use it to the other project for improvement.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>