Runtime environment (runenv)

Search…
Interacting with the test plan runtime environment
Information about the test plan being run is sent to every test instance and available through the runtime.RunEnv value - the runtime environment.
Let's have a look at the information available to us via the runtime environment:
1
// RunEnv encapsulates the context for this test run.
2
type RunEnv struct {
3
	RunParams
4
	*logger
5
​
6
  ...
7
}
8
​
9
// RunParams encapsulates the runtime parameters for this test.
10
type RunParams struct {
11
	TestPlan string `json:"plan"`
12
	TestCase string `json:"case"`
13
	TestRun  string `json:"run"`
14
​
15
	TestRepo   string `json:"repo,omitempty"`
16
	TestCommit string `json:"commit,omitempty"`
17
	TestBranch string `json:"branch,omitempty"`
18
	TestTag    string `json:"tag,omitempty"`
19
​
20
	TestOutputsPath string `json:"outputs_path,omitempty"`
21
​
22
	TestInstanceCount  int               `json:"instances"`
23
	TestInstanceRole   string            `json:"role,omitempty"`
24
	TestInstanceParams map[string]string `json:"params,omitempty"`
25
​
26
	TestGroupID            string `json:"group,omitempty"`
27
	TestGroupInstanceCount int    `json:"group_instances,omitempty"`
28
​
29
	// true if the test has access to the sidecar.
30
	TestSidecar bool `json:"test_sidecar,omitempty"`
31
​
32
	// The subnet on which this test is running.
33
	//
34
	// The test instance can use this to pick an IP address and/or determine
35
	// the "data" network interface.
36
	TestSubnet    *IPNet    `json:"network,omitempty"`
37
	TestStartTime time.Time `json:"start_time,omitempty"`
38
}
39
​
Copied!
The runtime environment is propagated on any runner to the test instances via environment variables and then deserialized in the runtime package of the SDK upon start.
Most of these fields should look familiar -- they represent the configuration we added to our manifest.toml file along with configuration specific to the test run and the test instance, such as TestRun, or TestSubnet.
If you want to find out how many instances of a test plan are running, it's as easy as this:
1
select runenv.TestInstanceCount {
2
case 1:
3
  // The lonliest number
4
case 2:
5
  // It takes two to tango
6
case 3:
7
  // Do we have a quorum?
8
default:
9
  // Now this is a party!
10
}
Copied!
Additionally a logger is initialized as part of the RunEnv run environment, so that every time you call runenv.RecordMessage("my message") in your test plan, messages include additional metadata such as the current run identifier, group, timestamp, etc.
For more information, check the Observability, assets and metrics.
Runners
Client-Server communication
Last modified 1yr ago
Copy link