What is fatal defect?
These are the defects which results in complete software failure.
What is deferred/Trivial defect?
These are the defects which will not affect the customer business workflow and these defects can be fixed in the up coming releases. These minor defects is called trivial defect.
What is Latent defect?
These are the defect present in the software for some particular period of time and not identified by test engineer.
What is defect density:
Defect density=Total number of defects found-Total number of defect fixed/Total number of test case executed.
What is System integration testing?
Testing the data flow between two different software and also make sure end to end flow between two different software is working as expected or not is called System integration testing.
Why does Software have defect?
1. Programming error
2. Build is not installed properly
3. Misunderstanding/Miscommunication of requirements
4.Software Complexity
5.Because of Change request
6. Time Pressure
When to Stop Testing?
1. When the product functionality is stable
2. When the basic functionality itself is not working.
3. When time span is less, we should test basic and critical features and stop.
4. when there is no budget
Why should we do testing?
1. To ensure quality in the software
2. To make sure all the customer requirements are implemented properly.
What are the principles of Software testing or manual testing.
1. We should do early testing.
2. We should not do exhaustive testing
3. Testing is done to show the presence defects in the software
4. We should follow pesticide paradox
5. We should follow defect clustering
6. Testing is context dependent (depending on type of application and how customer use the application)
7. Absence of defects in the software does't mean that software is defect free.
What are the types of defects?
1. Functional defects
2. Usability defects
3.Compatibility defects
4.Performance defect.
5. Database defects.
6. Web security defects.
7. Globalization defects.
What is Testware?
Collection of all the material which is required to test the software is called test ware.
Ex: Test case,test script, traceability marix etc.
What is Compliance testing?
Testing the software and check whether software needs govt. rules,regulations policy is called compliance testing.
What is risk based testing?
Testing the software which is under risk is called risk based testing. here test engineer try to test feature or functionality which has got highest impact and probability of failure.
What is pilot testing?
It is a type of testing done by the users where in they do trail run of the software, check the performance, give the feedback to the company before the software is deployed into production server this is called pilot testing.
What is the difference between test strategy, Test plan, Test approach?
Test strategy is also called master test plan
Test approach is a part of test plan
Test strategy is a document prepared by project manager in a organization level. it is a document which capture application on how we go about testing all the projects in future.
These are the defects which results in complete software failure.
What is deferred/Trivial defect?
These are the defects which will not affect the customer business workflow and these defects can be fixed in the up coming releases. These minor defects is called trivial defect.
What is Latent defect?
These are the defect present in the software for some particular period of time and not identified by test engineer.
What is defect density:
Defect density=Total number of defects found-Total number of defect fixed/Total number of test case executed.
What is System integration testing?
Testing the data flow between two different software and also make sure end to end flow between two different software is working as expected or not is called System integration testing.
Why does Software have defect?
1. Programming error
2. Build is not installed properly
3. Misunderstanding/Miscommunication of requirements
4.Software Complexity
5.Because of Change request
6. Time Pressure
When to Stop Testing?
1. When the product functionality is stable
2. When the basic functionality itself is not working.
3. When time span is less, we should test basic and critical features and stop.
4. when there is no budget
Why should we do testing?
1. To ensure quality in the software
2. To make sure all the customer requirements are implemented properly.
What are the principles of Software testing or manual testing.
1. We should do early testing.
2. We should not do exhaustive testing
3. Testing is done to show the presence defects in the software
4. We should follow pesticide paradox
5. We should follow defect clustering
6. Testing is context dependent (depending on type of application and how customer use the application)
7. Absence of defects in the software does't mean that software is defect free.
What are the types of defects?
1. Functional defects
2. Usability defects
3.Compatibility defects
4.Performance defect.
5. Database defects.
6. Web security defects.
7. Globalization defects.
What is Testware?
Collection of all the material which is required to test the software is called test ware.
Ex: Test case,test script, traceability marix etc.
What is Compliance testing?
Testing the software and check whether software needs govt. rules,regulations policy is called compliance testing.
What is risk based testing?
Testing the software which is under risk is called risk based testing. here test engineer try to test feature or functionality which has got highest impact and probability of failure.
What is pilot testing?
It is a type of testing done by the users where in they do trail run of the software, check the performance, give the feedback to the company before the software is deployed into production server this is called pilot testing.
What is the difference between test strategy, Test plan, Test approach?
Test strategy is also called master test plan
Test approach is a part of test plan
Test strategy is a document prepared by project manager in a organization level. it is a document which capture application on how we go about testing all the projects in future.
No comments:
Post a Comment