Spike Testing is a subtype of stress testing. It specifically tests the software's reaction to sudden and drastic increases in load, often for very short durations. Regular stress testing, on the other hand, assesses the system's performance under sustained extreme conditions.

Manual static analysis is primarily performed in the Requirement Analysis phase of the software development lifecycle. During this phase, the specifications are studied to identify any potential flaws, ambiguities, or inconsistencies before the design and coding commence.

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.

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.

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.

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.

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 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.

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.

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.

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.

Integrating automated testing into Continuous Integration ensures that any change to the software is automatically tested, ensuring that the software is always in a deployable state. It provides quick feedback to developers and reduces the time to release new updates.