Service to host cleanslate fixture apis
-
strategical
- Build e2e soft testing platform
-
sub-problems
- Share and consume fixtures - manually or via tests
- Share and consume mocks of their service
-
Requirements
- A fixture is identified by a unique id.
- A running fixture is identified by unique_id and session_id.
- A fixture has associated scope and cardinality.
- scope: env_id
- cardinalty: number of allowed running instances at any time
- Fixture has a runtime state -> requested, queued, assigned, running, fulfilled, failed, aborted, completed
- Fixture has properties.
- status: stable, unstable, deprecated, deleted
- tags
- owner, signed, etc.
- capacity
- Fixture apis
- get
- details
- request
- status
- yield
- Fixture impl defines below interfaces:
- setup and teardown
- monitoring
- health
- users
- status