QualiTest shares a few tips about getting the most out of your web testing. Web applications are some of the most client-exposed content a company can have today. With potentially unlimited amount of users, you will want to ensure you always have a application that is effective and represents your company in a good light. We've focused on steps and areas you should include when considering the test process for any web application. For more information, visit us at: www.QualiTestGroup.com

1. Cheating your way through
WebTesting

2. About
QualiTest
QA and testing is
all that we do!
World’s 2nd
largest pure play
Testing
Company
Over 2,700 testing
professionals
world wide
Business
Assurance
QA &
Testing
Focus
Results
Based
Testing
(RBT)
Contractual guarantees for
quality Improvement &
cost reduction
Managed
Testing
Solutions
(MTS)
Long term, SLA
based testing
outsourcing
Industry & Technology Expert
3
Global
Service
Delivery
Model
Onshore, Near-Shore,
Offshore and Crowd
Testing

3. Cheating
yourWay
throughWeb
Testing
| Web applications are possibly one of the most visible and
impacting types of software that we test.With potentially
unlimited users, a comprehensively tested web application can be
the difference between losing or gaining clients.
4

4. WebTesting
Checklist
| The following 10 categories cover the most critical items in
making sure that a web application is ready to be deployed:
5
Effectiveness
& Efficiency
Orientation &
Navigation
Flexibility &
User
Stick to the
“RealWorld”
Recognition
Rather than
Recall
Error
Management
FeedbackConsistency
Visual design
& aesthetics
Accessibility

5. Effectiveness
and Efficiency
| Users of the system must be able to efficiently achieve the tasks
they attempt with the system in minimal time with appropriate
level of cognitive effort
6

6. Orientation
and
Navigation
| Users must always know where they are in the system or process,
how to return to previous steps and what steps can be taken next
7

7. Flexibility
and User
| Users should be allowed to conduct tasks in a flexible way.They
should be able to work in a way that suits them the most
depending on individual situations, including stopping and
returning to work as needed and not being forced to follow rigid
paths
8

8. Stick to the
“Real World”
| The system should speak the users’ language, with words,
phrases and concepts familiar to the user, rather than system-
oriented terms. Users should be able to complete system tasks in
a similar way to offline tasks. Grouping of items should suit the
way users think and need to use
9

9. Recognition
Rather than
Recall
| The user should not have to remember information from one part
of the dialogue to another.
| Minimize the user’s memory load by making the following visible:
10
Objects Actions Options

10. Error
Management
| The system should support users in three areas of error
management
11
Avoiding Error
Identifying an error has
occurred
Allowing users to
recover from error

11. Feedback
| The system should always keep users informed about what is
going on, through appropriate feedback within reasonable time
12

12. Consistency
| Consistency allows users to learn new systems or parts of systems
easily, based on their previous experiences. It minimizes cognitive
load as they do not have to wonder if different words, situations or
actions mean similar or different things.The system should be
internally consistent and consistent with platform standards
13

13. Visual
Design &
Aesthetics
| The application should be attractive!
14

14. Accessibility
| The application should be accessible for people with disabilities
15

15. Needs
| Depending on size, complexity, and corporate policies, modify the
steps to meet your specific web application testing needs
16

16. www.QualiTestGroup.com