Migrate from V0

Workspaces: Users can create any number of workspaces to isolate different services and teams. In each workspace, users can choose which directories should be included or excluded when Momentic searches for test files.

Store anywhere: Users can store Momentic test and module YAML files anywhere in their workspace. For example, they can choose to co-locate tests with relevant application source code.

Environment enhancements: Workspaces include environment definitions, which can now read from .env files and environment variables in the shell. This should unlock better secrets management and closer integration with tools like dotenv or (doppler)[https://www.doppler.com/].

Queue command: All commands for queueing executions remotely are now under the queue command (i.e. queue tests, queue suites). Passing the —local or —remote flags is no longer necessary.

Simplified context management: results and inputs have been unified into env and all commands now support the Save to environment option that allows the output of that step to be saved to an environment variable. To read more about these changes, please see the original RFC.

Pushing/pulling entities to Momentic Cloud: For CLI users, we recommend using Git as the source of truth for Momentic tests and modules going forward. Environment variables can be tracked in the momentic.config.yaml (which can read from process.env ) or in .env files. For complex use cases, we recommending using a managed solution like dotenv or doppler .

Hybrid cloud/local runs: Running a test on the local machine that only exists remotely on Momentic Cloud is no longer supported. Running a test locally with an environment that only exists on Momentic Cloud is no longer supported.

Fixtures: Support for defining fixtures locally that run setup and cleanup Bash commands has been removed. We do not believe this feature saw usage from any customer, but please surface feedback if you find this concept useful.