In this video, Meaghan Lewis explains the test pyramid. The test pyramid represents an ideal way to structure tests—and it's good to keep this representation in mind when writing WebDriver tests.
- [Instructor] The test pyramid explains…an ideal way to structure tests.…It is a visual representation intended…to guide the coverage of tests that should exist…at various levels within the application.…The test pyramid typically has three layers,…which represent unit, integration, and UI level tests.…Unit tests are always at the bottom of the pyramid.…They just hit the server and verify a result.…Unit tests test a single function.…They are the fastest and able to run in seconds.…
And there should always be the most number of unit tests,…which is why they are at the bottom of the pyramid.…In the middle there are integration or service level tests.…These level of tests involve multiple services…and how they work together.…These tests create their own data and are a bit slower.…They run in the range of tens of seconds.…There should be a decent amount of integration level tests.…UI tests are at the top.…This is where Selenium tests are.…
They are extremely valuable,…because they test end-to-end workflows…and mimic user actions.…
Find out how to set up the test-writing framework, WebDriver, and Selenium Grid, which allows you to distribute the testing load and run tests against a remote server. Learn best practices to write effective tests using variables and functions, and to organize tests into suites that can scale over time. Instructor Meaghan Lewis—a QA engineer at GitHub—also explains the test pyramid paradigm, which details an ideal way to balance unit, integration, and UI testing.
- Setting up Selenium WebDriver
- Using the Selenium grid to distribute the testing load
- Setting up a hub and nodes
- Writing clean test code
- Organizing a test suite