The overall process:
- Create user stories with Jira
- Document with Confluence
- Verify the process through manual UI test cases
- E2E Automated tests
- 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
Demo - visiting and analysing stories in Jira
Demo - the documentation created in Confluence
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.
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.