Add e2e tests
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the discussion in Flagsmith/ci#4 and inspect the existing workflow that calls the locally-referred actions. Define how the end-to-end run will access the Flagsmith API without leaving persistent test artefacts, using an ephemeral environment, a nightly-reset environment, or a local API instance. Done means the workflow runs the actions and verifies their results directly through the API.
Written by the indexing model from the issue text.
Description
(...) a workflow that calls the locally-referred actions and verifies the result directly via the Flagsmith API. (...)
Originally posted by @khvn26 in https://github.com/Flagsmith/ci/pull/4#discussion_r2724636039
Consider this will potentially spam the API with test artefacts. Ideally e2e testing should be pointed at environments with ephemeral data, e.g. a nightly-reset test environment, or a local instance of the API.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from Flagsmith/ci
-
Difficulty 4/5 3-5 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·