User Manual for web testing

Step-by-Step

Before starting to use the Test Priority Sheet you need to establish certain factors. You need to be familiar with the following:

  1. Complexity (architecture, components)

  2. Aim (purpose, target group)

There are two questions presented under each test area below. The first is to be answered under Complexity and the second under Aim.

Multiply the values on the same row with each other and put the product under Testing Need. Do this for all rows.

Result

Compare the values in the Testing Need column with each other. The higher the value, the higher the testing need. If several rows have the same value, higher priority should often be given the area with the higher Aim value.

Functionality

Links:

Are links present and to what extent?

  • Are links critical and how sensitive is the target group to bad links?

Forms:

  • Are forms present? To what extent and how advanced?

  • How critical are forms for the site and how sensitive are users to problems with forms?

Cookies:

  • Are cookies used and to what extent?

  • How critical are the use of cookies?

Web Indexing:

  • How advanced and extent is the use of techniques affecting search engine indexing?

  • How severe effects will problems with web indexing have?

Programming Language:

  • To what extent are different programming languages used?

  • How critical effects can problems with Programming Language have?

Dynamic Interface Components:

  • How extent and how advanced are the use of different technologies?

  • How critical are the functions of these components and will users notice failure of these and how will they react?

Databases:

  • How complex is the database architecture?

  • How critical are databases to the aim of the application and how will users respond to failure?

Usability

Navigation:

  • How complex is the structure of the site?

  • How severe effects will difficulty of navigation have?

Graphics:

  • How extent is the use of different graphical elements?

  • How critical is the use of graphics and how sensitive will users be to problems with graphics?

Content:

  • To what extent does the site contain complex and sensitive information?

  • How severe effects will errors in the content have?

General Appearance:

  • How advanced is the site layout?

  • How sensitive are users to poor appearance?

Server side Interface

Server Interface:

  • How complex is the architecture?

  • How critical information is dependant on communication between different servers?

External Interface:

  • How complex is the architecture?

  • How critical information is dependant on communication with external servers?

Client side Compatibility

Platform:

  • To what extent does the site contain features with possible platform compatibility problems?

  • To what extent may users differ in platforms and how critical effects will compatibility issues have?

Browsers:

  • To what extent does the site contain features with possible browser compatibility problems?

  • To what extent may users differ in browsers and how serious effects will compatibility issues have?

Settings:

  • To what extent does the site contain features sensitive to different settings?

  • To what extent may users differ in settings?

Printers:

  • To what extent does the site contain information that requires printing capability?

  • To what extent may users differ in configuration and how frequently will they print?

Performance

Connection Speed:

  • To what extent are there features on the site sensitive to connection speed?

  • To what extent will users differ in connection speed and how sensitive will they be to bad performance?

Load:

  • Are there features on the site that are sensitive to high loads?

  • Will the presence of users reach high load levels?

Stress:

  • Are there features on the site that are sensitive to stress situations?

  • How likely is it that stress situations will occur and how severe effects may it cause?

Continuous use:

  • Are there features on the site that are sensitive to continuous use?

  • Will the site or feature be continuously used and what will be the effects of problems of the feature?

Security

General security:

  • How advanced is the security?

  • How critical is the security of the site?

RELATED POST

UNIT TESTING PART ONE

UNIT TESTING PART TWO

UNIT TESTING PART THREE

GUI TESTING

WINDOWS COMPLIANCE GUI TESTING PART ONE

WINDOWS COMPLIANCE GUI TESTING PART TWO

WINDOWS COMPLIANCE GUI TESTING PART THREE

WINDOWS COMPLIANCE GUI TESTING PART FOUR VALIDATION TESTING

WINDOWS COMPLIANCE GUI TESTING PART FIVE CONDITION TESTING

WINDOWS COMPLIANCE GUI TESTING PART SIX GENERAL CONDITION TESTING

CONDITION TESTING

TESTING CONDITIONS PART ONE

TESTING CONDITIONS PART TWO

TESTING CONDITIONS PART THREE

TESTING CONDITIONS PART FOUR

SPECIFIC FIELD TESTING

USABILITY TESTING

INTEGRATION TESTING

INTEGRATION TESTING PART ONE

INTEGRATION TESTING PART TWO

INTEGRATION TESTING PART THREE

INTEGRATION TESTING PART FOUR

INTEGRATION TESTING PART FIVE

INTEGRATION TEST STANDARDS

INTEGRATION TEST STANDARDS PART TWO


No comments:

Post a Comment