Practical No.

Aim: Design test cases for Web Pages Testing any Web Sites

Theoretical Background

Website testing is a process to test a website or any web app which is deployed
on the internet which is aiming to identify potential bugs. This testing is done before
hosting the website and making it available globally. All web-based systems/
applications are required to be verified and validated in all aspect before it is hosted
on the internet. While performing website testing one must perform certain tests like
functionality testing, usability testing, interface testing, compatibility testing
performance testing, and most important is security testing. One of the crucial
modules which are required to be tested is linking between pages and also the
performance of the system because of its availability.

Procedure:
1. Select appropriate tool to generate test case(Like any text editor/web-based
tool)
2. Identify required modules of the system which is to be tested.
3. Identify required parameters such as test data, expected data, etc.
4. Prepare and generate a test case.
5. Verify test cases as per the specification by executing test data on specified
website/web application(s).

Resources Required

Sr. No Name of Specification Quantity Remarks

Resource

1. Hardware: Computer
For all
Computer System System
As per batch Practical of
Computer (i3-
size Test Case
i5 preferable),
Generation
RAM minimum
 2 GB and
onwards, HDD
free Space 1GB
or More
2. Operating system Windows 7 or
latest/LINUX
version 5.0 or
later
3. Software Any Word
Processing tool
such as Libre
Office, Open
Office. Any
web-
application/
website

Test cases for web pages of website

Testing of the To-do list website

1. Login page

Sr. Action Inputs Expected Actual Test

No. Output Output Result
For correct Username :
Message -
1. credentials/usernam mohan4554 Message - Login Pass
Login
e and password the Password: success!!!
success!!!
user must be log in m@han1090
 For incorrect Message -
Username : Message - Wrong
credentials/usernam Wrong
2. mohna4000 username or Pass
e and password the username or
Password: password is incorrect
webpage must password is
mahan1910 !!!
prompt the message incorrect!!!
Login button
is Message - Wrong
Should be log in Message -
3. clicked(After username or Fail
after clicking login Login
submitting password is incorrect
button success!!!
correct !!!
credentials)
Sign up
Username is already Message -
button is
registered but still Account Message - Account
4. clicked(After Pass
trying to register, already already registered !!
submitting
the webpage must registered !! Try to Log in
correct
prompt the message Try to Log in
credentials)
Account should get Sign up
Message -
5. created after button is Message - Pass
Account
clicking Sign up clicked (For Account created !!!
created !!!
button new user)

Output:
2. Home page

Sr. Action Inputs Expected Actual Test

No. Output Output Result
1. To add users Steps: The Task which The Task which Pass
task in task 1. Enter the task was inserted was inserted is
category in text box
2. Select the should be displayed in Task
category displayed in Task panel
Tasks
3. Click on add panel
button
2. To add users Steps: The Note which The Note which Pass
notes in notes 4. Enter the Note was inserted was inserted is
category in text box
5. Select the should be displayed in
category displayed in Notes Notes panel
Notes
6. Click on add panel
button
3. To delete a Click on trash The Note or Task The Note or Task Pass
task or note button should be deleted is deleted
Exercises:
1. Give significance of performance and stress for web application.
• Performance tests help identify these performance issues, bugs, and errors, after
which developers can decide what they need to do to ensure the system will
perform well under the expected workload. Without proper testing, you are
likely to face slowdowns, inconsistencies across different OS, and poor
usability when the number of online customers grows.
• The significance of Stress tests is to evaluate the problems that exist only when
the system is overloaded and the system can be recovered reliably. For
example, stress testing can provide you an idea of how the device responds, and
reveals any points of fault, in the ( ideally, improbable) case of a Denial of
Service (DoS) assault.

2. What is necessity of configuration testing? Describe various configuration

that are required to be considered while website testing.
Configuration Testing is a testing method of software in order to determine the
functional specifications and to find ideal setups under which the software
application operates without requiring the use of several combinations of software
and hardware.
During the website testing the possible configurations required are as follows:
• Configuration of the Web browser:
The best web browser for testing should be available. It should help all the new
HTML tags and Css properties to make the website look beautiful.
• Rich Internet:
If the website is hosted on the internet, testing includes a rich internet for proper
and proper testing.
• Plugins:
Web Testing - Basic web testing plugin. Enables web testing using Internet
Explorer, Edge and applications with the WebBrowser control. Provides support
for standard HTML controls, JavaScript popups and browser dialogs.
 Firefox Support - Enables web testing using Mozilla Firefox. Provides support for
XUL controls in Gecko-based applications.
Chrome Support - Enables web testing using Google Chrome and the latest
versions of Microsoft Edge (Chromium-based).
Chromium Embedded Framework Support - Enables web testing in applications
created with Chromium Embedded Framework (CEF) or Electron.
Web Checkpoints - Provides web accessibility and web comparison checkpoints for
verifying web pages.

3. Describe various security testings to be performed for web applications. Give

its importance.
Security Testing is a kind of software test that exposes weaknesses, hazards, risks
and avoids intrusive malicious attacks in software applications. The purpose of
security tests is to detect any potential software loopholes or weaknesses that may
lead to information loss, income, credibility by the Organization's employees or
outsiders.
1) Cracking the password
If a web application does not implement a complicated password (for example,
with alphabets, numbers and special characters or at least the minimum number of
characters), it does not take a long time to crack the username and password.
If a username or password is stored in cookies without encryption, an attacker can
use a variety of methods to steal cookies and information stored in cookies, such as
username and password.

2) URL exploitation by means of HTTP GET methods

The tester can verify whether or not the application passes crucial details in the
question string. This occurs when the application uses the HTTP GET method to
transfer information between the client and the server.
 3) Injection to SQL
The next element to be tested is SQL Injection. The application should deny the
entry of a single quotation (') in every text box. Instead, if the tester finds a
database error, this means that the user input is incorporated into a query that is
then executed by an application. In such a case, the program is vulnerable to
injection of SQL.

4) Cross-Site Scripting (XSS)

A tester should additionally check the web application for XSS (Cross-site
scripting). Any HTML For Example, <HTML> or any script For Example,
<SCRIPT> should not be accepted by the application. If it is, then the application
can be prone to an attack by Cross-Site Scripting.

Conclusion: Hence, we successfully design test cases for Web Pages Testing any Web
Sites.