https://github.com/intersectmbo/cardano-test-plans
Cardano-test-plans
https://github.com/intersectmbo/cardano-test-plans
test user-stories
Last synced: 8 months ago
JSON representation
Cardano-test-plans
- Host: GitHub
- URL: https://github.com/intersectmbo/cardano-test-plans
- Owner: IntersectMBO
- Created: 2023-12-06T15:20:19.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-08-16T11:27:04.000Z (over 1 year ago)
- Last Synced: 2025-04-22T02:28:56.780Z (11 months ago)
- Topics: test, user-stories
- Language: JavaScript
- Homepage: https://intersectmbo.github.io/cardano-test-plans/
- Size: 2.24 MB
- Stars: 2
- Watchers: 31
- Forks: 9
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# CIP-1694 User Stories and Test Scenarios Repository
Visit the rendered website here: https://intersectmbo.github.io/cardano-test-plans/
## Introduction
The CIP-1694 User Stories and Test Scenarios repository serve as a resource for Product owners, Developers and Test Engineers to define the features derived from CIP-1694 for each of the components under their responsability, togethr with most relevant requirements and acceptance criteria for such features. The user stories provide a narrative
description of different user interactions, while the requirements and acceptance criteria outline specific conditions and expected outcomes to verify the correct implementation of these features.
## User Stories, Requirements and Acceptance criteria
The [user stories](./userStoryInventoryChangHF.md) in this repository are organized to align with the specifications outlined in CIP-1694, focusing on the various components and tools interfacing with the Cardano Blockchain. Each user story presents features from an end user's viewpoint, capturing the interactions with proposed changes, core functionalities, and expected outcomes. The narratives aim to reflect different stakeholders' perspectives while adhering to the requirements derived from CIP-1694.
## Contribution Guidelines
We encourage contributions from the community to improve and expand the coverage of user stories and test scenarios. If you'd like to contribute, please follow these guidelines:
1. Fork the repository.
2. Create a new branch for your changes:
```bash
git checkout -b user/user-story
```
4. Make your changes and commit them:
```bash
git commit -m "Describe your changes"
```
5. Push your changes to your fork:
```bash
git push origin user/user-story
```
6. Open a pull request on the main repository.
Please ensure that your contributions align with the context and objectives outlined in CIP-1694 and follow any specific guidelines provided in the CIP itself.