Welcome to the second part of the final project. In this self-paced module, we will focus on automating test cases for the website “https://thinking-tester-contact-list.herokuapp.com/”.
Your Role:
- Assess Test Cases: Review the test cases you created in Part 1 of the project.
- Add a column called “Can be automated” and “Reason not automating”.
- For each test case, decide whether it can be automated. If it can, write yes in the “Can be automated” column next to that test case. If it can’t be automated, write no in the “Can be automated” and put the reason the test case can’t be automated into the “Reason not automating” column.
- Initialize Repository: Create a new repository using GitHub Desktop to host your automated test suite.
- Create a new folder for the repository.
- import this folder into Cypress and follow the Cypress project setup instructions (Review Lesson 3 if you need a refresher).
- Develop and Automate Tests: Using Cypress automate each of the test cases you marked as “Can be automated”. Write test scripts that accurately reflect the steps and expected results outlined in the manual test cases. Make sure your tests are diverse. Include regression tests to ensure that previously identified defects are not reintroduced and API and Security Tests. Utilize tools we’ve discussed and practiced using throughout the course.
- GitHub Actions Deployment: Configure GitHub Actions within your repository to automate the execution of your test suite.
- Set up a workflow that triggers the execution of your tests on each push or pull request to the repository.
- There should be a separate job for Cypress UI tests, Security tests, and API tests.
- Include the ZAP GitHub Action as a job in your workflow to perform security scanning.
- Test Execution and Validation: Commit and push your automated tests to your GitHub repository. Monitor the workflow execution and verify that all the tests are running successfully. Review the test results and investigate any failures or issues.
Submission:
Ensure that your repository includes the automated tests, the GitHub Actions workflow file, and any other necessary configuration files.
Remember to maintain good code organization, clarity, and readability in your test scripts. Use appropriate assertions and validations to ensure accurate test results. If you encounter any challenges or have questions along the way, don’t hesitate to seek assistance.