testing/taskcluster/design.md
author Mike Conley <mconley@mozilla.com>
Thu, 24 Mar 2016 16:18:25 -0400
changeset 290723 2c8a3acfb48c772cfc2f0417738590bc607ce110
parent 225663 f6a7135ba01290e9b982b14ac5238d3b340567c8
permissions -rw-r--r--
Bug 1254865 - Set disableglobalhistory on the thumbnail browser. r=Felipe MozReview-Commit-ID: 9SXEAo0H0ko

Problems:

Not all tests work on all platforms
Many tests work on N+1 platforms

Goals:

Tests and builds should be loosely coupled (you probably need a build
but you don't always need a build!)

Workflows:

1. Try: decide upon a set of builds and tests from a matrix of checkboxes

2. Branch: decide upon a set of builds based on in tree configuration
   (essentially a "fixed" version of try flags)

3. One off builds / One of tests (which require a build we created
   earlier)

## Build tasks

No special logic needed but convention of generating artifacts should be followed!

## Test Tasks

Always need a build (and likely also need the tests.zip). Should know
what potential builds they can run on.