Types of Web Applications Presentation-oriented A presentation-oriented Web application generates dynamic Web pages containing various types of markup

language (HTML, XML, and so on) in response to requests Service-oriented A service-oriented Web application implements the endpoint of a fine-grained Web service Service-oriented Web applications are often invoked by presentation-oriented applications Web services are services offered via the Web In a typical Web services scenario, a business application sends a request to a service at a given URL using the SOAP protocol over HTTP _________________________ Testing and the web

Web Applications are error prone mostly because anyone can develop them they are mostly distributed

Testing of Web Applications: manual or using dedicated tools The NEED to Test: Is the UI content meaningful? Is this application easy to use? How about browser compatible? Are we using the right tools? How reliable is our technology? Do the Servers have enough power? How many visitors are we expecting? Are the machines fast enough?

______________ "Web time" There is no customer loyalty on the Net Your competition is only a click away Web customers tend to be sticky Once they move, they dont come back until their new e-tailer has some problems ____ Costs of quality and testing Testing can be considered an investment. The process of negotiating a software testing budget can be painful. Smart software managers understand that testing is an investment in quality

 _________ Costs of quality and testing A technique of analyzing the costs of quality Start by breaking down the costs of quality as follows: Cquality = Cconformance + Cnon-conformance C conformance = Prevention costs + Appraisal costs. Prevention costs = Money spent on quality assurance - tasks like training, requirements and code reviews + other activities that promote good software. Appraisal costs = Money spent on planning test activities + developing test cases and data + executing those test cases once. _________ Costs of quality and testing Cnon-conformance = Internal failures + External failures. The costs of internal failure include all expenses that arise when test cases fail the first time theyre run, as they often do. A programmer incurs a cost of internal failure while debugging problems found during his/her own unit and component testing. The costs of external failure are those incurred when, rather than a tester finding a bug, the customer does. These costs will be even higher than those associated with either kind of internal failure, programmerfound or tester-found. How do web based systems fail? Web based systems fails because: The application is complex to use Not compatible with some browsers The application is very slow or hangs sometimes The application is not available Not a reliable application Does not meet the customer requirement _____________ The Testing Process Web application is a bit different and complex to test as tester dont have that much control over the application. Application is loaded on the server whose location may or may not be known and mostly no exe is installed on the client machine, you have to test it on different web browsers. ____________ The Testing Process

Web Testing Checklist: 1. Functionality Testing 2. Compatibility and Configuration Testing 3. Performance Testing 4. Security Testing 5. Usability testing

____ The Testing Process

Also worry about performance Check for Usability Focus on Browser Compatibility Model user behavior Focus on what can go wrong Focus on severity of problem Comfortable with conflict Report problems

Testers :

Usually Test the functionality Usually do not focus on usability Focus on their Browser Model system design Focus on how it can work Focus on interest in problem Avoid conflict Understand problems

Also worry about performance Check for Usability Focus on Browser Compatibility Model user behavior Focus on what can go wrong Focus on severity of problem Comfortable with conflict Report problems Also worry about performance Check for Usability Focus on Browser Compatibility Model user behavior

Focus on what can go wrong Focus on severity of problem Comfortable with conflict Report problems Usually Test the functionality Usually do not focus on usability Focus on their Browser Model system design Focus on how it can work Focus on interest in problem Avoid conflict Understand problems

Dev:

Usually Test the functionality Usually do not focus on usability Focus on their Browser Model system design Focus on how it can work Focus on interest in problem Avoid conflict Understand problems

_______

Test Design Essentials Test cases covers all features There is a balance between normal, abnormal, boundary and environmental test cases There is a balance between black box and white box testing There is a balance between functional tests and non- functional tests

Finally, documenting test cases ----_______________ What is the Good Test Case Accurate - tests what its designed to test Economical - no unnecessary steps Repeatable, reusable - keeps on going Traceable - to a requirement Appropriate - for test environment, testers Self standing - independent of the writer Self cleaning - picks up after itself ___________ What is the Good Test Case Accurate - tests what its designed to test Economical - no unnecessary steps Repeatable, reusable - keeps on going Traceable - to a requirement Appropriate - for test environment, testers Self standing - independent of the writer Self cleaning - picks up after itself _________ Test Case Mistakes Most common mistakes Making cases too long Incomplete, incorrect, or incoherent setup Leaving out a step Naming fields that changed or no longer exist Unclear what is pass or fail result Failure to clean up __________ Test Case Design Stages 58. 59. 60. 61. 62. 63. 64. Identify test resources. Identify conditions to be tested. Rank test conditions. Select conditions for testing. Determine correct results of processing. Create test cases. Document test conditions.

___________ Test Case Template In order to select the fields that we will use in our template, let us first identify all possible field choices for the template

Project Name, Test Suite ID

Version date, Version Number,

Version Author

Approval and distribution date Revision History with reasons

for update

Environment pre-requisites

(Installation & Network)

Test Pre-conditions (Data

created before testing)

Test Case Name Test Case Number Type Of Testing ( I.e. Functional,

Load etc.)

Objectives Expected Result Valid or invalid conditions Input Data ( ID type, values) Test Steps 33 Equivalence Partitioning Boundary Value Analysis Decision Table Orthogonal Arrays Cause Effect Graph

Requirement Based Testing Techniques

Equivalence Partitioning It is an organized way of designing and defining test cases. Equivalence Partitioning is the process of dividing the input domain in to the different classes (Valid and Invalid), And for a valid input class make the equal partitions so that it will reduce the no of test cases. Idea is to partition the input space into a small number of equivalence classes such that, according to the specification, every element of a given class is handled (i.e., mapped to an output) in the same manner. ________ Equivalence Partitioning Assuming the program is implemented in such a way that being handled in the same manner means that either (a) every element of the class would be mapped to a correct output, (if a test case in an equivalence class does not detect an error, then any other test case in that class should also does not detect the error.) or (b) every element of the class would be mapped to an incorrect output (if a test case in an equivalence class detects an error, then any other test case in that class should also detect.) Two types of equivalence classes The set of valid inputs to the program is regarded as the Valid equivalence class All other inputs are included in the Invalid equivalence class Equivalence Partitioning Example An input condition specifies a range of values between 4 & 10 Valid Equivalence class: 4 10 Invalid Equivalence classes: Less than 4 Greater than 10 ___________ Equivalence Partitioning Example An input condition specifies a set of values (A cloth can be Red, Green, Yellow, Violet) Valid Equivalence class: Red, Green Yellow, Violet (All valid values) Invalid Equivalence classes: Purple, Brown (Invalid values)

____________ 2009 Wipro Ltd - Confidential 38 Example The input condition is a must be situation. Like, the input string must be upper-case Valid Equivalence class: Uppercase characters Invalid Equivalence classes: All other input except uppercase characters Equivalence Partitioning

The application is expected to display the class the student has obtained after taking the input of the no. of percentage scored. The details of assigning the class specified below 0-34 Fail 35 50 - Pass 51 59 - Second class 60 69 - First class 70 100 - Distinction Equivalence Partitioning

0 34 : -1, 0, 17, 34, 35 35 50 : 34, 35, 40, 45 50, 51 51 59 : 50, 51, 55, 59, 60 60 69 : 59, 60, 63, 66, 69, 70 70 100 : 69, 70, 85, 100, 101 Totally, 27 test cases Eliminate redundant values obtained during EP

{ -1,0, 17, 33, 34, 35, 40, 45, 50, 51, 55, 59, 60, 63, 66, 69, 70, 85, 100, 101 } Totally, 20 Test Cases Equivalence Partitioning optimizes Test cases