Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DUP: test task #393

Open
1 of 22 tasks
Dianadec opened this issue Jun 5, 2024 · 0 comments
Open
1 of 22 tasks

DUP: test task #393

Dianadec opened this issue Jun 5, 2024 · 0 comments
Labels

Comments

@Dianadec
Copy link
Contributor

Dianadec commented Jun 5, 2024

Description:

[Description of the task]

Acceptance Criteria:

[Note: Use 'Given/When/Then' format if it makes sense to. Otherwise, a simple checklist that can be tested.]

Given that I am a parks visitor
When I am on the booking page of DUP
Then I see a green button

  • the button on this page is green

Development Checklist:

  • ... don't forget to change all the buttons green
  • ... techy
  • ...

Dependencies

Relevant documentation as reference

Definition of Ready

  • Acceptance criteria are included
  • Wireframes are included (if applicable)
  • Design / Solution is accepted by Product Owner (if applicable)
  • Dependencies are identified (technical, business, regulatory/policy)
  • Story has been estimated (under 13 pts)

Definition of Done

  • In progress:
    • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
    • UI meets accessibility requirements
    • Unit tests are written
    • Work is traceable in GitHub
    • PR linked to ticket number
    • If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
  • Code review:
    • Code is peer reviewed and has passed CI/CD tests
  • QA:
    • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
    • Code is potentially shippable to the production environment
    • Functional features have been tested and passed by QA
    • UI components tested by designer
    • Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
  • PO Review:
    • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
    • Reviewed and approved by Product Owner

Notes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant