Testing Methods – FURRPSC Model
Functionality Testing:
Objective: 
1.	Test against system requirements.
2.	To confirm all the requirements are covered.
Approach:
Equivalence Class

Boundary Value Analysis
Error Guessing.

Usability Testing:
To test the Easiness and User-friendliness of the system.
 Approach:
Qualitative & Quantitative
Qualitative Approach:

1.	Each and every function should available from all the
pages of the site.
2.	User should able to submit each and every request with in
4-5 actions.
3.	Confirmation message should be displayed for each and
every submit.

Quantitative Approach:
Heuristic Checklist should be prepared with all the general
test cases that fall under the classification of checking. 
This generic test cases should be given to 10 different
people and ask to execute the system to mark the pass/fail
status.
The average of 10 different people should be considered as
the final result.
Example: Some people may feel system is more users friendly,
If the submit is button on the left side of the screen. At
the same time some other may feel its better if the submit
button is placed on the right side.

Classification of Checking:
Clarity of communication.
Accessibility
Consistency
Navigation
Design & Maintenance
Visual Representation.

Reliability Testing:

RT is property, which defines how well the software meets
its requirements.
Objective is to find Mean Time between failure/time
available under specific load pattern. Mean time for recovery.

Approach: RRT (Rational Real Time) for continuous hours of
operation.
More then 85% of the stability is must.
Reliability Testing helps you to confirm:
Business logic performs as expected
Active buttons are really active
Correct menu options are available
Reliable hyper links