rubyforgood / rubyforgood/skillrx
E2e testing
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Currently we have both feature tests and system tests for e2e testing.
It would be great to use single approach. Let's move system tests info feature folder and have them separated by controller.
Also, we can replace view tests with e2e tests
- Merge system tests and feature tests
- Substitute view tests with e2e tests
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.
Research direction
Start by inventorying the existing feature, system, and view test locations and reviewing how the current end-to-end coverage is organized. Consolidate system tests into the feature-test area, separate them by controller, and replace view-test coverage with end-to-end tests. Done means the two checklist items are complete without losing existing coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100