Storyteller comes with an embedded web application to author and interactively execute specifications with a rich client. To launch the application, use the dotnet storyteller open
command described below. See Getting Started for more information about the command line tooling tool distributed with Storyteller.
For specific instructions on using the interactive specification tool, see the following topics:
- The Application Shell
- The Specification Explorer
- The Specification Editor
- Fixture & Grammar Explorer
- Stepthrough Mode for Debugging
- System Under Test Lifecycle
Storyteller 5.0
To launch the specification editor from a command line, type the command dotnet storyteller in the project directory.
Type dotnet storyteller ? to see a list of optional flags.
Storyteller 4.0
To launch the specification editor from a command line, type the command st open [path] where [path] is the project directory of the specification project you want to load. Other options to control how the testing AppDomain is constructed and other explicit overrides are described below:
dotnet storyteller openOpens the specification editor web tool
| Flags | |
|---|---|
| [-f, --framework <framework>] | Override the .Net target framework if you are multi-targeting |
| [-h, --hotreload] | Only for Storyteller development itself |
| [-r, --port <port>] | Optional. Bind to the specified port. |
| [-n, --hostname <hostname>] | Optional. Bind to the specified hostname. |
| [-s, --specs <specs>] | Optional. Override the spec directory |
| [-y, --path <path>] | Optional, override the root directory of the project. Should be very rarely used |
| [----prop:<prop> <value>] | Key/Value data for customized system construction |
| [-p, --profile <profile>] | Storyteller Profile for conditional system construction |
| [-c, --culture <culture>] | Force Storyteller to use this culture in all value conversions |
| [-f, --fixtures <fixtures>] | Optional. Override the fixtures directory |