testing/taskcluster/design.md
author Masayuki Nakano <masayuki@d-toybox.com>
Thu, 19 Feb 2015 15:50:19 +0900
changeset 229844 d7ef5a56b661bbabc20b0ef5ba09e5e8d3b9cba0
parent 225663 f6a7135ba01290e9b982b14ac5238d3b340567c8
permissions -rw-r--r--
Bug 1119609 part.3 Implement converting methods from key/code value to key/code name index r=smaug

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.