updated doctring to explain the bok-choy shards
This commit is contained in:
@@ -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:
|
||||
#
|
||||
|
||||
Reference in New Issue
Block a user