Illustrative example of the interaction between API and UI automation, showcasing the capabilities of testing automation across different levels of the application.
- Tools
- Steps
- Running Automated Tests
- Jenkins Build
- Example of Allure Report
- Integration with Allure TestOps
- Integration with Jira
- Telegram notifications
- Example of test execution (UI part only)
- Login to Demo QA: An automated login process to the Demo QA platform.
- Adding a Book via API: Utilizing API requests to add a book to the system.
- Deleting a Book via UI: Deleting the previously added book through the web application's UI.
- Verification of Deletion: Confirming the successful deletion of the book by verifying its absence from the list.
- Ensure you have the necessary dependencies installed.
- Update the base URI in the test file to match your Demo QA API endpoint.
- Run the tests and observe the results.
To run all the tests:
gradle clean demoqa_api
To start the build, go to the "Build with parameters" section, select the necessary parameters, and click "Build".
- TASK (set scope/task to execute)
- COMMENT (optional parameter to add notes that will be displayed in report)
Registration on the Jenkins resource is required for access to Jenkins.
Example of Allure Report
Integration with Allure TestOps
On the Dashboard in Allure TestOps, you can see the statistics of the number of tests: how many of them are added and executed manually, how many are automated. New tests and test run results are sent through the integration with each build.
Integration with Jira
Integration with Allure TestOps and Jira is implemented. In the Jira task, you can see which test cases were written as part of the task and their execution results.
Report notification in Telegram via Bot
After the build is complete, a Telegram bot automatically processes and sends a message with the test run report to a specifically configured chat.
In the Allure reports for each test, a video of the test execution is attached along with a screenshot.