Experiment No.

Title :- Web Application Testing Complete Guide (How To Test A Website).

Objective :- To familiarize with the concept of structured charts

S/W Requirement :- Smart Draw

H/W Requirement :-
• Processor – Any suitable Processor e.g. Celeron

• Main Memory - 128 MB RAM

• Hard Disk – minimum 20 GB IDE Hard Disk

• Removable Drives–1.44 MB Floppy Disk Drive

–52X IDE CD-ROM Drive

•PS/2 HCL Keyboard and Mouse

METHOD:

Web testing is the name given to software testing that focuses on web applications. Complete testing of a we

Documentation testing

We should start with the preparatory phase, testing the documentation. The tester studies the received docum

The main artifacts related to the website testing are analyzed on this stage:

 Requirements
 Test Plan
 Test Cases
 Traceability Matrix.

Functionality Testing

1
Functionality Testing of a Website is a process that includes several testing parameters like
user interface, APIs, database testing, security testing, client and server testing and basic website
functionalities. Functional testing is very convenient and it allows users to perform both manual
and automated testing. It is performed to test the functionalities of each feature on the website.

Web based Testing Activities includes:

Test all links in your webpages are working correctly and make sure there are no broken links.
Links to be checked will include -

 Outgoing links
 Internal links
 Anchor Links
 Mail To Links

Test Forms are working as expected. 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.
 Check default values are being populated
 Once submitted, the data in the forms is submitted to a live database or is linked to a
working email address
 Forms are optimally formatted for better readability

Test Cookies are working as expected. 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.
Cookie Testing will include

 Testing cookies (sessions) are deleted either when cache is cleared or when they reach
their expiry.
 Delete cookies (sessions) and test that login credentials are asked for when you next visit
the site.

Test HTML and CSS to ensure that search engines can crawl your site easily. This will include

 Checking for Syntax Errors

 Readable Color Schemas
 Standard Compliance. Ensure standards such W3C, OASIS, IETF, ISO, ECMA, or WS-I
are followed.

Test business workflow- This will include

 Testing your end - to - end workflow/ business scenarios which takes the user through a
series of webpages to complete.

2
  Test negative scenarios as well, such that when a user executes an unexpected step,
appropriate error message or help is shown in your web application.

Usability Testing has now become a vital part of any web-based project. It can be carried out by
Usability testing
testers like you or a small focus group similar to the target audience of the web application.

Test the site Navigation:

 Menus, buttons or Links to different pages on your site should be easily visible and
consistent on all webpages.

Test the Content:

 Content should be legible with no spelling or grammatical errors.

 Images if present should contain an "alt" text

UI (User Interface) testing

User Interface (UI) testing is provided to verify the graphic user interface of your
website meets the specifications.
Compatibility (Configuration) testing
Here are some verifications
Cross-platform for UI
testing allows testing of
evaluating thea work
website:
Compatibility (Configuration) testing is performed tooftest
your sitewebsite
your in different
with OS (both
each one of
desktop and mobile): Windows, iOS/Mac OS,
the supported software and hardware configurations: Linux, Android, and BlackBerry etc.
 Compliance with the standards of graphical interfaces
46
 Design elements evaluation: layout, colors, fonts, font sizes, labels, text boxes,
 OS Configuration
text formatting, captions, buttons, lists, icons, links
 Browser Configuration
Testing with different screen resolutions
 Database Configuration
Testing of localized versions: accuracy of translation (multilanguage,
multicurrency), checking the length of names of interface elements, etc.
 Testing the graphical user interface on target devices: smartphones and tablets.
 Cross-browser website testing methods help to verify the correct work of the site in
different browser configurations: Mozilla Firefox, Google Chrome, Internet Explorer, and
Opera etc.
Database Testing:
Database is one critical component of your web application and stress must be laid to test it
thoroughly. Testing activities will include-

 Test if any errors are shown while executing queries

 Data Integrity is maintained while creating, updating or deleting data in database.
 Check response time of queries and fine tune them if necessary.
 Test data retrieved from your database is shown accurately in your web application

Performance testing
This will ensure your site works under all loads. Software Testing activities will include but not
limited to -

 Website application response times at different connection speeds

 Load test your web application to determine its behavior under normal and peak loads
 Stress test your web site to determine its break point when pushed to beyond normal
loads at peak time.
 Test if a crash occurs due to peak load, how does the site recover from such an event
 Make sure optimization techniques like gzip compression, browser and server-side cache
enabled to reduce load times

Security testing

Security Testing is vital for e-commerce website that store sensitive customer information like
credit cards. Testing Activities will include-

 Test unauthorized access to secure pages should not be permitted

 Restricted files should not be downloadable without appropriate access
 Check sessions are automatically killed after prolonged user inactivity
 On use of SSL certificates, website should re-direct to encrypted SSL pages.

RESULT: This experiment introduces the concept Testing a web application.

47