Builds and test environments
Last modified on Tue 21 Feb 2023

Latest builds

Check out Tryout apps for the latest builds for both iOS and Android.

Development and testing environments

A test environment is any space in which software undergoes a series of experimental uses. To fully grasp the definition of a test environment, consider how a typical app gets deployed and managed. There are times when developers make clones of the main codebase and deploy them separately to iron out bugs and glitches in different virtual machines. The location and state of these parallel apps are what we’re calling test environments.

We typically have four environments along any software’s lifecycle:

Types of testing environments

Testing environments are a critical part of the software development lifecycle. Before moving to production, the app will have undergone test executions looking to break it in a safe environment.

Listed below are the most common types of testing environments and the ones you will often hear about from software testers and developers:

Test devices

When checking implementation, we use mobile devices from our Test Lab. Each office has its own Test lab, usually consisting of a shelf with test devices. For instance, in the Zagreb office, all test devices can be found on the 7th floor next to the QA team.

Device claiming is described in detail in our General Handbook and the QA Handbook.

We're working a lot more remotely, so you'll need to check implementation from time to time even if you don't have physical devices on hand. That's where BrowserStack comes in - its an emulator of a lot of different platforms, desktop and mobile devices where you can load app files to test them out. The credentials are in 1Password.