From d275107dc0b60cbe7caa851b1554744b7438a802 Mon Sep 17 00:00:00 2001 From: Christine Lytwynec Date: Tue, 29 Jul 2014 11:43:32 -0400 Subject: [PATCH] updated doctring to explain the bok-choy shards --- scripts/all-tests.sh | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/scripts/all-tests.sh b/scripts/all-tests.sh index a02b1f83a2..a32baa5d9d 100755 --- a/scripts/all-tests.sh +++ b/scripts/all-tests.sh @@ -23,9 +23,20 @@ set -e # - "bok-choy": Run acceptance tests that use the bok-choy framework # # `SHARD` is a number (1, 2, or 3) indicating which subset of the tests -# to build. Currently, "lms-acceptance" has two shards (1 and 2), -# "cms-acceptance" has three shards (1, 2, and 3), and all the -# other test suites have one shard. +# to build. Currently, "lms-acceptance" and "bok-choy" each have two +# shards (1 and 2), "cms-acceptance" has three shards (1, 2, and 3), +# and all the other test suites have one shard. +# +# For the "bok-choy", the tests are put into shard groups using the nose +# 'attr' decorator (e.g. "@attr('shard_1')"). Currently, anything with +# the 'shard_1' attribute will run in the first shard. All other bok-choy +# tests will run in shard 2. +# +# For the lettuce acceptance tests, ("lms-" and "cms-acceptance") they +# are decorated with "@shard_{}" (e.g. @shard_1 for the first shard). +# The lettuce tests must have a shard specified to be run in jenkins, +# as there is no shard that runs unspecified tests. +# # # Jenkins configuration: #