MozTrap/Admin Guide

Introduction
This page aims to give a necessarily explanation and guide to MozTrap administration related concepts and concrete operations. It is supposed to support people who would love to maintain, optimize MozTrap test organization, as well as to coordinate test processes.

Currently most of the content were extracted and edited from official MozTrap guide, where you can search for more details.

Please notice you will need to have Test Manager permission to act on most of those described in this section.

Product management
To manage products, simply click from MozTrap navigator tab Manage->Products. Please notice you will need to have Admin permission to manage users.

The core object in MozTrap is the Product. A Product itself is little more than a name and optional description, but almost everything in MozTrap more or less relates to a Product.

Product Versions management
To manage product versions, simply click from MozTrap navigator tab Manage->Versions.

Every product has a list of product versions. When a new Product Version is created, all test cases for that Product will get a new version to match the new Product Version.

Product versions are automatically ordered according to their version number/name. The version is split into dotted segments, and the segments are ordered lexicographically (with implicit left-side zero-padding of numerals to avoid e.g. “2” ordering after “11”). So, for instance, version 1.1 is greater than version 1.0.3, version 2.0b1 is greater than 2.0a3, and 3.11.1 is greater than 3.2.0.

There are some special cases to better support common version-numbering schemes. Strings alphabetically prior to “final” are considered pre-release versions (thus 2.1a, 2.1alpha, and 2.1b are all prior to 2.1, whereas 2.1g is considered a post-release patchlevel). The strings “rc”, “pre”, and “preview” are considered equivalent to “c” (thus also pre-release), and the string “dev” orders before “alpha” and “beta” (so 2.1dev is prior to 2.1a).

Product versions can also optionally have a code name that does not impact their ordering.

Test Suite management
To manage test suites, simply click from MozTrap navigator tab Manage->Suites.

A Test Suite is a named collection of test cases that can be included in a test run. And it is the only way to include a set of test cases into a test run.

It is interesting to point out the test suites held by a test run are order sensitive. When a test run has several test suites included, the set of cases in a test suite, which has a higher position in a test run, will have a higher position in running list, which is visible in the running list when executing test.

Moreover the test cases order in the running list does not only depends on the suite order when creating test run, but also depends on the test case order in a test suite. Namely the order of test cases in a test suite decides the order test cases display in a test run who has the suite included.

Test Run management
To manage test runs, simply click from MozTrap navigator tab Manage->Runs.

A Test Run consists of a set of test case versions for execution in a particular environment or set of environments.

Environment management
To manage environments, simply click from MozTrap navigator tab Manage->Environments.

Environment is an important feature in MozTrap, it is required to thoroughly understand it before doing changes with current setting.

MozTrap allows fine-grained and flexible specification of the environment(s) in which each test should be run.

An Environment is a collection of environment elements that together define the conditions for a single run of a test. For instance, an environment for testing a web application might consist of a browser, an operating system, and a language; so one environment might be Firefox 10, macOS, English, and another Internet Explorer 9, Windows 7, Spanish.

An Environment Element is a single element of a test environment, e.g. Windows 7 or Firefox 10.

An Environment Category is a category containing several (generally mutually exclusive) elements. For instance, the Operating System category might contain the elements macOS 10.5, macOS 10.6, Windows Vista, and Windows 7.

An Environment Profile is a collection of Environments that specifies the supported environments for testing a product or type of product. For instance, a Web Applications environment profile might contain a set of environments where each one specifies a particular combination of web browser, operating system, and language.

Environment profiles can be named and maintained independently of any specific product; these generic profiles can then be used as the initial profile for a new product. For instance, the generic Web Applications profile described above could be used as the initial profile for a new web application product.

Product versions, runs, and test cases all have their own environment profile; that is, the set of environments relevant for testing that particular product version, test run, or test case. These profiles are inherited.

There are more detailed manual to know how the environment mechanism works.

User management
To manage users, simply click from MozTrap navigator tab Manage->Users. Please notice you will need to have Admin permission to manage users.

The MozTrap user management page allows admins to create a new user, delete an existing user, enable or disable a user, as well as assigning a role to a user.

It is worthy of mentioning that actively changing a user's password is not allowed directly. In case a MozTrap user forgets her password, the usual way it to ask her get the password reset via email from MozTrap login UI. In the worst case that nothing could be done by the user, please ask MozTrap server team to find a solution.