Q2 Go to https://petstore.octoperf.com/actions/Catalog.action and report at least 3 bugs.
This document serves as a bug report in Gherkin/Cucumber format for reporting an identified issue in the system. The bug report follows the structured format of Gherkin to provide clear details about the bug and its expected behavior.
The bug report is written using the Gherkin syntax, which allows for easy understanding and communication between stakeholders, developers, and testers. Each bug report includes the following information:
- Title: A brief title summarizing the bug.
- Preconditions: The necessary conditions or steps required to reproduce the bug.
- Steps: The step-by-step instructions to reproduce the bug.
- Actual Result: The observed result or behavior when executing the steps.
- Expected Result: The expected result or behavior of the system.
- Test Date: The date when the bug was reported.
- Status: The current status of the bug (Open, In Progress, Resolved, Closed).
- Error Category: The severity category of the bug (Low, Medium, High).
Feel free to refer to the bug report sections for detailed steps, observed and expected results, and the current status of the bug.
A lot of people underestimate how tricky bug identification can be until they find something unusual in the garden or inside the house. I’ve noticed that using image-based tools makes the process much faster, especially when trying to figure out whether an insect is harmless or something that needs attention. I recently came across free bug identifier and liked how it explains insect behavior and habitat instead of only giving a name. Makes learning about insects much easier for regular users.