-
Notifications
You must be signed in to change notification settings - Fork 123
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
Spike: There is a plan for the end-to-end test framework for testing simplified Kubernetes Conjur configuration management #2063
Comments
Prerequisites / Assumptions / Separate WorkRequired Helm chartsThe E2E scripts that are being developed as described in Issue #2062 depend upon the
Conjur deployments are assumed availableFor the E2E workflow described below, it's assumed that a Conjur instance has been deployed and is available
Required WorkflowThe test setup should support the following workflow:
Issues Which will Accomplish the Creation of an E2E framework=========================================================
=========================================================
=========================================================
=========================================================
========================================================= |
There is an initial draft in #2062.
The goal of this spike is to complete the draft in #2062 that describes the test plan we'll use for the improved Conjur configuration management project. The outcome of the spike is a thorough draft described in #2062 and broken out into small (1-3 day) issues.
Once written, the test plan will be reviewed by the quality architect.
The text was updated successfully, but these errors were encountered: