Skip to content

Commit

Permalink
Remove all things related to Cram
Browse files Browse the repository at this point in the history
All Cram tests were for scripts that were removed in the previous
commit.
  • Loading branch information
joverlee521 committed Jul 11, 2024
1 parent 7277827 commit fc230a9
Show file tree
Hide file tree
Showing 3 changed files with 0 additions and 16 deletions.
3 changes: 0 additions & 3 deletions .cramrc

This file was deleted.

8 changes: 0 additions & 8 deletions .github/workflows/ci.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,3 @@ jobs:
steps:
- uses: actions/checkout@v4
- uses: nextstrain/.github/actions/shellcheck@master

cram:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
- run: pip install cram
- run: cram tests/
5 changes: 0 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,11 +125,6 @@ Some scripts may require Bash ≥4. If you are running these scripts on macOS, t

Most scripts are untested within this repo, relying on "testing in production". That is the only practical testing option for some scripts such as the ones interacting with S3 and Slack.

For more locally testable scripts, Cram-style functional tests live in `tests` and are run as part of CI. To run these locally,

1. Download Cram: `pip install cram`
2. Run the tests: `cram tests/`

## Working on this repo

This repo is configured to use [pre-commit](https://pre-commit.com),
Expand Down

0 comments on commit fc230a9

Please sign in to comment.