6186555c15
* Elastic search krkn-lib integration Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> removed default urls Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * Fix alerts bug on prometheus Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * fixed prometheus object initialization bug Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * updated requirements to krkn-lib 2.1.8 Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * disabled alerts and metrics by default Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * reverted requirement to elastic branch on krkn-lib Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * numpy downgrade Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * maximium retries added to hijacking funtest Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * added elastic settings to funtest config Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> * krkn-lib 3.0.0 update Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com> --------- Signed-off-by: Tullio Sebastiani <tsebasti@redhat.com>
CI Tests
First steps
Edit functional_tests with tests you want to run
How to run
./CI/run.sh
This will run kraken using python, make sure python3 is set up and configured properly with all requirements
Adding a test case
-
Add in simple scenario yaml file to execute under ../CI/scenarios/
-
Copy test_application_outages.sh for example on how to get started
-
Lines to change for bash script
a. 11: Set scenario type to be your new scenario name
b. 12: Add pointer to scenario file for the test
c. 13: If a post action file is needed; add in pointer
d. 14: Set filled in config yaml file name specific to your scenario
e. 15: Make sure name of config in line 14 matches what you pass on this line
-
Add test name to functional_tests file
a. This will be the name of the file without ".sh"
-
If any changes to the main config (other than the scenario list), please be sure to add them into the common_config