0% found this document useful (0 votes)
18 views4 pages

Quality Assurance Checklist - Impl

The document is a quality assurance checklist that contains tests for various types of testing including usability, functional, compatibility, security, performance, regression, responsive, API, accessibility, and automation testing. The checklist contains tests to check for spelling and grammatical errors, validate fields, test sorting and buttons, check compatibility across browsers, security vulnerabilities, response times, regressions, responsiveness on different devices, API inputs and outputs, alternative text for images, keyboard shortcuts, and whether tasks can be automated.

Uploaded by

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

Quality Assurance Checklist - Impl

The document is a quality assurance checklist that contains tests for various types of testing including usability, functional, compatibility, security, performance, regression, responsive, API, accessibility, and automation testing. The checklist contains tests to check for spelling and grammatical errors, validate fields, test sorting and buttons, check compatibility across browsers, security vulnerabilities, response times, regressions, responsiveness on different devices, API inputs and outputs, alternative text for images, keyboard shortcuts, and whether tasks can be automated.

Uploaded by

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

Quality Assurance Checklist

Project Name Date Completed

Application Name Release #

Project Manager Delivery Manager

Usability Testing Yes No N/A


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 ☐ ☐ ☐
Tool tip text should be there for every field ☐ ☐ ☐
Title should display on each web page ☐ ☐ ☐

Functional Testing Yes No N/A


Test all the mandatory fields should be validated ☒ ☒ ☐
Test for negative numbers if allowed for numeric fields ☐ ☐ ☐
Test the Sorting functionality ☐ ☐ ☐
Test all the uploaded documents are opened properly ☐ ☐ ☐
Test the functionality of the buttons available ☐ ☐ ☐

Compatibility Testing Yes No N/A


Test the images display correctly in different browsers ☐ ☐ ☐
Test the fonts are usable in different browsers ☐ ☐ ☐
Test the HTML version being used is compatible with appropriate
☐ ☐ ☐
browser versions

Test the website in different browsers ☐ ☐ ☐

Security Testing Yes No N/A


Verify the application for Brute Force Attacks ☐ ☐ ☐
Verify the user account gets locked out if the user is entering the
☐ ☐ ☐
wrong password several times

Verify the error messages should not display any important


☐ ☐ ☐
information

Verify if the password is changed the user should not be able to


☐ ☐ ☐
login with the old password

Performance Testing Yes No N/A


Evaluate if the current architecture can support the application at
☐ ☐ ☐
peak user levels

Evaluate product and/or hardware to determine if it can handle


☐ ☐ ☐
projected load volumes
Evaluate if the latest version of the software adversely had an
☐ ☐ ☐
impact on response time

Evaluate application and infrastructure bottlenecks ☐ ☐ ☐

Regression Testing Yes No N/A


As new capability is introduced, is the new capability tested? ☐ ☐ ☐
Have all previous tests been reconducted with the results
☐ ☐ ☐
compared against expected results?

Is every capability of the software supported with a test case and


is the test case added to the test case library to support final and ☐ ☐ ☐
future system testing?

As bugs are detected and fixed, is the test that exposed the bug
recorded and regularly re-tested after subsequent changes are ☐ ☐ ☐
applied to the application?

Responsive Testing Yes No N/A


URLs of a responsive website should also be resolution specific ☐ ☐ ☐
Test site speed on different devices ☐ ☐ ☐
Consider finger taps ☐ ☐ ☐
Make popups responsive ☐ ☐ ☐
API Testing Yes No N/A
Verify that the API receives input and returns the expected output. ☐ ☐ ☐
Verify that the correct HTTP status code is returned ☐ ☐ ☐
Specify input with minimum required fields and with maximum
☐ ☐ ☐
fields.

Perform input validation test. ☐ ☐ ☐

Accessibility Testing Yes No N/A


Images should include equivalent alternative text (alt text) in the
☐ ☐ ☐
markup/code.

Whether tabs are ordered logically to ensure smooth navigation? ☐ ☐ ☐


Whether shortcut keys are provided for menus? ☐ ☐ ☐
Whether a user is able to adjust audio or video controls? ☐ ☐ ☐

Automation Testing Yes No N/A


Is The task repetitive? ☐ ☐ ☐
Does it save time? ☐ ☐ ☐
Does the task involve lot of data entry? ☐ ☐ ☐

You might also like