9 Manual Testing Process
9 Manual Testing Process
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.
1) Functionality Testing
2) Usability testing
3) Compatibility testing
4) Performances testing
5) Security testing
6) Database testing
1. Functionality Testing
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
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.