Environments

Environments make it easier for us to manage the variables used by test scripts from a centralized structure. There are essentially two environment groups: Development and Production.

Environment Groups

The Development group is the environment used while developing tests. Tests are developed within this environment.

The Production group is the environment used by completed tests.

• No new environment groups can be added beyond these two groups.

• Unlimited environments can be added under these environment groups.

Environments

Environments are positioned under environment groups and can be added in unlimited numbers. To access environments, the environment_key is used, and these keys are sequentially named as env1, env2, ..., envn.

Under each environment folder, there are files named configs-1.js and configs-2.js. These files store our test parameters in JSON format.

global.config.js

In the global.config.js file located under environment groups, common parameters to be used across all environments within the group are stored.

For example, if the username and password information is the same and unchanging for all environments, it can be defined in global.config.js.

If environment configs and global configs conflict, the parameters in the global config will prevail. Global configs override environment configs.

Genarete New Environment

You can use the sente new command to generate a new environment.

sente new

Select Environment

To run the run by selecting Environment, see here.