Browser testing

Regular cross-browser testing helps ensures your web site or application is accessible and functional to a broad audience, especially as Internet Explorer 11 is pervasive in federal government but 18F developers use Chrome on macOS almost exclusively.

Using a responsive web design and a standards-based approach will result in wide compatibility across modern browsers, but at the edges your product can still trip up on browser-specific quirks. For example, compare the list of web technologies supported in Internet Explorer 11 versus Chrome. Progressive Web Application-related features and behaviors also vary widely across devices and browsers.

A few options are available at TTS that allow testing on multiple browser platforms. An automated testing solution is ideal, but even manual cross-browser testing remains valuable.

Windows

To test with Windows-native browsers like Internet Explorer or Microsoft Edge:

• Citrix Workspace
  • Pros:
    • No extra installation necessary
  • Cons:
    • You can’t pick the browser versions; the Standard Desktop image includes Internet Explorer 11 and Microsoft Edge (EdgeHTML layout engine)
    • You can’t access localhost
    • Manual testing only
• Virtual machine (VM)
  • Request access to VirtualBox.
  • Pros:
    • You can access localhost
    • Can support local, automated testing through Selenium
  • Cons:
    • Takes a bit of setup

Android

For Google Chrome for Android:

• Android Studio with AVD Manager
  • The GSA IT Helpdesk will need to configure policy on your macOS workstation in order for the Android emulator to run.

iOS

For Safari on iOS:

• Xcode with Simulator
  • If you are using the latest version of macOS currently released by Apple, Xcode is available in the Mac App Store. Otherwise, find the version of Xcode that maps to your macOS version on Apple Developer.

Chrome-family browsers and Firefox

• Cypress
  • The command-line test runner and local GUI is approved for use. However, the Cypress Dashboard SaaS is not.