🏝️ Environment

Sometimes it may be appropriate to provide a report on details and tests from the environment in an effort to replicate production or the context of a defect as much as possible.

  • Environment Name
    • Environment URL/Location
    • Database
      • Seeded
      • Cloned from Production
  • Device Environment
    • Operating System
      • MacOS
      • Linux
        • Ubuntu
        • Fedora
        • Redhat
        • Arch
      • Windows
      • iOS
      • Android
    • Hardware Device
      • iPhone
      • Samsung Galaxy
      • Google Pixel
      • iPad
      • Android Tablet

Market Share

Often the relative market share of a device is very relevant in regards to focusing on Risks and Priorities. Testing is much more efficient when QA is using environments the end-users actually use. This can depend on a number of factors:

  • What ratio of end-users globally use the device/operating system combination?
  • What ratio of end-users who would use this application use the device/operating system combination?

For example

  • When testing a mobile application for ordering food online and the market share of 2011 iPhone4 mobile devices is 0.001%, there is no point in testing on this environment.
  • When testing a mobile application featuring different Android-related technology and features, it may be a lot less necessary to test on iPhones.

The point basically is to "read the room":

  • Who are your end-users?