Staging Domain for Prototype UI

[ohsh6o]

Extended Description

As a FedRAMP reviewer, in order to easily access the demo and test environment, I would like to have a URL where I can easily access the demo environment of the FedRAMP Validations UI prototype with remembering complicated instructions or a hard-to-remember address.

Preconditions

• [x] Approval and guidance from Federalist on setting up a staging pre-prod domain, if any
• [ ] Understand GSA-specific domain options as it applies to this documentation, if applicable and relevant
• [x] Potentially a merge upstream first, per 18F/fedramp-automation#113.

Acceptance Critera

• [ ] Easy to access address for reviewers to access and use prototype.

NOTE: This is just to obtain the domain configuration and guidance, a follow-on story will be written to deploy it and integrate into the Federalist configuration in the repo

Story Tasks

• [ ] Tasks...

Definition of Done

• [ ] Acceptance criteria met - Each user story should meet the acceptance criteria in the description
• [ ] Unit test coverage of our code > 90% (from QASP) this may be fuzzy and hard to prove
• [ ] Code quality checks passed - Enable html tidy with XML code standards as part of the build (from QASP)
• [ ] Accessibility: (from QASP) as we create guidance or documentation and reports (semantic tagging including aria tags): demonstrate with 0 errors reported for WCAG 2.1 AA standards using an automated scanner and 0 errors reported in manual testing
• [ ] Code reviewed - Code reviewed by at least one other team members (or developed by a pair)
• [ ] Source code merged - Code that’s demoed must be in source control and merged
• [ ] Code must successfully build and deploy into staging environment (from QASP): this may evolve from xslt sh pipline into something more
• [ ] Security reviewed and reported - Conduct vulnerability and compliance scanning. threat modeling?
• [ ] Code submitted must be free of medium- and high-level static and dynamic security vulnerabilities (from QASP)
• [ ] Usability tests passed - Each user story should be easy to use by target users (development community? FedRAMP FART team)
• [ ] Usability testing and other user research methods must be conducted at regular intervals throughout the development process (not just at the beginning or end). (from QASP)
• [ ] Code refactored for clarity - Code must be clean, self-documenting
• [ ] No local design debt
• [ ] Load/performance tests passed - test data needed - saxon instrumentation
• [ ] Documentation generated - update readme or contributing markdown as necessary.
• [ ] Architectural Decision Record completed as necessary for significant design choices

[ohsh6o]

We opted for the 10x ASAP program to not pursue a dedicated staging domain and trigger pre-ATO procedures. Closing this along with 18F/tts-tech-portfolio#1360.