Testing a content-driven web app frontend
Stay organized with collections
Save and categorize content based on your preferences.
Testing is crucial to ensuring the functionality, quality, accessibility,
security, and performance of your content driven web application. Testing lets
you assess the user experience and determine if further development is
necessary. Your web application should meet quality standards and perform as
expected.
This provides basic testing guidance for you to consider to make your web
application accessible and user-friendly.
| Components |
| Color contrast |
Ensures that the contrast ratio is optimized for readability. Checks need to be done for
various types of color blindness and user defined high contrast forced colors.
|
| Typography |
Determines if the application accommodates different devices and settings. By using relative
font size and non linear scaling the typography can still be usable on the max size.
|
| Images |
Ensures that the images are high quality and can load quickly. It is important to check for
correct fallbacks with no network and optimized assets for higher resolutions.
|
| Navigation |
Ensures that the navigation is clear and usable by mouse, touch and keyboard navigation.
Checking the history api ensures the back and forward navigation is also preserved
correctly.
|
| Search |
Check for low latency in response times to queries in the URL query parameters and search
field.
|
| Form |
Ensures that all forms are user-friendly to complete and submit. If overriding the default form
submission the correct events need to be listened to and checked for proper form reset and
protection against malicious user input.
|
| Performance |
Ensures that the application is efficient and responsive, with fast load times. This should be
an important part of regression testing too.
|
There are many tools you can
use to check web accessibility. It is important to use multiple methods in order
to cover the range of accessibility components. Be sure to check for ARIA
labels, a11y on DOM elements, keyboard navigation, and screen reader use.
Front end testing frameworks, such as Jest,
Vitest,
Cypress,
Mocha or
Jasmine help you write tests
efficiently and support behavior-driven and test-driven development. With
integrations into CI/CD pipelines you can also automate your tests and help
prevent regression bugs in commits.
Runner frameworks, such as Web Test
Runner,
Playwright, Web
Driver or the Test Runner in
Node.js let you execute these
tests efficiently and support testing across multiple environments and
platforms. This is not an exhaustive list and depending on the framework you are
using there could be testing built-in.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-10 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-07-10 UTC."],[[["\u003cp\u003eTesting is essential for ensuring the functionality, quality, accessibility, security, and performance of your web application, ultimately enhancing user experience.\u003c/p\u003e\n"],["\u003cp\u003eKey components of web application testing include color contrast, typography, images, navigation, search, forms, and performance.\u003c/p\u003e\n"],["\u003cp\u003eUtilize a variety of accessibility testing tools and methods to cover a comprehensive range of components like ARIA labels, keyboard navigation, and screen reader compatibility.\u003c/p\u003e\n"],["\u003cp\u003eLeverage front-end testing frameworks such as Jest, Vitest, Cypress, Mocha, or Jasmine to efficiently write and automate tests, supporting both behavior-driven and test-driven development.\u003c/p\u003e\n"],["\u003cp\u003eEmploy runner frameworks like Web Test Runner, Playwright, Web Driver, or Node.js's Test Runner for executing tests across multiple environments and platforms.\u003c/p\u003e\n"]]],["Testing should evaluate web application accessibility, functionality, and performance. Key actions include checking color contrast for readability, ensuring relative typography scaling, and verifying image quality and load times. Navigation should be usable via mouse, touch, and keyboard. Search response times should be fast, and forms must be user-friendly with appropriate event handling. Performance, including fast load times, is vital. Multiple tools and front-end frameworks (e.g., Jest, Cypress) can aid in this process, and automation via CI/CD pipelines is recommended.\n"],null,["# Testing a content-driven web app frontend\n\nTesting is crucial to ensuring the functionality, quality, accessibility,\nsecurity, and performance of your content driven web application. Testing lets\nyou assess the user experience and determine if further development is\nnecessary. Your web application should meet quality standards and perform as\nexpected.\n\nThis provides basic testing guidance for you to consider to make your web\napplication accessible and user-friendly.\n\n| Components ||\n|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Color contrast | Ensures that the contrast ratio is optimized for readability. Checks need to be done for various types of color blindness and user defined high contrast forced colors. |\n| Typography | Determines if the application accommodates different devices and settings. By using relative font size and non linear scaling the typography can still be usable on the max size. |\n| Images | Ensures that the images are high quality and can load quickly. It is important to check for correct fallbacks with no network and optimized assets for higher resolutions. |\n| Navigation | Ensures that the navigation is clear and usable by mouse, touch and keyboard navigation. Checking the history api ensures the back and forward navigation is also preserved correctly. |\n| Search | Check for low latency in response times to queries in the URL query parameters and search field. |\n| Form | Ensures that all forms are user-friendly to complete and submit. If overriding the default form submission the correct events need to be listened to and checked for proper form reset and protection against malicious user input. |\n| Performance | Ensures that the application is efficient and responsive, with fast load times. This should be an important part of regression testing too. |\n\nThere are [many tools](https://www.w3.org/WAI/ER/tools/) you can\nuse to check web accessibility. It is important to use multiple methods in order\nto cover the range of accessibility components. Be sure to check for ARIA\nlabels, a11y on DOM elements, keyboard navigation, and screen reader use.\n\nFront end testing frameworks, such as [Jest](https://jestjs.io/),\n[Vitest](https://vitest.dev/),\n[Cypress](https://www.cypress.io/),\n[Mocha](https://mochajs.org/) or\n[Jasmine](https://jasmine.github.io/) help you write tests\nefficiently and support behavior-driven and test-driven development. With\nintegrations into CI/CD pipelines you can also automate your tests and help\nprevent regression bugs in commits.\n\nRunner frameworks, such as [Web Test\nRunner](https://modern-web.dev/docs/test-runner/overview/),\n[Playwright](https://playwright.dev/), [Web\nDriver](https://webdriver.io/) or the [Test Runner in\nNode.js](https://nodejs.org/api/test.html) let you execute these\ntests efficiently and support testing across multiple environments and\nplatforms. This is not an exhaustive list and depending on the framework you are\nusing there could be testing built-in."]]
