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

Evaluation Form: Challenge Assignment #65

Open
23 of 43 tasks
r-bartlett-gsa opened this issue Jul 26, 2024 · 3 comments · Fixed by #201
Open
23 of 43 tasks

Evaluation Form: Challenge Assignment #65

r-bartlett-gsa opened this issue Jul 26, 2024 · 3 comments · Fixed by #201

Comments

@r-bartlett-gsa
Copy link
Member

r-bartlett-gsa commented Jul 26, 2024

User Story

As a challenge manager, in order to have appropriate evaluation forms linked to my challenges, I would like to assign a challenge and challenge phase to an evaluation form.

Acceptance criteria:

  • A challenge manager can select a single challenge / challenge phase from a list of challenges they have available on their account within an evaluation from creation workflow
    • If the selected challenge has phases, they are listed as separate challenge entries in the list
  • Already assigned challenges or challenge phases to other evaluation forms do not display in the list
  • An assigned challenge and a challenge phase ties the evaluation form to all submissions of that challenge / phase

Development tasks:

Definition of Done

Doing (dev team)

  • Code complete
  • Code is organized appropriately
  • Any known trade offs are documented in the associated GH issue
  • Code is documented, modules, shared functions, etc.
  • Automated testing has been added or updated in response to changes in this PR
  • The feature is smoke tested to confirm it meets requirements
  • Database changes have been peer reviewed for index changes and performance bottlenecks
  • PR that changes or adds UI
    • include a screenshot of the WAVE report for the altered pages
    • Confirm changes were validated for mobile responsiveness
  • PR approved / Peer reviewed
  • Security scans passed
  • Automate accessibility tests passed
  • Build process and deployment is automated and repeatable
  • Feature toggles if appropriate
  • Deploy to staging
  • Move card to testing column in the board

Staging

  • Usability testing: mobile and desktop (Tracy or Marni)
  • Accessibility tested (Marni)
    • Keyboard navigation
    • Focus confirmed
    • Color contrast compliance
    • Screen reader testing
  • Cross browser testing - UI rendering is performant on below listed devices/browsers (Tracy or Marni)
    • Windows/Chrome
    • Windows/Edge
    • Mac/Chrome
    • Mac/Safari
    • iOS/Safari
  • AC review (Renata)
  • Deploy to production (production-like environment for eval capability) (dev team)
  • Move to production column in the board

Production

  • User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)
  • PO / PM approved (Jarah or Renata)
  • AC is met and it works as expected (Jarah or Renata)
  • Move to done column in the board (Jarah or Renata)
@r-bartlett-gsa
Copy link
Member Author

r-bartlett-gsa commented Aug 2, 2024

Image

@r-bartlett-gsa
Copy link
Member Author

r-bartlett-gsa commented Oct 25, 2024

Testing / review notes:

  1. The system allows multiple forms for a challenge / phase. This is intentional for now to allow for more efficient testing of form creation.
  2. Evaluation form tie to a challenge submission cannot be tested until submissions-related user stories are implemented

Both if these items will need to be re-tested in the future as part of other user stories.

@stepchud
Copy link
Contributor

Testing / review notes:

  1. The system allows multiple forms for a challenge / phase. This is intentional for now to allow for more efficient testing of form creation.

@r-bartlett-gsa this is fixed, a challenge phase can have one and only one evaluation form.

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

Successfully merging a pull request may close this issue.

3 participants