This will include- Scripting checks on the form are working as expected. For example- if a user does not fill a mandatory field in a form an error message is shown. Cookies are small files used by websites to primarily remember active user sessions so you do not need to log in every time you visit a website.
The following 10 steps cover the most critical items that I have found important in making sure a web application is ready to be deployed. Depending on size, complexity, and corporate policies, modify the following steps to meet your specific testing needs.
Step 1 - Objectives Make sure to establish your testing objectives up front and make sure they are measurable. It will make your life a lot easier by having written objectives that your whole team can understand and rally around.
In addition to documenting your objectives, make sure your objectives are prioritized. Ask yourself questions like "What is most important: If you are building a medical web application that will assist in diagnosing illnesses, and someone could potentially die based on how correctly the application functions, you may want to make testing the correctness of the business functionality a higher priority than testing for navigational consistency throughout the application.
If you are testing an application that will be used to solicit external funding, you may want to put testing the aspects of the application that impact the visual appeal as the highest testing priority. Step 2 — Process and Reporting Make sure that everyone on your testing team knows his or her role.
Who should report what to whom and when? In other words, define your testing process. Use the following questions to help you get started: How will issues be reported? Who can assign issues?
How will issues be categorized? Who needs what report and when do they need it?
Are team meetings scheduled in advance or scheduled as needed? You may define your testing process and reporting requirements formally or informally, depending on your particular needs.
The main point to keep in mind is to organize your team in a way that supports your testing objectives and takes into account the individual personalities on your team. One size never fits all when dealing with people.
Step 3 - Tracking Results Once you start executing your test plans, you will probably generate a large number of bugs, issues, defects, etc. You will want a way to easily store, organize, and distribute this information to the appropriate technical team members.
You will also need a way to keep management informed on the status of your testing efforts. By using an online system, you can make it much easier on yourself by eliminating the need to install and maintain an off-the-shelf package. Step 4 - Test Environment Set up a test environment that is separate from your development and production environment.
This includes a separate web server, database server, and application server if applicable. You may or may not be able to utilize existing computers to setup a separate test environment.
Create an explicitly defined procedure for moving code to and from your test environment and make sure the procedure is followed. Also, work with your development team to make sure each new version of source code to be tested is uniquely identified.
How easy is it to navigate through your web application? Is it obvious to the user which actions are available to him or her? Is the look-and-feel of your web application consistent from page to page, including font sizes and colors?
I refer to it often, and recommend it highly. In addition to the traditional navigation and look-and-feel issues, Section compliance is another area of importance.
The Amendment to Section of the Rehabilitation Act spells out accessibility requirements for individuals with certain disabilities.
For instance, if a user forgets to fill in a required field, you might think it is a good idea to present the user with a friendly error message and change the color of the field label to red or some other conspicuous color.
However, changing the color of the field label would not really help a user who has difficulty deciphering colors. The use of color may help most users, but you would want to use an additional visual clue, such as placing an asterisk beside the field in question or additionally making the text bold.
For more details, refer to http:Testers should test the Web-based application on different browsers to make sure that the application behavior is consistent on all the browsers.
Functional testing The functionality of the application like, calculation, business logic, validation links and navigation should be proper. How to Develop Test Cases and Test Scripts for Web Testing Print; Email; Details Written by Randall Rice Some processes delivered via a web-based application are very predictable.
The user points and clicks on objects, but there are clearly defined steps that must be completed before the process is considered complete. How to Develop. Testing a web application is not easy than testing a static website but not much difficult than testing an e-commerce website.
Functionality testing is the most important thing to be performed while testing a . In Database testing backend records are tested which have been inserted through the web or desktop applications. The data which is displaying in the web application should match with the data stored in .
Jun 30, · Testing Web Applications Tutorial Lesson How to test web based applications class at Portnov Computer School. Web Application Testing Example Test Cases: This is a complete Testing Checklist for both web-based and desktop applications.
This is a very comprehensive list of Web Application Testing Example Test Cases/scenarios.