What is Capture/Replay Tool?
A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.
What is Code Walkthrough?
A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.
What is Defect?
Nonconformance to requirements or functional / program specification
What is Software Requirements Specification?
A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software/
What is Stress Testing?
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.
What is Test Plan?
A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.
How can it be known when to stop testing?
This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:
- Deadlines (release deadlines, testing deadlines, etc.)
- Test cases completed with certain percentage passed
- Test budget depleted
- Coverage of code/functionality/requirements reaches a specified point
- Bug rate falls below a certain level
- Beta or alpha testing period ends
- What are all the basic elements in a defect report?
- Is an "A fast database retrieval rate" a testable requirement?
- What is software quality assurance?
- What is the value of a testing group? How do you justify your work and budget?
- What is the role of the test group vis-à-vis documentation, tech support, and so forth?
- How much interaction with users should testers have, and why?
- How should you learn about problems discovered in the field, and what should you learn from those problems?
- What are the roles of glass-box and black-box testing tools?
- What issues come up in test automation, and how do you manage them?
- What development model should programmers and the test group use?
- How do you get programmers to build testability support into their code?
- What is the role of a bug tracking system?
- What are the key challenges of testing?
- Have you ever completely tested any part of a product? How?
- Have you done exploratory or specification-driven testing?
- Should every business test its software the same way?
- Discuss the economics of automation and the role of metrics in testing.
- Describe components of a typical test plan, such as tools for interactive products and for database products, as well as cause-and-effect graphs and data-flow diagrams.
- When have you had to focus on data integrity?
No comments:
Post a Comment