Negative, Endurance, Spike & Component Testing

Negative Testing:

Term	Definition
Negative Testing	- Definition: Negative testing is a software testing technique where the system undergoes testing with invalid input or unexpected conditions to ensure it behaves as expected, aiming to identify vulnerabilities and weaknesses.
	- Elaboration: The focus during negative testing is on evaluating how the system handles incorrect or inappropriate inputs. The goal is to uncover flaws in error handling, security measures, and overall system robustness.

Endurance Testing:

Term	Definition
Endurance Testing	- Definition: Endurance testing, also known as endurance or longevity testing, evaluates the system's capability to handle a sustained workload over an extended period. The goal is to identify performance degradation or issues related to long-term usage.
	- Elaboration: Endurance testing involves simulating real-world usage scenarios for an extended duration, ensuring the system can operate continuously without memory leaks, performance degradation, or resource exhaustion.

Spike Testing:

Term	Definition
Spike Testing	- Definition: Spike testing assesses how well a system can handle sudden, significant increases in load or traffic to determine its scalability and ability to recover from unexpected spikes in usage.
	- Elaboration: This testing involves subjecting the system to rapid and substantial load increases, identifying potential bottlenecks, resource limitations, or issues related to handling sudden bursts of activity.

Component Testing:

Term	Definition
Component Testing	- Definition: Component testing is a phase in the software testing process where individual components or modules of a system are tested in isolation, aiming to ensure each component functions correctly and meets its specified requirements.
	- Elaboration: Focused on verifying the functionality of individual parts of a software application, component testing is carried out to identify and address defects within specific modules before integration into the complete system.

In summary, negative testing evaluates how the system handles invalid inputs, endurance testing assesses long-term performance, spike testing checks scalability under sudden load increases, and component testing ensures the correctness of individual modules. Integrating these testing approaches contributes to building robust and reliable software systems.