Академический Документы
Профессиональный Документы
Культура Документы
Testing Types
Functional testing
Non-functional testing
Recovery testing
Alpha testing
Beta testing
Confirmation testing
Regression test
Example
The Loan Management System (LMS) with
requirements:
Specific requirements:
- Client query
- Create for new loan
- Second loan Agreement, etc
Other requirements:
- Usability: training, user interface
- Reliability/Performance: availability,
performance
- Supportability
Refer to URS of LMS
Functional Testing
Test functions, focus on external behavior of
software system
Can be used in every levels of testing (UT, IT,
ST, UAT).
2 perspectives for functional testing:
Specification-based: based on what customer
required.
Usage-based: based on day-to-day business use
of system.
Exercise
List all functions, that will be tested in LMS
15 minutes to complete
need
Interoperability: interaction of the software with
other system
Security: Prevention of accidental or deliberate
unauthorized access to program and data
Accuracy: accuracy of the results provided by the
software
Compliance: compliance with standards,
conventions, regulations, law and similar rules in
relation to functionality
Function Testing
Objective: Ensure proper target-of-test
Non-functional testing
Concentrate on how well or how fast
something is done.
Also can be performed at all levels of testing
but mostly at System testing
Non-functional testing
Mostly include:
Performance testing
Load testing
Stress testing
Volume testing
Characteristics:
Usability testing: learnability, attractiveness
Maintainability testing: analyzability, changeability
Reliability testing: fault-tolerant, recoverability
Portability testing: adaptability, replaceability
Efficiency testing: resource utilization
Exercise
List all non-functions, that will be tested in LMS
15 minutes to complete
Performance Testing
Tests the performance of a system under
Load Testing
(Concurrency Testing)
Tests the systems ability to perform more
Stress Testing
Tests the performance of a system under
abnormal conditions
Determine how the performance of the system
Volume Testing
Test with large amounts of data to determine if
Recovery Testing
Tests that the system can be recovered in the event of
a failure
Types of failure that as system may need to recover
from include:
Program errors
Hardware failures (power failure etc.)
Transmission errors (noise, line disconnected, etc.)
Data errors
Testing related to
change
Confirmation testing:
Needed when there is a defect fixed or change
requirement.
Test to confirm defect has indeed fixed or new
change is correct.
Regression test:
Execute test cases that are executed before.
Test to ensure there is no defect is made due to
change of source code.
There should be a regression test suite that executed
every time a new version of source code produced
-> automation can be applied.
Conclusion
Functional testing
Non-Functional testing
Recovery testing
Alpha testing
Beta testing
Confirmation testing
Regression test