Testspace

Configuration

To enable manual testing a .testspace.yml configuration file is required to be placed at the root of your repo, for example:

root
├── README.md
├── .testspace.yml
└── specs
 ..

Manual

At the minimum the .testspace.yml content should be:

manual:

Note without the .testspace.yml file specs will not be visible in Testspace

The full .testspace.yml configuration format is:

manual:
  path: "/path/to/thespecs" # optional path to specs root, defaults to "specs"
  board: # optional
sandbox: # optional one or more branch-wildcard entries, defaults to "sandbox*"

path

The path represents the root folder for spec files. It the path is omitted, the root defaults to specs.

manual:
  path: "/path/to/thespecs" # optional path to specs root, defaults to "specs"

board

To enable a GitHub Project Board the keyword board: is required.

manual:
  board:

Sandbox

Testspace can be customized to manage branches based on a naming content as a sandbox. The default naming is sandbox/*. A Sandbox space provides a functional space for new test development and or experimentation.

sandbox: # optional one or more branch-wildcard entries, defaults to "sandbox/*"

Sandbox spaces have the following attributes:

  • Push New Issue are disabled
  • Email notifications are never sent
  • They are not shown in the Organization view
  • They are excluded from Project Insights

Example

Using a pattern to define branches with specific naming along with one explicit named branch.

sandbox:
 - newtest/*
 - sandbox/*
← SpecificationAutomation →