User Stories - nawa236/StorefrontTestingApp GitHub Wiki
1.) Name: Online Storefront (Epic User Story)
User story: As a Testing Employee, I need an online storefront possessing all of the major functionality of a real webstore so that I can perform automated testing and validation in an environment that our company controls.
Acceptance Criteria: Storefront contains the ability to create a new account, login to an existing account, view my account information and previous orders, view and filter available products, add items to a shopping cart and finalize the order, actual payment processing is not required. Page components are uniquely identified in tags.
Storefront Sub-sections
Account Creation (Points: 5)
Login page (Points: 3)
User settings/info page (Points: 8)
User purchase history (Points: 8)
Multi-Product display with sorting/filtering (Points: 8)
Individual item page (Points: 5)
Shopping cart (Points: 5)
Checkout page (Points: 3)
2.) Name: Bug Framework
User story: As a Project Manager, I need to have the Storefront possess bugs that can be turned on and off so that employees can be trained on a dynamic platform for writing appropriately robust automated web testing and validation scripts.
Acceptance Criteria: Storefront works within specifications when all bugs are turned off. When turned on, a bug only impacts the feature it was intended to impact. Pre-programmed bugs cover common use cases like invalid account information, page navigation issues, incorrect product filtering, broken page elements and checkout errors.
Story Points: 20
3.) Name: Bug Flexibility
User story: As a Project Manager, I need the ability to introduce new bugs at a later date so that itโs easy to adapt to future project needs.
Acceptance Criteria: Addition of new bugs does not require significant rewrites to the adjacent code. Framework for tracking, controlling and assigning bugs supports adding new elements.
Story Points: 8
4.) Name: Sales Demonstrations
User story: As a Sales Engineer, I need to be able to load both a clean site and a site with bugs, so I can use our testing tools to show customers the value of automated testing.
Acceptance Criteria: Ability to load a previously generated bug set and download a company-validated testing script against that bug set.
Story Points: 1
5.) Name: User Bug History (Not implemented)
User story: As a Storefront Administrator, I need the view the history of a user, so that when I am assigning bugs I select different bugs for the user to test against.
Acceptance Criteria: Administrator accounts need to be able to select a user and see a list of bugs the user has encountered.
Story Points: 3
6.) Name: User Bug Grading (Not implemented)
User story: As a Storefront Administrator, I want to rate how my Testing Employee handled a specific bug, so I can determine which bugs were the most challenging and provide additional training opportunities to my team.
Acceptance Criteria: Administrator accounts should be able to review a previous user bug assignment and add a rating or completion score. These scores should be available in other Administrator features, such as the history.
Story Points: 3
7.) Name: Admin Page
User story: As a Test Storefront Administrator, I need an admin page that allows me to see a list of current users and assign storefront bugs to their user account so that I can quickly and easily set up varying bug sets for testing employees to test for.
Acceptance Criteria: Admin page must have list of current accounts. All bugs currently available must be able to be assigned to any user in any logical combination. Admin page is only accessible by users with admin privilege.
Story Points: 3
8.) Name: Server Admin
User story: As a server admin, I need to be able to deploy a buggable storefront website to either a Windows or Linux web server quickly and easily so that my company may use it for employee testing and client demos.
Acceptance Criteria: Final storefront website must be able to be run on either a standard Windows server or Linux server, following well written installation documentation or with a full installer package provided by the team.