What is test summary report?

Test Summary Report


1.0 Overview
Provide a high level description of the overall testing and results.

2.0 Test Coverage/Results
Describe the specific functionality (area) tested and the results of the testing.

3.0 Functionality NOT Tested
Document any functionality that should have been tested, but was either not tested or did not receive adequate testing. Provide reason why testing was not accomplished. Such as:
. Late delivery of product
. No impact from changes to this functionality based on
. Development assessment
. Not enough time for testing –
. Project Manager approved deferral of testing until next release

4.0 Test Confidence
Describe the confidence level of the testing that was performed. As an outline for now we can use the following levels:
. Extremely High
. High
. Medium
. Low

Provide the reason for the rating if not Extremely High or High.

5.0 Test Issues and Concerns
Document any issues or concerns you may have about the release. This may encompass things such as:
. No documentation of changes in area xxxx made testing pretty darn difficult.
. Late delivery of release caused impact to available resources.
. Slip of code complete caused a one-week impact to the test schedule

Verification V/S Validation

Verification ensures that system(software,hardware,documentation,personalnel) complies with the organization standards or process relying on review or non-executable methods.

Verification requires several types of reviews like requirement review,design review,code review, code walkthroughs, code inspections and test reviews.The system users should involes in this review to find defects before they are build in to the systems.

Validation physically ensures that system works according to the plan by executing system functions through the series of the tests.

Validation examples are unit testing,integration testing,system testing and user acceptance testing.

verification answers the question " Are we building the right system?" while
validation addresses, "Are we build the system right?"

Define the component present in testplan?

1)Objectives
2)scope of the project
3 Test Strategy it includes Scope of Testing thing that are not covered in Scope Etc
4)Resources
5)Assumption Which Covers Risk During the Testing For ex if the Code is not delivered on time etc
6)Features to be tested.
7)Features not be tested.
7) Work Plan--------Which Includes the Role and the people Involved in the Testing
8) testing Procedures ---------- Like how they incite the Migration of the Code Etc
9)Entry and Exit criteria
10)Dependencies.
11) Environment Requirement
12)Execution Criteria
12)Observation
13) Release Notes

Define component present in Test Strategy?

1) Identifies the items that should be targets by the test
2) Identifies the motivation and ideas behind the test cases should be covered.
3) Outlines the testing approach that will be used.
4)Identifies the required resources.
5)Lists the deliverable elements of the test project.

What is bidirectional traceability?

Traceability matrix cross to check whether all requirements are tested. Using traceability matrix we can estimate how much functionality is tested.

Forward traceability is from requirement to design to code to test cases.

Backward traceability is from reverse direction and make sure that end product meets all requirements.

So bidirectional traceability is forward traceability+backward traceability.

What is Equivallance partinioning?

A technique in black box testing is equivalence partitioning. Equivalence partitioning is designed to minimize the number of test cases by dividing tests in such a way that the system is expected to act the same way for all tests of each equivalence partition. Test inputs would be selected from each partition.

Suppose you want to write test cases to check month field. The valid month range will be 1 to 12 stranding from Jan to Dec. This will be valid range of partition. Invalid partition will be <=0 and second invalid range will be >=13.

By using equivalence partitioning you can reduce number of test cases. and you can select right test cases to cover all scenarios.

What is Boundary Value Testing ?

Boundary Value Testing(BVT) testing technique in Black box testing. It is testing technique to find whether application accepting the expected range of values and rejecting values which falls out of range.

For example for password it should accept alphabet character(a-z) and within 4 to 10 characters.

BVT done like this.

max:10 pass; max-1=9 pass; max+1=11 fail;
min=4 pass; min+1=5: pass; min-1=3 fail;

Also check corner value and check application is working properly or not.

---