Testing Applications on the Web Introduction

1
Testing Applications on the WebIntroduction
2
Web Testing

• Plans are needed for Web Testing
• Software testing for the web has improved
• Fixed locations
• Desktops
• Mobile Clients
• Phones, PDAs, Portable Computers, Wireless
• Software quality costing more
• More configurations interactions to examine

3
Testing Software for the Web

• What is necessary?

4
Introduction

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

5
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
  

6
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?

7
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

8
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

9
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

10
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