Integration tests: pull and deploy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
I've love a suite of integration tests against CLI pull and deploy
They should work against the lightning mock. We extend the lightning mock to include responses for the deploy APIs, and we write a bunch of tests which uses the CLI to call out to the mock.
Tests should be stateful and do stuff like:
- deploy a branch new project
- pull a new project for the first time
- change and re-deploy a project
- pull a project that's been changed
These tests should pay particular attention to state and config files
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CLI pull and deploy entry points and the lightning mock, then review existing integration-test conventions. Extend the mock for deploy API responses and cover stateful new-project deployment, first pull, redeployment after changes, and pulling changed projects, including state and config files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100