[M10.1] E2E suite on real VMs

Open
  • Is something wrong?
#243 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
devops, docker, github-actions, typescript
Domain
devops, infrastructure, testing

Research direction

Start by reading .github/workflows/e2e-nightly.yml and the existing CI work in issue #137, then identify how the project deploys and runs its scenarios. Implement the three pnpm e2e:* commands using Hetzner Cloud VMs tagged by run id. Done means all six scenarios run green three nights in a row and forced failures leave no orphaned VMs; this is blocked on #137 and an owner-provided Hetzner token.

Written by the indexing model from the issue text.

Description

blocked priority:P2 task track:cross-cutting
Task id

M10.1

Track

X: cross-cutting

Scope
  • Implement pnpm e2e:provision, pnpm e2e:run, pnpm e2e:teardown used by .github/workflows/e2e-nightly.yml (Hetzner Cloud via hcloud, resources tagged with the run id, teardown deletes by tag).
  • Scenarios: deploy, rollback, failover, backup and restore, preview, upgrade.
Acceptance criteria

Nightly run green three nights in a row; no orphaned VMs after a forced failure.

Depends on

M4.5

Blocked by

CI-1 (#137) and a Hetzner token set by the owner.

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.