Parameters and test cases

Search…
Adding an additional test case
Parameters and test cases are defined in the manifest.toml file of every test plan. Let's have a look once again at the quickstart/manifest.toml file and add two test cases to the bottom of the file:
$TESTGROUND_HOME/plans/quickstart/manifest.toml
1
...
2
​
3
​
4
[[testcases]]
5
name = "smallbrain"
6
instances = { min = 1, max = 200, default = 1 }
7
​
8
  [testcases.params]
9
  word = { type = "string", default = "never" }
10
  num = { type = "int", default = 2 }
11
  feature = { type = "bool", default = false }
12
​
13
[[testcases]]
14
name = "bigbrain"
15
instances = { min = 1, max = 200, default = 1 }
16
​
17
  [testcases.params]
18
  word = { type = "string", default = "always" }
19
  num = { type = "int", default = 10000000 }
20
  feature = { type = "bool", default = false }
Copied!
Feel free to add your own galaxybrain test case as well!
You can confirm that the testground client is able to parse the manifest, and enumerate the cases it declares:
1
$ testground plan list --testcases | grep quickstart
2
quickstart    smallbrain
3
quickstart    bigbrain
Copied!
We would like to take these two cases out for a spin. First, let's prepare our code. Open our quickstart plan program and deal with these parameters!
This snippet is routing both test cases to the same function. In practice, you will want to run different logic for each test case!
As you can see, a test plan a simple executable that conforms to the simple Testground contract, which the SDK facilitates. This makes it super easy to debug and develop. There's beauty in simplicity!
$TESTGROUND_HOME/plans/quickstart/main.go
1
package main
2
​
3
import (
4
    "github.com/testground/sdk-go/runtime"
5
)
6
​
7
func main() {
8
    runtime.InvokeMap(map[string]runtime.TestCaseFn{
9
        "bigbrain":     run,
10
        "smallbrain": run,
11
    })
12
}
13
​
14
func run(runenv *runtime.RunEnv) error {
15
  var (
16
    num         = runenv.IntParam("num")
17
      word         = runenv.StringParam("word")
18
      feature = runenv.BooleanParam("feature")
19
  )
20
​
21
    runenv.RecordMessage("I am a %s test case.", runenv.TestCase)
22
    runenv.RecordMessage("I store my files on %d servers.", num)
23
    runenv.RecordMessage("I %s run tests on my P2P code.", word)
24
​
25
    if feature {
26
        runenv.RecordMessage("I use IPFS!")
27
    }
28
​
29
    return nil
30
}
Copied!
The time has come now to run these test cases by setting the --testcase flag. Let's run the smallbrain test case first!
1
$ testground run single --plan quickstart \
2
                        --testcase smallbrain \
3
                        --builder exec:go \
4
                        --runner local:exec \
5
                        --instances 1
Copied!
Watch the output for MESSAGEs with the smallbrain's parameters.
1
INFO  0.0112s      START << instance   1 >> {"plan":"quickstart","case":"smallbrain", [...]
2
INFO  0.0114s    MESSAGE << instance   1 >> I am a smallbrain test case.
3
INFO  0.0115s    MESSAGE << instance   1 >> I store my files on 2 servers.
4
INFO  0.0115s    MESSAGE << instance   1 >> I never run tests on my P2P code.
Copied!
Then watch for the different parameters of the bigbrain test case.
1
$ testground run single --plan quickstart \
2
                        --testcase bigbrain \
3
                        --builder exec:go \
4
                        --runner local:exec \
5
                        --instances 1
Copied!
Try using different runners. This command executes the plan with the local:exec runner and exec:gobuilder, but it works just as well with the local:docker runner or the Kubernetes cluster:k8srunner (for which you will need to use the docker:go builder)!
Understanding the test plan manifest
Keeping instances in sync
Last modified 1yr ago
Copy link