what is the FURRRPSC model?

Question Posted / jaipal reddy

2 Answers
7273 Views
CTS, I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

what is the FURRRPSC model?..

Answer / shilpa

F - Functionality Testing
U - Usability Testing
R - Reliability Testing
R - Regression Testing
P - Performance Testing
S - Scalability Testing
C - Compatibility Testing

1)Functionality Testing

To conform that all the requirements are covered.
Functional requirements specify which o/p should be
produced from the given i/p. They describe the relationship
between Input and Output of the system.
A major part in black box testing is called functional
testing
Eg:
Here we test…
Input domain -- (whether taking right values of i/p or not)
Error handling -- (whether the application reporting to
wrong data or not)
URL’s checking – (for only web application, all links are
correcting working or not)

Testing Approach:
Equivalence class
Boundary value analysis
Error guessing

2)Usability Testing:
To test the ease (comfort, facility) and user-friendliness
of the system.
Approach:

Qualitative and quantitative Heuristic Check List.
Classifications of checking:
Accessibility
Clarity of communication
Consistency
Navigation
Design & maintenance
Visual representation
Qualitative approach

i.Each and every function should be available from all the
pages of the site.
ii.User should be able to submit request within 4-5 actions.
iii.Confirmation message should be displayed for each
submits.

Quantative approach:

The average of 10 different people should be considered as
the final result.
Eg:
Some people may feel the system is more users friendly, if
the submit button is on the left side of the screen. At the
same time some others may feel its better if the submit
button is placed on the right side.

3)Reliability Testing

Which defines how well the software meets its requirements?

Objective is to find mean time between failure/time
available under specific load pattern and mean for recovery.

Eg:
23 hours/day availability & 1 hour for recovery (system).
City bank – have 4 servers in each region. Every 6 hrs. It
will change servers.
Approach
RRT (Ration Real time tool)

4)Regression Testing

To check the new functionalities have been incorporated
correctly without failing the existing functionalities.

Approach: Automation Tool.

The bugs need to be communicated and assigned to developers
that can fix it. After the problem is resolved, fixes
should be re-tested, and determination mode regarding
requirements for regression testing to check that fixes did
not create problems else where.

5)Performance Testing

Primary objective of the performance testing is “ To
demonstrate the system functions to specifications with
acceptable response times while processing the required
transaction volume on a production sized data base.
Objectives:
Assessing the system capacity for growth.
Identifying weak points in the architecture.
Detect obscure bugs in the software.

Performance parameters;

Request – response time
Transactions per second
Turn around time
Page down load time
Through put
Approach:
Classification of performance testing.
Load test
Volume test
Stress test
Stress testing:

Finding break point of application. Max. No. of users that
an application can handle(at the same time)

Approach:

RCQE
Repeatedly working on the same functionality.
Critical Query Execution.
To emulate peak load.

Volume testing:

Execution of our application under huge amounts of
resources is called volume testing.
To find out threshold point we may use this test
Approach: Data Profile.

Load testing:

With the load that customer wants ( not at the same time) .
Load is increasing continuously till the customer is
required load.

Gradually increasing the load on the application and
checking the performance.

Approach: Load profile.

6)Scalability testing:

To find the maximum number of user system can handle.
(Customer will give max. no.)

Approach: performance tools.

Classification:
Network scalability
Server scalability
Application scalability
7) Compatibility testing:

How a product will perform over a wide range of hardware,
software & network configuration and to isolate the
specific problems.

Approach: ET Approach.

Environment Selection:
Understanding the end users application environment.
Importance of selecting both old browser & new browser.
Selection of the operating system.

Read more: http://www.testingfinder.com/2009/10/furrpsc-
model-types-of-testing.html#ixzz0mw2OVKSO

Is This Answer Correct ?

2 Yes

0 No

what is the FURRRPSC model?..

Answer / rahul swami

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

Is This Answer Correct ?

0 Yes

5 No

Post New Answer