Knowledge Check
Nine questions on the decisions that matter most when a suite has to pass in every browser. Each answer comes with a short explanation, so a wrong answer points you back to the right chapter.
1. Your matrix is Chrome, Edge, Opera and Brave on Windows 11, all green. A colleague says Firefox and Safari are "covered by the others". What is wrong with that?
Browser names are not engines. Four Chromium-based browsers test one rendering engine. Firefox (Gecko) and Safari (WebKit) each need at least one configuration of their own.
2. A team on Windows laptops wants to test Safari. Which option actually gives them Safari?
Safari has not been released for Windows since 2012. Playwright's WebKit build is the engine, not Safari, and on Windows it uses Windows fonts and controls. Only Apple platforms run Safari.
3. Analytics show Safari on macOS at 0.8% of your users, down from 6% last year. What is the most responsible next step?
A falling share can be a symptom: users who cannot use the site in their browser leave. Chrome on macOS is Blink, so it says nothing about Safari.
4. A test types 12/24/2026 into an <input type="date">. It passes in Firefox and leaves the field empty in Chrome and Safari. What is the fix?
Each engine's native date control handles keystrokes its own way. The value of a date input is always ISO yyyy-mm-dd, and setting it that way works in every engine.
5. A Selenium suite passes in Firefox against a staging server with a self-signed certificate and fails in Chrome and Safari. Why?
Options classes come with different defaults. Set accept_insecure_certs explicitly on every options object, so all browsers behave the same.
6. In a Playwright grid config, which project is set up correctly for Microsoft Edge?
The project's browserName is the Playwright client engine, and it must match the remote browser. Edge is Chromium-based, so it connects with the chromium client.
7. A login test passes on desktop browsers and an older Android phone, but on a newer phone the click on "Log in" does nothing and the test times out. visualViewport.height is much smaller than innerHeight at the moment of the click. What is happening?
A small visual viewport with a focused input means the keyboard is taking up the screen. Close it (for example by blurring the field) or submit the way a user would, with the keyboard's Go or Enter key.
8. Your plan has 5 parallel slots. A nightly matrix of 60 sessions at about 30 seconds each runs with one worker and takes 30 minutes. Roughly how long should it take with five workers?
Wall time is roughly sessions times average length divided by slots: 60 x 30 s / 5 = 6 minutes. Workers beyond your slots would only wait in the queue.
9. A test that selects all text with send_keys(Keys.CONTROL, "a") fails on Safari only, with the field still containing the old text. Changing CONTROL to COMMAND does not help. What is the best final version of the test, if its purpose is "the user replaces the comment"?
The shortcut is incidental to the user's goal, and keyboard chords depend on the OS and the vendor's driver. clear() works the same everywhere. Setting the value with JavaScript skips the input events the application may rely on.
Where to go next#
To check pages visually across the same matrix, continue with the Visual Regression Testing course. If your application is not public yet, the local website testing course shows how a remote browser reaches localhost and staging through TestingBot Tunnel. For the full list of browser and platform options, see the Selenium documentation and the Playwright documentation for TestingBot.
You finished Cross-Browser Testing Tutorial
Put what you learned into practice. Run your tests on 6100+ real browsers and physical iOS and Android devices.