| 1 | Feature: running Exosphere applications
|
| 2 |
|
| 3 | As an Exosphere developer
|
| 4 | I want to have an easy way to run an application on my developer machine
|
| 5 | So that I can test my app locally.
|
| 6 |
|
| 7 | Rules:
|
| 8 | - run "exo run" in the directory of your application to run it
|
| 9 | - this command boots up all dependencies
|
| 10 |
|
| 11 |
|
| 12 | Scenario: running the "test" application
|
| 13 | Given a set-up "test" application
|
| 14 | When starting it
|
| 15 | Then my machine is running ExoComm
|
| 16 | And ExoComm uses this routing:
|
| 17 | | COMMAND | SENDERS | RECEIVERS |
|
| 18 | | users.list | web, dashboard | users |
|
| 19 | | users.listed | users | web, dashboard |
|
| 20 | | users.create | web | users |
|
| 21 | | users.created | users | web, dashboard |
|
| 22 | And my machine is running the services:
|
| 23 | | NAME |
|
| 24 | | web |
|
| 25 | | users |
|
| 26 | | dashboard |
|