lvarayut / lvarayut/relay-fullstack
Testing and CI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 978
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
At the moment I have a project that whenever the repo get's pushed to has circle ci
* build the project
* tests graphql end point query works
* uses selenium to
* navigate to a few pages to make sure they load
* test form validation errors such as sign up form
* takes a picture which circle ci stores
I'd like to add some of this testing to this project.
I'm thinking the first pull request would simply be to get the project to build on ci.
Then go from there.
Browser Testing
* mocha
* Selenium
Unit Testing
* Jest
CI Contentious Integration
* circle ci
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
Review the project's existing build configuration and the requested CircleCI workflow. Start by determining how the project should build in CI, then identify the existing GraphQL, Selenium, and Jest test entry points; done means the project builds successfully in CI before browser and unit testing are added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, javascript, nodejs, react
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100