Consider a web application, any web application, but only one.
To what extent does it depend on links, forms or cookies?
Is the content valid according to the purpose of the site?
Does the site contain features sensible to slow connection speeds?
- 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
Instructions
Sitemap/nav.bar
Content
Colour/background
Images
Tables
Wrap around
Functionality
Links
Forms
Cookies
Web Indexing
Dynamic Interface Components
Programming Language
Databases
Interface testing
Server interface
External interface
Error handling
Client side Compatibility
Operating systems
Browsers
Video settings
Modem/connection speed
Printers
Combinations
Performance
Connection speed
Load
Stress
Continuous use
Security
Directory setup
SSL
Logins
Logfiles
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