Handling the Factors of software testing

Consider a web application, any web application, but only one.

  1. To what extent does it depend on links, forms or cookies?

  2. Is the content valid according to the purpose of the site?

  3. Does the site contain features sensible to slow connection speeds?

  4. How will the target group react to long download times?

For Complexity, one must consider how the application is built, of what components, both hardware and software, and the architecture of the application. Purpose is what the application is meant to achieve and Target Group is, of course, for what group, or groups, your efforts are aimed.

Functionality

  • Is the feature present - To what extent and how advanced

  • How critical is the feature for the Aim of the site

Performance

  • Does the site contain features that demand specific performance and to what extent

  • How sensitive are users to the performance of the site

First, overall testing requirements may be established using the methodology on the application as a whole. For instance, the project leader and the test leader go through the Test Priority Sheet considering the established architecture and requirements of the application.

A second step is to view the points of integration and consider what requirements that can and should be verified at those points. Integration is usually done on several levels, such as integrating single units with each other as well as putting larger systems together by integrating subsystems consisting of previously integrated units.

Third, having used the Test Priority Sheet on unit level, the project leader and test leader are able to give valid advise to developers what to test on unit level as well, even before the coding has started.

Areas to test:

User interface

  1. Instructions

  2. Sitemap/nav.bar

  3. Content

  4. Colour/background

  5. Images

  6. Tables

  7. Wrap around

Functionality

  1. Links

  2. Forms

  3. Cookies

  4. Web Indexing

  5. Dynamic Interface Components

  6. Programming Language

  7. Databases

Interface testing

  1. Server interface

  2. External interface

  3. Error handling

Client side Compatibility

  1. Operating systems

  2. Browsers

  3. Video settings

  4. Modem/connection speed

  5. Printers

  6. Combinations

Performance

  1. Connection speed

  2. Load

  3. Stress

  4. Continuous use

Security

  1. Directory setup

  2. SSL

  3. Logins

  4. Logfiles

  5. Scripting languages

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