0% found this document useful (0 votes)
19 views5 pages

9 Manual Testing Process

Testing process

Uploaded by

urvashi4301
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views5 pages

9 Manual Testing Process

Testing process

Uploaded by

urvashi4301
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

MANUAL TESTING PROCESS TO TEST

THE LIVE APPLICATION


What Is Web Testing?
Web testing is a software testing practice to test websites or web applications for potential
bugs. It’s a complete testing of web-based applications before making them live.
A web-based system needs to be checked completely from end to end before it goes live for
end users.

By performing website testing, an organization can make sure that the web-based system is
functioning properly and can be accepted by real-time users.

The UI design and functionality are the captains of website testing.

Web Testing Checklists

1) Functionality Testing
2) Usability testing
3) Compatibility testing
4) Performances testing
5) Security testing
6) Database testing

1. Functionality Testing

• Test all the mandatory fields should be validated.


• Test the asterisk sign should display for all the mandatory fields.
• Test the system should not display the error message for optional fields.
• Test that leaps years are validated correctly & do not cause errors/miscalculations.
• Test the numeric fields should not accept the alphabets and proper error message
should display.
• Test for negative numbers if allowed for numeric fields.
• Test division by zero should be handled properly for calculations.
• Test the max length of every field to ensure the data is not truncated.
• Test the pop-up message (“This field is limited to 500 characters”) should display
if the data reaches the maximum size of the field.
• Test that a confirmation message should display for update and delete operations.
• Test the amount values should display in currency format.
• Test all input fields for special characters.
• Test the timeout functionality.
• Test the Sorting functionality.
• Test the functionality of the buttons available
• Test the Privacy Policy & FAQ is clearly defined and should be available for
users.
• Test if any functionality fails the user gets redirected to the custom error page.
• Test all the uploaded documents are opened properly.
• Test the user should be able to download the uploaded files.
• Test the email functionality of the system.
• Test the Java script is properly working in different browsers (IE, Firefox,
Chrome, safari and Opera).
• Test to see what happens if a user deletes cookies while in the site.
• Test to see what happens if a user deletes cookies after visiting a site.
• Test all the data inside combo/list box is arranged in chronological order.

2. Usability testing

• Web page content should be correct without any spelling or grammatical errors
• All fonts should be same as per the requirements.
• All the text should be properly aligned.
• All the error messages should be correct without any spelling or grammatical
errors and the error message should match with the field label.
• Tool tip text should be there for every field.
• All the fields should be properly aligned.
• Enough space should be provided between field labels, columns, rows, and error
messages.
• All the buttons should be in a standard format and size.
• Home link should be there on every single page.
• Disabled fields should be grayed out.
• Check for broken links and images.
• Confirmation message should be displayed for any kind of update and delete
operation.
• Check the site on different resolutions (640 x 480, 600×800 etc.?)
• Check the end user can run the system without frustration.
• Check the tab should work properly.
• Scroll bar should appear only if required.
• If there is an error message on submit, the information filled by the user should be
there.
• Title should display on each web page
• All fields (Textbox, dropdown, radio button, etc) and buttons should be accessible
by keyboard shortcuts and the user should be able to perform all operations by
using keyboard.
• Check if the dropdown data is not truncated due to the field size. Also, check
whether the data is hardcoded or managed via administrator.

3. Compatibility testing

• Test the website in different browsers (IE, Firefox, Chrome, Safari and Opera) and
ensure the website is displaying properly.
• Test the HTML version being used is compatible with appropriate browser
versions.
• Test the images display correctly in different browsers.
• Test the fonts are usable in different browsers.
• Test the java script code is usable in different browsers.
• Test the Animated GIFs across different browsers.

4. Performances testing

• To determine the performance, stability and scalability of an application under


different load conditions.
• To determine if the current architecture can support the application at peak user
levels.
• To determine which configuration sizing provides the best performance level.
• To identify application and infrastructure bottlenecks.
• To determine if the new version of the software adversely had an impact on
response time.
• To evaluate product and/or hardware to determine if it can handle projected load
volumes.

5. Security testing

• Verify the web page which contains important data like password, credit card
numbers, secret answers for security question etc should be submitted via HTTPS
(SSL).
• Verify the important information like password, credit card numbers etc should
display in encrypted format.
• Verify password rules are implemented on all authentication pages like
Registration, forgot password, change password.
• Verify if the password is changed the user should not be able to login with the old
password.
• Verify the error messages should not display any important information.
• Verify if the user is logged out from the system or user session was expired, the
user should not be able to navigate the site.
• Verify to access the secured and non-secured web pages directly without login.
• Verify the “View Source code” option is disabled and should not be visible to the
user.
• Verify the user account gets locked out if the user is entering the wrong password
several times.
• Verify the cookies should not store passwords.
• Verify if, any functionality is not working, the system should not display any
application, server, or database information. Instead, it should display the custom
error page.
• Verify the SQL injection attacks.
• Verify the user roles and their rights. For Example, the requestor should not be
able to access the admin page.
• Verify the important operations are written in log files, and that information
should be traceable.
• Verify the session values are in an encrypted format in the address bar.
• Verify the cookie information is stored in encrypted format.
• Verify the application for Brute Force Attacks

6. Database Testing

• Verify the database name: The database name should match with the
specifications.
• Verify the Tables, columns, column types and defaults: All things should match
with the specifications.
• Verify whether the column allows a null or not.
• Verify the Primary and foreign key of each table.
• Verify the Stored Procedure:
• Test whether the Stored procedure is installed or not.
• Verify the Stored procedure name
• Verify the parameter names, types and number of parameters.
• Test the parameters if they are required or not.
• Test the stored procedure by deleting some parameters
• Test when the output is zero, the zero records should be affected.
• Test the stored procedure by writing simple SQL queries.
• Test whether the stored procedure returns the values
• Test the stored procedure with sample input data.
• Verify the behaviour of each flag in the table.
• Verify the data gets properly saved into the database after each page submission.
• Verify the data if the DML (Update, delete and insert) operations are performed.
• Check the length of every field: The field length in the back end and front end
must be same.
• Verify the database names of QA, UAT and production. The names should be
unique.
• Verify the encrypted data in the database.
• Verify the database size. Also test the response time of each query executed.
• Verify the data displayed on the front end and make sure it is same in the back
end.
• Verify the data validity by inserting the invalid data in the database.
• Verify the Triggers.

You might also like