Q1 Background: GIThub is a web-based hosting service for version control using Git. Itis widely used to store code revisions in a single repository. GIThub also provides several other features one of them being, Gists. Gists are mainly used for documentation purposes to share code snippets, notes, files, directories, as well as full applications. Go to https://gist.github.com/ HYPERLINK "https://gist.github.com/", login and clickon New Gist to create a new gist. Gists can have different extensions such as .js, .md, .txt, etc. Create a test scenario which has multiple test cases for the following features: • As a user, I want to create a public gist. • As a user, I want to edit an existing gist. • As a user, I want to delete an existing gist. The test cases should include as much detail as possible.
This document presents a set of test cases written in Gherkin/Cucumber format for testing the features related to public gists on GitHub. Gists are used for sharing code snippets, notes, files, and directories.
The test cases cover the following scenarios:
-
Create Public Gist
- This scenario includes test cases for creating a public gist with and without a registered account on GitHub.
-
Edit an Existing Gist
- This scenario focuses on test cases for editing an existing gist, including scenarios with both active and inactive accounts.
-
Delete an Existing Gist
- This scenario contains test cases for deleting an existing gist, covering different ways of deletion.
The test cases are written using the Gherkin syntax, which provides a clear and structured format for expressing requirements and expectations.
The test cases can be used for manual testing or as a reference for creating automated test scripts. Each test case includes the following information:
- Id Test Case: A unique identifier for the test case.
- Description: A brief description of the test case.
- Feature: The feature or functionality being tested.
- Type: Indicates whether the test case is positive or negative.
- Precondition: Any necessary prerequisites for executing the test case.
- Test Steps: The step-by-step instructions for executing the test case.
- Data Input: The input data required for the test case.
- Expected Result: The expected outcome or behavior.
- Actual Result: The actual outcome after executing the test case.
- Test Date: The date when the test was executed.
- Status: The status of the test case (Passed, Failed, Blocked).
- Error Category: The severity category of any encountered errors (Low, Medium, High).
Feel free to refer to the test cases in the subsequent sections for detailed steps and expected results.