https://github.com/gablemathias/init-cypress
E2E Automated Testing using Cypress on a recruiting page
https://github.com/gablemathias/init-cypress
confluence cypress e2e-testing javascript jira
Last synced: 10 months ago
JSON representation
E2E Automated Testing using Cypress on a recruiting page
- Host: GitHub
- URL: https://github.com/gablemathias/init-cypress
- Owner: gablemathias
- Created: 2024-10-29T12:56:21.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-11-21T23:16:22.000Z (over 1 year ago)
- Last Synced: 2025-01-01T06:22:32.691Z (over 1 year ago)
- Topics: confluence, cypress, e2e-testing, javascript, jira
- Language: JavaScript
- Homepage: https://www.init.pt/en/career-init-dcp
- Size: 30.7 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# End-to-End Testing - Cypress - ]init[ Website
The overall process:
1. Create user stories with Jira
2. Document with Confluence
3. Verify the process through manual UI test cases
4. E2E Automated tests
5. Report results
Test Scenario: Successfully send a Job application through the career page on https://www.init.pt/en/career-init-dcp
Test Steps:
1. The user navigates to init.pt
2. The user clicls the 'Career' button.
3. The user scrolldown the page and clicks 'Nothing suitable? Send us an unsolicited application' button.
4. The user fills the form accordingly.
5. The user clicks the 'Send application' button.
Prerequisites: A curriculum and an ID document to attach.
Browser: Chromium v130. Firefox v129
Test Data: Personal information, curriculum, check-boxing preferences
Expected/Intended Results: Once user fill and checkbox the form, the application will be send correctly.
Actual Results: As Expected
Test Status – Pass/Fail: Pass
Two specs, one for each task (Cypress)
The second test passing (Cypress)
Demo - visiting the career webpage and filling the form (E2E Automated Test)
[e2e_filling_form.webm](https://github.com/user-attachments/assets/66a9186f-bb07-408c-a5fc-c32ae7bbb122)
Demo - visiting and analysing stories in
[Jira](https://github.com/user-attachments/assets/b0f3a1a1-13f0-4b7f-84ed-a47d19ef3a1d)
Demo - the documentation created in
[Confluence](https://github.com/user-attachments/assets/4cbf9a20-7959-4b10-95be-0836cc3df92f)
## Images of the process on Jira and Confluence
### Jira
### Confluence
## Conclusion
Jira gives me excellent control over my tasks and stories. When a story needs to be split into different tasks, it provides the necessary tools
and management features.
Documenting in Confluence allows me to review my past work and helps with future tasks. It's crucial to link everything here and add as
much information as possible for anyone to reference. This includes technical issues, troubleshooting, know-how, and workshops.
Cypress is an outstanding tool for creating End-to-End Automated Tests. It uses the target web application and verifies with its auto-reload
feature every time I save the code.
### There is always room for improvement
Revisiting and refactoring the `do_job_application.cy.js` could be a nice idea. I have used a lot of `wait` function calls to pure purpose of
demonstration.