## Description Add a command that allows the end user to run the cypress tests against their big bang deployment. This should also include the standardization and centralization of a cypress testing library that gogru and bbctl can both reference and use. ## Requirements/Scope - A new command that - Will run cypress tests against the big bang cluster - Allows the user to additively select - All tests - Predefined list of tests - Individual package tests - Will output the results of the tests as they finish `bbctl test CHART_NAME [--all-charts | --charts=CHART_NAME_1 --charts=CHART_NAME_2...]` - `bbctl test CHART_NAME` will run a given packages tests. - `bbctl test --all-charts` will look at all packages deployed in the cluster and try and run all their charts. - `bbctl test --charts=chart1 --charts=chart2` will run tests for `chart1` and `chart2`. All tests will continue to live in the individual packages as helm unit tests and be runnable with the [in-cluster](https://repo1.dso.mil/big-bang/product/packages/gluon/-/blob/master/docs/executing-cypress.md?ref_type=heads#executing-from-within-the-cluster-using-gluon) gluon testing methodology. ## Out of Scope - Moving package cypress tests out of their respective packages - Writing a new suite of tests - Ensuring our tests test all packages ## Duration 6 weeks ## Team Tools & Automation ## Epic Team Members - Leads: - @andrewshoell - Team: - TBD ## Dependencies N/A ## Risks - Scope creep - Ambiguous requirements/acceptance criteria - Too much work for a single epic ## Acceptance Criteria See [Requirements](https://repo1.dso.mil/groups/big-bang/-/epics/303#requirementsscope) ## Related Issues and/or Epics TBD