Learning outcomes:

Understand that the two are closely related — you will want your web app functionality to work for a target range of users, across a range of target browsers/devices. In addition, such testing can largely be automated using available tools.
Some accessibility testing can be automated, for example, "do the images all have alt text?".
A typical process for performing automated tests:
- Identify who the target audience groups are, and what browsers they are using.
- Identify the items of functionality that should be tested. These can range from visual ("does the layout look like it should?"), to user-facing functions ("does the search box return a result?"), to lower-level code ("does function x() return the expected result?").
- Some tests will also test that integrated modules are working correctly with other parts of the codebase (integration testing).
- Write tests to test this functionality, using an appropriate tool set.
- Run the tests regularly (for example after each commit to the repo) to see if any tests fail.
- Document the test results.
- Fix the code and rerun the tests to make sure they pass, and ensure that new errors have not been introduced by the code updates (regression testing).
Understand the typical toolset used to run automated tests:
Understand how to integrate testing with GitHub using continuous integration (CI) tools:
- Understand the utility of this — you can create a setup to automatically run your test suite each time you commit a change to the codebase.
- Use tools such as CircleCI or Travis CI to do this.

Resources:

Cross-browser testing

Page not found