Closed mike-gangl closed 3 months ago
did a preliminary run-through for "shared services" that need to be validated, and have the following set of components to test:
apgs - https://github.com/unity-sds/unity-system-test/tree/main/features/apgs
application_catalog - https://github.com/unity-sds/unity-system-test/tree/main/features/application_catalog
core_services - https://github.com/unity-sds/unity-system-test/tree/main/features/core_services
data_catalog - https://github.com/unity-sds/unity-system-test/tree/main/features/data_catalog
project_isolation - https://github.com/unity-sds/unity-system-test/tree/main/features/project_isolation
security -
workflow_authoring_tool - N/A Out of prototype scope
workflow_catalog - https://github.com/unity-sds/unity-system-test/tree/main/features/workflow_catalog
@mike-gangl any updates on this one? Is this something that @brianlee731 or @GodwinShen can help test?
The test plan has been written, but the procedure has not been 'implemented'. i'll go back and check where i left off with this and how these tests were marked as shared service validation tests.
I noticed that there is one feature file for multiple requirements (indicated in the table). Is this required? I'm starting to realize that it might be best to create multiple feature files... @mike-gangl your thoughts? we can talk about this tomorrow during our tag-up.
@brianlee731 ping for status
The direction was to focus on the following requirements shown here: https://github.com/unity-sds/unity-project-management/blob/main/docs/phase_2_requirements.csv
The current status is that we've writing out the validation tests on Testrail and executing them. Link to testrail: https://cae-testrail.jpl.nasa.gov/testrail/index.php?/milestones/view/2080
Define Validation Tests for Shared Services (non-functional)
Acceptance Criteria:
As managed services, these must also fulfill managed services requirements: