Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .github/workflows/unit-tests.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
name: Unit tests

on:
push:

jobs:
test-unit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4

- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: "3.12"

- name: Run gc-stack-deploy unit tests
run: make -C caprover/tests test-unit
9 changes: 4 additions & 5 deletions caprover/tests/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,11 @@ setting up and tearing down a CapRover server).

## When to run Tests

Since we have not automated running tests (e.g. in CI), we provide a simple recommendation:
GitHub Actions runs **unit tests only**. It cannot run e2e tests.

* Run the tests locally for every change to `stack_deploy.py` or `stack.example.yaml`

You probably do not need to run the tests when adding/modifying one-click app definitions,
because that build step is in fact run automatically in CI.
For every change to `gc-stack-deploy`, including the YAML file,
and every change to one-click apps,
run the E2E tests locally (`make -C caprover/tests all`)


## Prerequisites
Expand Down
Loading