Testing is questioning a product to evaluate it.or software testing is a way to identify defects in a software product Through testing ,Software testing is the process of executing a Program with the intent to find errors, which can raise the quality or reliability of the program.
Bug Reporting
Popular Tool Used for Bug Reporting are Mantis and Bugzzila.
Project Name:-
Build / Version:-
Test Environment:-
Summary of The Bug:-
Issue Type:-
Reproducibility:-
Assigned To:-
Severity:-
Priority:-
Detailed Description:-
Attachment:-
Status:-New/Open/Closed
Resolution:-Assigned/Fixed/Resolved
Project Name:-
Build / Version:-
Test Environment:-
Summary of The Bug:-
Issue Type:-
Reproducibility:-
Assigned To:-
Severity:-
Priority:-
Detailed Description:-
Attachment:-
Status:-New/Open/Closed
Resolution:-Assigned/Fixed/Resolved
Test Case
Test Case-Test Case is the step to test the result.
Test Case Writing:
Test case No.:
Functionality:
Requirement No.:
Written By:
Date:
Test case sheet Format-
S.No. Step to Execute Executed Result Actual Result Remark
Test Case Writing:
Test case No.:
Functionality:
Requirement No.:
Written By:
Date:
Test case sheet Format-
S.No. Step to Execute Executed Result Actual Result Remark
Software testing tool classification
1. Functional Testing Tool-
A) QTP (quick test professional)-HP
B) Rational function tester-IBM
C) Selenium / WATIR / WATIJ / WATIN/sahi-(open Source)
A) QTP (quick test professional)-HP
B) Rational function tester-IBM
C) Selenium / WATIR / WATIJ / WATIN/sahi-(open Source)
2. Non-functional Tool-
A) Load Runner-(HP)
B) Rational function tester-(IBM)
C) Jmeter /Weblood- (open source)
3. Defect Tracking Tool-
A) Rational Clear Quick-(IBM)
B) Mantis /Bugzilla-(open source)
4. Test Management Tool-
A) Quality Center-(HP)
B) Rational Test Manager-(IBM)
B) Test Link-(open source)
Characteristics of a bug
There are five characteristics of a bug-
1. The product is not doing something which product specification say it should do.
2. The product is doing something which product specification say it should not do.
3. The product is not doing something which product specification does not mention but it should do.
4. The product is doing something which product specification does not mention but it should not do.
5. The product is very slow (performance),hard to use(usability) ,in users eye it is not right(GUI).
1. The product is not doing something which product specification say it should do.
2. The product is doing something which product specification say it should not do.
3. The product is not doing something which product specification does not mention but it should do.
4. The product is doing something which product specification does not mention but it should not do.
5. The product is very slow (performance),hard to use(usability) ,in users eye it is not right(GUI).
SDLC and Software Testing Life Cycle
Software testing life cycle identifies what test activities to carry out and when to accomplish those test activities. Even though testing differs between organizations, there is a testing life cycle.
Software Testing Life Cycle consists of six phases.
Software Testing Life Cycle consists of six phases.
- Test Planning
- Test Analysis
- Test Design
- Construction and verification
- Testing Cycles
- Final Testing and Implementation and Post Implementation.
Software testing has its own life cycle that intersects with every stage of the SDLC. The basic requirements is software testing life cycle is to control/deal with software testing – Manual, Automated and Performance.
- Test Planning:
This is the phase where Project Manager has to decide what things need to be tested, do I have the appropriate budget etc. Naturally proper planning at this stage would greatly reduce the risk of low quality software. This planning will be an ongoing process with no end point.
Activities at this stage would include preparation of high level test plan-(according to IEEE test plan template Almost all of the activities done during this stage are included in this software test plan and revolve around a test plan.
Activities at this stage would include preparation of high level test plan-(according to IEEE test plan template Almost all of the activities done during this stage are included in this software test plan and revolve around a test plan.
2. Test Analysis:
Once test plan is made and decided upon, next step is to delve little more into the project and decide what types of testing should be carried out at different stages of SDLC, do we need or plan to automate, if yes then when the appropriate time to automate is, what type of specific documentation I need for testing.
Proper and regular meetings should be held between testing teams, project managers, development teams, Business Analysts to check the progress of things which will give a fair idea of the movement of the project and ensure the completeness of the test plan created in the planning phase, which will further help in enhancing the right testing strategy created earlier. We also have to define areas for Stress and Performance testing.
3. Test Design:
Test plans and cases which were developed in the analysis phase are revised. Functional validation matrix is also revised and finalized. In this stage risk assessment criteria is developed. If you have thought of automation then you have to select which test cases to automate and begin writing scripts for them. Test data is prepared. Standards for unit testing and pass / fail criteria are defined here. Schedule for testing is revised (if necessary) & finalized and test environment is prepared.
4. Construction and Verification
In this phase we have to complete all the test plans, test cases, complete the scripting of the automated test cases, Stress and Performance testing plans needs to be completed. We have to support the development team in their unit testing phase. And obviously bug reporting would be done as when the bugs are found. Integration tests are performed and errors (if any) are reported.
5. Testing Cycles
In this phase we have to complete testing cycles until test cases are executed without errors or a predefined condition is reached. Run test cases –> Report Bugs –> revise test cases (if needed) –> add new test cases (if needed) –> bug fixing –> retesting (test cycle 2, test cycle 3….).
6. Final Testing and Implementation:
In this we have to execute remaining stress and performance test cases, documentation for testing is completed / updated, provide and complete different matrices for testing. Acceptance, load and recovery testing will also be conducted and the application needs to be verified under production conditions.
The recording of new errors and enhancements is an ongoing process. Cleaning up of test environment is done and test machines are restored to base lines in this stage.
Proper and regular meetings should be held between testing teams, project managers, development teams, Business Analysts to check the progress of things which will give a fair idea of the movement of the project and ensure the completeness of the test plan created in the planning phase, which will further help in enhancing the right testing strategy created earlier. We also have to define areas for Stress and Performance testing.
3. Test Design:
Test plans and cases which were developed in the analysis phase are revised. Functional validation matrix is also revised and finalized. In this stage risk assessment criteria is developed. If you have thought of automation then you have to select which test cases to automate and begin writing scripts for them. Test data is prepared. Standards for unit testing and pass / fail criteria are defined here. Schedule for testing is revised (if necessary) & finalized and test environment is prepared.
4. Construction and Verification
In this phase we have to complete all the test plans, test cases, complete the scripting of the automated test cases, Stress and Performance testing plans needs to be completed. We have to support the development team in their unit testing phase. And obviously bug reporting would be done as when the bugs are found. Integration tests are performed and errors (if any) are reported.
5. Testing Cycles
In this phase we have to complete testing cycles until test cases are executed without errors or a predefined condition is reached. Run test cases –> Report Bugs –> revise test cases (if needed) –> add new test cases (if needed) –> bug fixing –> retesting (test cycle 2, test cycle 3….).
6. Final Testing and Implementation:
In this we have to execute remaining stress and performance test cases, documentation for testing is completed / updated, provide and complete different matrices for testing. Acceptance, load and recovery testing will also be conducted and the application needs to be verified under production conditions.
The recording of new errors and enhancements is an ongoing process. Cleaning up of test environment is done and test machines are restored to base lines in this stage.
Subscribe to:
Posts (Atom)