Glossary of Sauce Labs Terminology
A B C D E F G H I L M N O P R S T U V W
A
Action RPG (ARPG)
This is typically a smaller role-playing game, usually small parties of 1-10 players, without all the depth of play offered by a full-fledged RPG. ARPGs will have tight, compact game experiences, where you have characters and loot that "persist" from session to session, but where the world the user plays in will be auto-generated at run-time.
Alpha
See: Playtest.
Analytics
See: Insights.
API Contract Testing
A lightweight form of API testing that checks each endpoint's contract -- that is, the content and format of static API requests and responses. It ensures that spec files (e.g., Swagger, OpenAPI, and RAML) fulfill the contract between API consumers and producers.
More information: Accelerating Releases with Quality: Contract Testing vs. E2E Functional Testing.
API E2E Testing
An API testing method that validates the logic of dynamic APIs, ensuring that the API consumer can fully support the user story’s goals.
More information: Accelerating Releases with Quality: Contract Testing vs. E2E Functional Testing.
API Mocking
An API server that mimics a real API server's requests and responses, which are based on the data from the spec file you provide. Commonly used for testing and debugging APIs while they're still in development; environment is stable and third-party dependencies are not required.
The Sauce Labs API Mocking tool is called Piestry. See: Piestry.
API Monitoring
Refers to the Sauce Labs API Testing functionality accessible from your Project Dashboard, where you can view testing activity, metrics, test outcome reports, tags, schedule tests, and more.
Appium
An open source mobile UI automation framework that uses the Selenium WebDriver protocol to control interaction with native apps, mobile web apps, and hybrid apps in your tests. Appium acts as a wrapper that translates Selenium WebDriver commands into iOS and Android commands. With Sauce Labs, you can use Appium to test mobile apps on Emulators, Simulators, and real devices.
See also: selenium, webdriver.
App Under Test (AUT)
A web or mobile app in the test phase of the software development cycle.
See also: software development lifecycle.
Automated Testing
A testing method where you use separate software to control the execution of tests on your own software and compare your actual test results to your expected results. You can use frameworks like Appium and Selenium to control the execution of automated tests on your web and mobile apps.
B
Beta
See: Playtest.
Build
-
A suite of individual Sauce Labs tests on various parts (e.g., page objects) of a website or app using any platform/browser combination, bundled together in the same session. A build is defined when you add the same build number to the code for tests in that suite. More information: Best Practice: Use Build IDs, Tags, and Names to Identify Your Tests.
-
The process by which source code is compiled and converted into an executable or binary pre-release version of your software program. Builds are often comprised of multiple smaller builds.
C
Camera Image Injection
A Sauce Labs feature that enables you to mimic camera behavior when testing apps on the Real Device Cloud by letting you upload an image (in .jpeg .jpg, or .png format) from your computer or another location and presenting it to the app as if it was read by the device camera.
Capabilities (Caps)
A section of code required in automated test scripts to specify test parameters (e.g., OS, browser, API, device) used to configure the environment for your Selenium, Appium, and Sauce Labs tests. More information: Test Configuration Options.
See also: platform configurator.
CI/CD Pipeline
An end-to-end software development process that supports continuous integration and continuous deployment throughout the software development lifecycle (building, testing, and deploying software).
See also: CI/CD platform, software development lifecycle.
CI/CD Platform
A pipeline-driven software platform that automates the CI/CD pipeline process at scale. You can configure your CI/CD platform to run tests on Sauce Labs using one of our platform-specific proprietary plug-ins. More information: Sauce Labs Integrations.
See also: CI/CD pipeline, continuous integration, continuous deployment.
Closed Beta Testing
See: Playtest.
Colliding Tunnels
A Sauce Connect Proxy scenario where two or more tunnels are launched with the same tunnel name not in High Availability Mode.
By default, duplicated (already running) tunnels are halted unless a Sauce Connect Proxy is started with the --tunnel-pool
option.
More information: High Availability Setup.
See also: sauce connect proxy, tunnel name.
Company Vault
A Sauce Labs API Testing storage space where you can save variables and code snippets to use across all of your Projects.
See also: vault.
Composer
A Sauce Labs API Testing feature where you can generate API functional tests and write tests from scratch.
See also: http client.
Concurrency Limit
The maximum number of total Sauce Labs tests -- both automated and manual -- that you can run simultaneously across all user accounts within your organization. Concurrency limits vary according to pricing plan. Once you and/or your teammates have used all concurrency slots, additional tests will not launch until an existing test has finished. More information: Managing Concurrency.
Continuous Deployment (CD)
A software development practice where code that has passed all required tests is immediately and automatically deployed into production.
See also: CI/CD pipeline.
Continuous Integration (CI)
A software development practice where all code changes are regularly committed to a shared repository and re-tested to collect and act on feedback.
See also: CI/CD pipeline.
Continuous Testing
The process of continuously executing automated tests throughout your software development lifecycle, allowing you to collect and act on feedback.
See also: CI/CD pipeline.
Continuous Testing Benchmark
See: Sauce Labs Continuous Testing Benchmark.
Cross-Browser Compatibility
The consistency of your web or mobile app's user experience across multiple combinations of browsers, devices, and operating systems.
Cross-Browser Testing
A method of testing where you can verify the consistency of your web or mobile app when accessed through multiple combinations of browsers, devices, and operating systems. By leveraging automated testing, you can test thousands of these combinations simultaneously in parallel. More information: Sauce Labs Cross-Browser Testing for Web Apps.
Cross-Platform
Describes the ability of players using different video game hardware to play with each other simultaneously.
D
Data Center (DC)
A network that houses the set of Sauce Labs services relevant to your license type and your company's needs (i.e., geographic location, real vs. virtual device, and optional other services). To run a Sauce Labs test, you must connect to one or more data centers by including the appropriate endpoint URL(s) in your test script. More information: Data Center Endpoints.
DirectX
DirectX is a series of application programming interfaces (API) that provide low-level access to hardware components like video cards, the sound card, and memory. At a basic level, DirectX allows games to "talk" to video cards. In the DOS days, games had direct access to video cards and the motherboard, and you could directly edit the configuration file to make changes.
E
Emulator
A virtual machine used to mimic the software, operating system, and certain device features (e.g., camera, touch ID, GPS) of the Android mobile app that you're testing in Sauce Labs. Can be used to test multiple browser/device combinations and use cases.
See also: Simulator, real device testing.
Enterprise
-
The Sauce Labs subscription plan that offers the largest amount of testing bandwidth and premium benefits.
-
A Sauce Labs customer subscribed to our enterprise plan, which offers a dedicated account team and premium support. For more information, contact your Customer Success Manager. More information: Sauce Labs Pricing.
eSports
A form of competition using video games. Esports often takes the form of organized, multiplayer video game competitions, particularly between professional players, individually or as teams.
F
Failure Analysis
A Sauce Labs Insights tool that analyzes failures that occur during test runs and reveals any common root causes so that you can debug as quickly as possible. More information: Using Failure Analysis.
See also: Insights.
Failure Pattern
A Sauce Labs Failure Analysis metric that shows a specific, recurring error that's causing test and build failures. You can see the amount of tests impacted and the percentage of total failures attributed to each error.
See also: failure analysis.
First-Person Shooter (FPS)
A subgenre of shooter video games.
Flight Sim
Microsoft Flight Simulator is a series of amateur flight simulator programs for Microsoft Windows operating systems, and earlier for MS-DOS and Classic Mac OS. It is one of the longest-running, best-known, and most comprehensive home flight simulator programs on the market.
Frames-Per-Second (FPS)
It is the frequency (rate) at which consecutive images (frames) are captured or displayed.
Framework
The UI automation library and test runner combination that you use for testing. You can tailor your framework to meet your situation and test goals.
See also:_ UI automation library, test runner._
Free Trial
A period for prospective customers to explore the full functionality of the Sauce Labs platform for free. Includes automated cross-browser testing, live testing, and access to real devices for mobile testing. More information: Sauce Labs Free Trial.
Front-End Performance Testing
A method of performance testing that enables you to check UI functionality like forms, graphs, and menus, as well as associated JavaScript. You can integrate Sauce Performance, our front-end performance testing tool, with your existing CI/CD workflows. Front-end testing - using tools like Google Lighthouse and GTmetrix - measures how quickly you can see and interact with your website. It doesn't have back-end load testing functionality, where you'd use tools like JMeter, Gatling. More information: Getting Started with Sauce Front-End Performance, Sauce Labs White Paper: Best Practices for Front-End Performance Testing.
See also: performance testing.
Functional Testing
A method of testing that validates some functionality or feature of your app. The output of these tests should generally be a simple "pass" or "fail" – either your functionality worked as expected, or it didn't.
See also: non-functional testing.
G
Game Artist
Game Artists design preliminary sketches and develop them according to a video game's general style. They then create 2D or 3D animations from these sketches under the supervision of the Lead Artist. These elements create the world, its mood, and unique personality.
Game Designers
Game designers have duties like designing characters, levels, puzzles, art and animation. They may also write code, using various computer programming languages. Depending on their career duties, they may also be responsible for project management tasks and testing early versions of video games.
Game Engine
The “game engine” is the fundamental technology that the game lives on. In most cases, a game’s menuing system, networking layer, graphical presentation, user interface, everything, will be centered around a single gaming “engine”.
A game on a specific platform will never be based on more than one engine. The only time a game will be implemented on multiple engines is when the developer has to implement it on multiple platforms.
Given that more engines are being developed to work across platforms, developers are starting to prefer these engines, which is leading to considerable market consolidation.
Game-Maker Studio
A series of cross-platform Game Engines.
Games as a service (GaaS)
Represents providing video games or game content on a continuing revenue model, similar to software as a service. Games as a service are ways to monetize video games either after their initial sale, or to support a free-to-play model. Games released under the GaaS model typically receive a long or indefinite stream of monetized new content over time to encourage players to continue paying to support the game.
Graphics Processing Unit (GPU)
A graphics processing unit is a specialized electronic circuit designed to rapidly manipulate and alter memory to accelerate the creation of images in a frame buffer intended for output to a display device. GPUs are used in embedded systems, mobile phones, personal computers, workstations, and game consoles.
H
Headless Browser
A browser or browser simulation without a UI. It's considered by developers to be a lightweight and scalable option if you want to test and collect pass/fail data earlier in the development lifecycle. Available only for Chrome and Firefox.
HTTP Client
A Sauce Labs API Testing tool and workspace where you can:
- Make HTTP API requests (i.e.,
GET
,POST
,DELETE
) to a web server - Generate API functional tests
- Import, store, and organize OpenAPI specs, Postman Collections, and API requests
- Use Sauce Connect Proxy to make calls to locally hosted APIs in a development environment
Hybrid App
A mobile app written in platform-agnostic web technologies like HTML5, CSS, and JavaScript. Hybrid apps run inside a native container and leverage the device’s browser engine to render the HTML and process the JavaScript locally.
I
Image Injection
See: camera image injection.
In-House
- Many studios develop their own in-house game engine, for a variety of reasons. Many times it’s a matter of legacy: they’ve been doing it this way, so they need to keep doing it that way. Some of the older engines are starting to show their age in a way that’s unavoidable, so these companies are starting to migrate in the direction of Unreal or Unity.
- Another case for an in-house engine is the Decima engine is one example, used by publisher Guerilla Games to make Horizon: Zero Dawn. Whether it’s feature inadequacy, a long-term vision of monetizing a new engine as its own IP, or a specific problem with the other engines, this was the default for nearly all game studios throughout the 80s and 90s, and started to dwindle with the advent of Unreal in the late 90s.
- Though most companies use pre-built game engines, they still don’t have much in the way of automated testing or error/APM monitoring. That’s where Sauce Labs comes in.
Instances
A special area that generates a new copy of the location for each group, or for a certain number of players, that enters the area. Instancing, the general term for the use of this technique, addresses several problems encountered by players in the shared spaces of virtual worlds.
Insights
A Sauce Labs analytics tool that tracks and reports how your tests are performing over time, allowing you to quickly identify and remediate risk, improve productivity, and create digital confidence in your entire organization. More information: Insights.
Invoice Customer
See: enterprise customer.
IPSecVPN
A protocol used to establish a secure VPN connection between apps hosted on an internal server and the Sauce Labs virtual machines or real devices used for testing. More information: IPSec VPN.
L
Live Testing (LT)
A type of software testing where you execute test cases manually, without using any automation tools. More information: Live Cross Browser Testing.
See also: manual testing.
Logger
A Sauce Labs API Testing tool that captures and record API calls (HTTP requests and responses).
logfile
A file where various Sauce Labs processes record events that occur during testing. Access to different logfiles depends on the process that generated them.
Lumberyard
This is Amazon Studios’ game engine.
M
Managed Customer
See: enterprise customer.
Manual Testing
See:live testing.
MMORPG
Massively Multiplayer Online Role-Playing Game.
MOBA
Multiplayer Online Battle Arena.
Mobile App
See: native app, hybrid app.
N
Native App
A mobile software app written in a programming language specific to the platform it is being developed for: either iOS or Android. More information: Live Testing for Native Mobile Apps on Real Devices, Mobile App Testing with Espresso and XCUITest.
See also: hybrid app.
Non-Functional Testing
A type of software testing that validates behavioral, measurable aspects of the software (e.g., performance, compatibility, user experience). Functional testing determines if your software meets its business requirements, whereas non-functional testing determines how it operates. When running non-functional tests on Sauce Labs, you can use custom extensions for WebDriver that will allow you test the performance of your website under specific network conditions and collect network and app-related metrics.
See also: functional testing.
O
OnDemand Service
A prime facility and feature of cloud computing services that allows users to provision raw cloud resources at run time, when and where needed.
Open Beta Testing
See: Playtest.
Organization Admin
The Sauce Labs account admin role that can manage permissions levels for all users, oversee Sauce Labs test settings and activity for their organization, create Teams and Team Admins, designate other Organization Admins, and set concurrency allocations among different Teams. More information: Account and Organization Management.
See also: team admin, team management.
P
Parallel Testing
-
The practice of running multiple tests simultaneously.
-
When signing up for a self-service license, this is equivalent to your account's concurrency settings. More information: System and Network Requirements for Sauce Connect Proxy, Using Frameworks to Run Tests in Parallel.
See also: concurrency limit.
Parallelization
See: parallel testing.
Performance Metrics
The data that developers and QA teams use to capture and address performance regressions early in the development cycle. More information: Sauce Connect Proxy Performance Metrics.
Performance Testing
A type of non-functional software testing that ensures your software responds as expected on the front end and meets your requirements under expected workload. Sauce Labs supports front-end performance testing; see front-end performance testing for more information.
See also: front-end performance testing.
Persistence
A persistent online world that supports hundreds or thousands of players simultaneously; gaming continues to develop even when some of the players are not playing their characters.
pidfile
A text file generated by Sauce Connect Proxy that records your tunnel's process identification number (PID). Unless otherwise specified, the file will be cleaned up on exit or overwritten at startup. If needed, you can terminate a tunnel any time by sending a kill signal to the PID recorded in pidfile. More information: How to Start and Stop Sauce Connect Tunnels (Startup and Teardown), Sauce Connect Proxy Command-Line Quick Reference Guide.
Piestry
The name of our API mocking server tool. In keeping with the Sauce tradition of naming things after food, Piestry is a pastry masquerading as a pie. This is analogous to our API mocking server, which mimics a real API server's requests and responses.
See API Mocking to learn more about the concept.
Platform Configurator
A Sauce Labs tool where you can select your capabilities and generate code snippets to copy and paste into your automated testing scripts. More information: Platform Configurator.
See also: capabilities.
Platform-dependent
Platform dependent typically refers to applications that run under only one operating system in one series of computers (one operating environment).
Playtest
A playtest is the process by which a game designer tests a new game for bugs and design flaws before releasing it to market. Playtests can be run "open", "closed", "beta", or otherwise, for which they have become an established part of the quality control process.
- Alpha: It is the phase of game testing where the game is still in the development phase along with which parallel testing is done to ensure that the game is developed without any glitches and is working smoothly without crashing.
- Beta: During beta testing, the game is almost production ready with all the major issues being fixed. In this phase, the game testers are required to extensively find all the possible ways to break the game along the lookout for all minor issues. During Beta Testing, the game needs to pass through many testing methodologies such as performance testing, stress testing, and game compliance testing.
- Open Beta Testing: Open test is when the beta version of the game is made available for everyone interested. This interested group will play the game a share the reviews to the publisher. This process is also called as pre-release of the game software.
- Closed Beta Testing: This testing is done only be the closed set of people who work closely with the game developers.
- Release: when the game is released to the public