Skip to content

☂️ Improved (e2e) test coverage for common flows in the product #12332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
2 of 33 tasks
bpmct opened this issue Feb 27, 2024 · 3 comments
Closed
2 of 33 tasks

☂️ Improved (e2e) test coverage for common flows in the product #12332

bpmct opened this issue Feb 27, 2024 · 3 comments

Comments

@bpmct
Copy link
Member

bpmct commented Feb 27, 2024 •
edited by stirby
Loading

Before a release, we should run (end-to-end?) tests to ensure that developer and admin flows are not broken.

Note

Some of these have not been split into individual issues yet. If you want to take one, please create any necessary issue(s). We need your help understanding which components of the product are easy to test, or if they are tested already via other tests.

These flows are ranked in the order of how common they are combined with how error-prone they are.

Error-prone/critical areas:

Common flows

  • Create workspace
    • via coder create against a template with parameters
    • via the UI against a template with parameters
  • Connect to a workspace
    • via a coder_app
      • does the proper path resolve
      • does a websocket session remain open
    • via VS Code Desktop
      • can a direct connection be established
      • can a DERP connection be established
    • via terminal
  • Update workspace
    • against a template with no new parameters
    • against a template with a new parameter introduced
    • against a template with a type: select parameter updated so the previous option is not available
    • passing an ephemeral parameter via the UI
  • Update template
    • via the template editor
    • via the CLI
    • creating a promoted template version
    • creating a non-promoted template version
    • with variables supplied via a variables file
    • with variables supplied via the --var flag
  • Scheduling
  • Audit log
@cdr-bot cdr-bot bot added the chore label Feb 27, 2024
@stirby stirby mentioned this issue Mar 1, 2024
Closed
24 tasks
@stirby
Copy link
Collaborator

stirby commented Mar 1, 2024

Added a list of scheduling flows.

@bpmct bpmct changed the title ☂️ Improved test coverage for common flows in the product ☂️ Improved (e2e) test coverage for common flows in the product Mar 6, 2024
@bpmct bpmct mentioned this issue Mar 6, 2024
Closed
@stirby
Copy link
Collaborator

stirby commented Apr 26, 2024

@bpmct @sreya Is this aligned with our current progress in testing coverage? Maybe we make a plan and revisit tracking methods here?

@stirby
Copy link
Collaborator

stirby commented May 31, 2024

We're happy with e2e tests now.

@stirby stirby closed this as completed May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bpmct @stirby