Complexity is a factor considering the architecture of a web application and of which components it is built. Aim is a combination between purpose and target group, considering what you mean to achieve with the application.
The test types are:
- Server side interface
- Client side compatibility
To separately consider all areas where errors might occur we applying a risk-based approach, where complexity is likelihood of an error to occur and aim is impact, or cost, of an error. For each area under the test types there are two questions to answer, one for each factor. For example, Forms is an area under functionality where the following questions are to be answered:
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?
Further, tools for automating tests have been evaluated. Two types of tools were evaluated. First, tools for mainly functional tests, and second, tools for performance tests. The tools are used for script creation, script execution and result analysis.
Functional testing tools are mainly used for regression tests, since when a test has been made, it can be rerun with minimal manual effort. Performance testing tools are used in order to evaluate how the tested application reacts to high numbers of simultaneous users. The tool simulates a number of actual users and captures and displays data on the performance of the site.
The most basic web site. Presentation of HTML-documents. The only interactivity offered is the choice of page by clicking links.
· Static with Form-Based interactivity
Forms are used collecting information from the user, including comments or requests for information. Main purpose is document delivery, limited emphasis on data collection mechanisms.
· Sites with Dynamic Data Access
web site used as front-end for accessing a database. Via the web page users can search a catalogue or perform queries on the content of a database. The results of the search are displayed as HTML-documents.
· Dynamically Generated Sites
The wish to provide customized pages for every user creates a need to take a step away from the static web site. The page presented may be static, providing no interactivity, but the way it was created has similarities with the way screens are created in software applications.
Web-Based Software Applications
Web sites that are part of the business process often have more in common with other client/server applications than with static web sites. This could be a inventory tracking system or a sales force automaton tool.
When publishing a web site the construction and design, of course, is based upon what you hope to achieve with the site. Depending on this, the site may be classified as a certain type of site. There are a number of different types of sites published on the web. These sites have been categorized by a number of authors. We have chosen two different classifications that we believe in a clear way show the different angels from which to view the sites.
The first classification is based on the different business purposes of a commercial web site. purposes of commercial web sites into three categories:
· Promotion of products and services
· Provision of data and information
· Processing of business transactions
Promotion is information about products and services that are part of the company’s business, whereas provision is information about, for instance, the environmental care program the company may sponsor. Processing refers to regular business transactions.
Another classification is based on the degree of interactivity the web site offers.
UNIT TESTING PART ONE
UNIT TESTING PART TWO
UNIT TESTING PART THREE
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
TESTING CONDITIONS PART ONE
TESTING CONDITIONS PART TWO
TESTING CONDITIONS PART THREE
TESTING CONDITIONS PART FOUR
SPECIFIC FIELD 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