wlsf82 / wlsf82/gitlab-cypress
Create GUI test for "Deploy key creation"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 105
- Forks
- 30
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Description
As a test pre-condition, the root user has to be authenticated.
Following is the page for the creation of a new public deploy key: http://localhost/admin/deploy_keys/new.
Remember to add the new test to the cypress/e2e/gui/allButProject.cy.js file, anywhere between the access token creation and deletion (preferably closer to another test of the same domain - admin/.)
If you need more information, don't hesitate to tag me (@wlsf82).
Also, remember to follow the project's contributing guidelines.
Cc. @Fabricioperrone.
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 with cypress/e2e/gui/allButProject.cy.js and review the nearby access-token and admin/ tests. Authenticate as root, open http://localhost/admin/deploy_keys/new, and follow the existing test patterns for deploy key creation. Done means the new GUI test covers creating a public deploy key and is placed between access-token creation and deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, javascript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100