Developer Story

Our bread-and-butter critical path in Coder is:

• Can I create a workspace?
• Does it build?
• Can I stop that workspace?

Furthermore, it's desirable to ensure that this critical path is operating as expected with all combinations of user roles.

We want to E2E test these paths.

V1

In V1, we E2E tested that workspaces could be created and cancelled. We used an xstate model to generate all paths.
We also had a matrix of users with various roles.

MVP

An MVP of this ticket does not need to consider the entire matrix that we'd like to cover, but we do want some automated
coverage that we can up/down workspaces. One such test could even bypass the UI at the start and simply use the API.

Acceptance Criteria

• We have a MVP E2E test that issues up/down (start/stop) on a workspace
• It is not required to step through the UI at the start
• It is not required to create a matrix for all user roles

Considerations

• we use playwright and have an e2e package in progress
• coderd binary can be run directly, and have these tests performed against them
• Add in checks to ensure workspaces are not left hanging.