(back to Introduction article with links to all parts)
---------- Section 2 ------------
Testing Throughout The Software Life Cycles
Software development models:
- Sequential (examples: waterfall, V-model), when every stage must be completely finished before moving to the next stage,
- Iterative-incremental (examples: Rapid Application Development (RAD), Spiral (prototyping),
Scrum, Kanban);
Agile - the ability to create and respond to change in order to profit in a tough global business environment.
Agile Manifesto (defines the set of most important beliefs of what is truly important):
- People NOT Tools (Individuals and Interactions over Process and Tools),
- Value NOT Documentation (Working Software over Comprehensive Documentation),
- Flexibility NOT Negotiation (Customer Collaboration over Contract Negotiation),
- Smart Plan (Responding to Change over Following a Plan);
Scrum - agile framework with roles: scrum master, product owner (PO), the development team.
Test Levels:
1. Unit (Component) is done by Devs
2. Component Integration is done by Devs
3. System is done by Testers
4. System Integration is done by Testers
5. Acceptance (User, Operational, Contract regulation, Alpha/Beta) is done by Testers/Users
Test Types (a group of test activities aimed at testing specific characteristics):
- Functional Testing (objectives: check completeness, correcteness and suitability),
- Non-functional Testing (objectives: check security, performance, load, stress, compatibility, usability),
- White-box Testing (objectives: validate structure complete, correct),
- Change-related Testing (objectives: confirmation testing (confirming deffects have been fixed (re-testing), regression testing)
Maintenance Testing - takes place on a system which is in operation in the live environment
(can involve planned releases and unplanned releases (hotfixes)).
Impact Analysis is used for Maintenance.