Q. What is verification?
Answer: Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings.
Q. What is meant by validation?
Answer: Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed.
Q. What is meant by unit testing?
Answer: Unit testing is the process of testing a particular complied program, i.e., a window, a report, an interface, etc. independently as a stand alone component/program. The types and degrees of unit tests can vary among modified and newly created programs. Unit testing is mostly performed by the programmers who are also responsible for the creation of the necessary unit test data.
Q. What are the categories of debugging?
Answer: The various categories for debugging are :
Brute force debugging
Backtracking
Cause elimination
Program slicing
Fault tree analysis
Q. What is incremental testing?
Answer: Incremental testing is partial testing of an incomplete product. The goal of incremental testing is to provide an early feedback to software developers.
Q.What is regression testing?
Answer: Regression testing is not a level of testing, but it is the retesting of software that occurs when changes are made to ensure that the new version of the software has retained the capabilities of the old version and that no new defects have been introduced due to the changes.
Q. What is the difference between black box and white box testing?
Q. What is system integration testing?
Answer: Testing of software components that have been distributed across multiple platforms (e.g., client, web server, application server, and database server) to produce failures caused by system integration defects (i.e. defects involving distribution and back office integration).
Q. What is acceptance testing?
Answer: Testing the system with the intent of confirming readiness of the product and customer acceptance. Also known as User Acceptance Testing.
Q. What is the difference between alpha, beta and acceptance testing?
Q. What are the advantages of black box testing?
Answer: The advantages of this type of testing include :
Q. What are the advantages of white box testing?
Answer: The various advantages of white box testing include :
Answer: Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings.
Q. What is meant by validation?
Answer: Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed.
Q. What is meant by unit testing?
Answer: Unit testing is the process of testing a particular complied program, i.e., a window, a report, an interface, etc. independently as a stand alone component/program. The types and degrees of unit tests can vary among modified and newly created programs. Unit testing is mostly performed by the programmers who are also responsible for the creation of the necessary unit test data.
Q. What are the categories of debugging?
Answer: The various categories for debugging are :
Brute force debugging
Backtracking
Cause elimination
Program slicing
Fault tree analysis
Q. What is incremental testing?
Answer: Incremental testing is partial testing of an incomplete product. The goal of incremental testing is to provide an early feedback to software developers.
Q.What is regression testing?
Answer: Regression testing is not a level of testing, but it is the retesting of software that occurs when changes are made to ensure that the new version of the software has retained the capabilities of the old version and that no new defects have been introduced due to the changes.
Q. What is the difference between black box and white box testing?
- Black box testing is a testing strategy based solely on requirements and specifications. Black box testing requires no knowledge of internal paths, structures, or implementation of the software being tested.
- White box testing is a testing strategy based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.
Q. What is system integration testing?
Answer: Testing of software components that have been distributed across multiple platforms (e.g., client, web server, application server, and database server) to produce failures caused by system integration defects (i.e. defects involving distribution and back office integration).
Q. What is acceptance testing?
Answer: Testing the system with the intent of confirming readiness of the product and customer acceptance. Also known as User Acceptance Testing.
Q. What is the difference between alpha, beta and acceptance testing?
- Alpha Testing : Alpha testing refers to the system testing carried out by the test team within the development organization.
- Beta Testing : Beta testing is the system testing performed by a selected group of friendly customers.
- Acceptance Testing : Acceptance testing is the system testing performed by the customer to determine whether to accept or reject the delivery of the system.
Q. What are the advantages of black box testing?
Answer: The advantages of this type of testing include :
- The test is unbiased because the designer and the tester are independent of each other.
- The tester does not need knowledge of any specific programming languages.
- The test is done from the point-of-view of the user, not the designer.
- Test cases can be designed as soon as the specifications are complete.
Q. What are the advantages of white box testing?
Answer: The various advantages of white box testing include :
- Forces test developer to reason carefully about implementation
- Approximates the partitioning done by execution equivalence
- Reveals errors in hidden code
No comments:
Post a Comment