Functional and Non-Functional requirements in software testing
Functional and Non-Functional
requirements in software
testing
Functional Requirements are specific user demands
defining basic system facilities.
Non-functional Requirements, also known as
non-behavioural requirements, ensure quality and adhere to project contracts.
They encompass aspects such as Portability,
Security, Maintainability, Reliability, Scalability, Performance, Reusability,
and Flexibility.
Load
testing assesses system performance under
real-world stress, identifying bottlenecks and user/transaction limits.
Beta
Testing involves real users testing in a live
environment, part of User Acceptance Testing.
Accessibility
Testing checks if the system behaviour aligns
with specified requirements.
Installation
Testing reviews installation procedures,
including updates, uninstallation, and reinstallation.
Non-functional
Testing confirms system behaviour aligns with
requirements.
Stress
Testing analyses system behaviour
post-failure, ensuring recovery, functionality under abnormal conditions, and
proper error handling.
Gray Box Testing
involves partial knowledge of the internal workings of a system during testing.
Acceptance Testing
ensures the system meets user requirements.
Scalability Testing
assesses how the application scales with increasing workload, user limits,
client-side degradation, and server-side robustness.
1. Study
project documentation.
2. Examine
the Application Under Test (AUT).
3. Design
test cases covering all documentation requirements.
4. Review
and baseline test cases with the team lead and client.
5. Execute
test cases on the AUT.
6. Report
bugs.
7. After
bug fixes, re-execute failing test cases for verification.
Comments
Post a Comment