00b introduction to testing applicaitons on the web

Testing Applications on the WebIntroduction

Web Testing

Plans are needed for Web Testing Software testing for the web has improved

Fixed locations Desktops

Mobile ClientsPhones, PDA’s, Portable Computers, Wireless

Software quality costing more More configurations interactions to examine

Testing Software for the Web

What is necessary?

Introduction

Software testing has changing objectives Gray box testing Balance of design and users perspective

Evolution of Software Testing

Increased complexity of software caused increase in complexity of testing Combination metrics grow exponentially

More and different types of testing needed Details of testing must be retained Early mainframes had users connected Now we have more independent users Technical support costs have increased

Evolution of Software Testing-2-

Important questions Which features and tests are most important? How much total testing is enough? How much risk does an unfixed bug have?

And what do you do about it? When do we not have to test components? When do we ship to market? How long should tests delay a product delivery?

Evolution of Software Testing-3-

Tracking bugs understands their nature Distributed computers require bug updates Developers are building testing into code Software is being delivered in shorter time Competitive issues undermining quality Reviews and analysis are being reduced Less time available for design, code and test

Gray Box Testing

Black Box Testing We do not know contents of software We test and acquire external performance

White box testing We know the contents and test accordingly

Gray box testing Has elements of white and black box testing Evaluates functionality and compatibility Tests are based on the knowledge of the algorithm

Real World Software Testing

Dot com Successful companies could support losers 3-5 years needed for company startup CMM is not supported by startups Companies reducing testing budgets

Goals

Understand gray box testing Plan and test your application Analyze the testing requirements Responsibilities of testers

Identify high risk areas Reduce errors Use errors to eliminate related ones

Web based testing should be platform independent