Dynamic testing, unlike static testing, requires the software to be in a _______ state.
- Configured
- Designed
- Developed
- Executable
"Dynamic Testing" involves executing the software system or a part of it during the testing process. For dynamic testing to be carried out, the software needs to be in an "Executable" state, i.e., it should be running.
_______ is a key criterion that considers the ease with which testers can create, maintain, and execute test scripts using the automation tool.
- Maintainability
- Scalability
- Testability
- Usability
Maintainability is a critical attribute of testing tools. It signifies the ease with which test scripts can be updated when there are changes in the application. A maintainable script leads to reduced costs and efforts over time as the application evolves.
During the STLC, the process of executing the test cases and reporting defects is carried out in the _______ phase.
- Test Closure
- Test Design
- Test Execution
- Test Planning
The "Test Execution" phase of the STLC is where the actual testing occurs. During this phase, the test cases are executed against the software. Any deviations from the expected results are reported as defects. This is a critical phase, as it uncovers the defects before the software is released.
The _______ section of a test plan specifies the items that are subject to testing.
- Resources
- Schedule
- Scope
- Strategy
The "Scope" section of a test plan defines what is subject to testing, which can include features, modules, or functionalities. It sets the boundaries and clarifies what is to be tested and what is not.
In exploratory testing, testers often use a _____, which is a brief document that provides guidance on what to test.
- Test Case
- Test Charter
- Test Plan
- Test Script
In exploratory testing, a "Test Charter" is used to provide guidance on what areas or functionalities to test. While it offers direction, it still allows testers the freedom to explore and adapt their testing as they proceed.
In Agile methodologies, which role closely collaborates with developers to ensure requirements are testable?
- Agile Tester
- Business Analyst
- Product Owner
- Scrum Master
In Agile methodologies, an Agile Tester closely collaborates with developers and other stakeholders to ensure that requirements are clear and testable. They provide immediate feedback, contribute to user story refinement, and ensure that testing considerations are included from the beginning of the development cycle.
The process of evaluating the test's progress and adapting the test plan accordingly is termed as _______.
- Test Analysis
- Test Design
- Test Execution
- Test Monitoring
Test Monitoring refers to the continuous monitoring of the testing process. It involves evaluating the progress of testing against the objectives set and making necessary adjustments to ensure the testing aligns with the set plan and objectives.
In non-incremental integration testing, what is a primary challenge testers might face?
- Difficulty in isolating defects
- Lack of documentation
- Limited tools availability
- Time-consuming
Non-incremental integration testing (often referred to as Big Bang) integrates all components at once, making it challenging to isolate defects since everything is tested together. This can lead to prolonged debugging sessions.
How does session-based test management (SBTM) enhance the efficiency of exploratory testing?
- By automating repetitive tests
- By introducing formal test documentation
- By providing scripted tests
- By setting timed sessions for structured exploration
SBTM enhances the efficiency of exploratory testing by organizing the testing process into timed sessions, allowing testers to focus on a specific area or objective. This structured approach ensures that the exploration is systematic, maximizing the coverage and quality of tests within the time frame.
Imagine a scenario where there's a sudden demand to increase the scope of testing due to a newly introduced module. How would this impact test planning and resource allocation?
- Increase test coverage and possibly bring in additional resources.
- Introduce automation for the new module only.
- No change in test planning required.
- Reduce test coverage for other modules.
The introduction of a new module would require increasing test coverage to accommodate the new functionalities. This could lead to the need for additional resources or extended time. While introducing automation could speed up the process, it might not be immediately feasible. Reducing test coverage elsewhere is risky and should be a last resort.