harshjainnn
bf59ed3c9c
* feat(tests): migrate pod error scenario tests to v2 framework Signed-off-by: Harsh Jain <hjain4815@gmail.com> * chore: drop unrelated file from PR Signed-off-by: Harsh Jain <hjain4815@gmail.com> * refactor: rename assert_no_hang_and_correct_logs to assert_failure_logs_contain Signed-off-by: Harsh Jain <hjain4815@gmail.com> * docs: reference pod_disruption_scenario_plugin.py:234 in test comment Signed-off-by: Harsh Jain <hjain4815@gmail.com> --------- Signed-off-by: Harsh Jain <hjain4815@gmail.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