Understanding the test plan manifest
Inside the root of every test plan is a file called manifest.toml
. This file is used to explain the test plan to the Testground daemon. In this file, a plan can be restricted to specific runners. Additionally, this is the file where test cases and parameters are defined.
If you have created the quickstart
plan in the previous article, let's have a look at the manifest file we have just created.
Test plan name
the name of the test plan is a top-level of the file's schema.
Defaults
Enclosed in a defaults section are default builders. These are variables which can be used as defaults for the plan In this section, we set the default builder and runner.
Builder and runner options
The next few sections are options passed to each builder and runner when they are selected. Make sure to enable any builders and runners you want to use! The following section enables all runners and passes configurations. Of particular interest is the module path. Make sure this is correct to ensure code can be correctly imported.
Test cases
Finally, we have test cases. Test cases are defined in an array of tables which specify the name of the test case, boundaries for the number of instances and the values of any parameters being tested in a particular test case.
The resulting manifest.toml
test plan manifest
manifest.toml
test plan manifestPutting it all together:
Last updated