Skip to content

test: correcting the existing test case so that we will get the alert#59

Open
karthikkesarla wants to merge 1 commit intomainfrom
fix/test-case-fix-for-ConsulIsDownAlarm
Open

test: correcting the existing test case so that we will get the alert#59
karthikkesarla wants to merge 1 commit intomainfrom
fix/test-case-fix-for-ConsulIsDownAlarm

Conversation

@karthikkesarla
Copy link

@karthikkesarla karthikkesarla commented Jun 16, 2025

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

Consul-service robot tests we have alert by name "ConsulIsDownAlarm" to make this alert activated we need the test case "Consul Is Down Alert" as it was failing we modified it and wrote tin below mentioned 2 ways.

Description
What for is that MR?
Consul-service robot tests we have alert by name "ConsulIsDownAlarm" to make this alert activated we need the test case "Consul Is Down Alert" as it was failing we modified it and wrote tin below mentioned 2 ways.

Implementation details
Consul-service robot tests we have alert by name "ConsulIsDownAlarm" to make this alert activated we were deleting all the pods but it was not activating the alert. To make that alert active we need have used 2 approches 'changing memory to very low values' and 'changing the readiness probe unhealty'. In this tests we first capture the existing details and change to make pods unhealty and once alert is activated revert it back to orginal values.
Finally we were asked to use memory approach, keeping that removing the other changes.

Test cases
"Consul Is Down Alert" we had now re-wrote it into 2 ways "Consul Is Down Alert Using Memory Changes" and "Consul Is Down Alert Using Readiness Probe"

Related Tickets & Documents
Related Issue #
Closes #
This also needs this changes to be in place: Netcracker/qubership-docker-integration-tests#3

QA Instructions, Screenshots, Recordings

Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.

Breaking Change checklist

If your PR includes any deployment or processing changes, please utilize this checklist:

  • Does it change any deployment parameters, logic of their working or rename them?
  • Did update from previous version tested with the same set of deployment parameters?

Added/updated tests?

  • [ X] Yes
  • No, and this is why: please replace this line with details on why tests
    have not been included
  • I need help with writing tests

[optional] Are there any things to highlight or double check?

[optional] What gif best describes this PR or how it makes you feel?

@github-actions
Copy link

github-actions bot commented Jun 16, 2025

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@karthikkesarla
Copy link
Author

the below changes are need for this to be successful Netcracker/qubership-docker-integration-tests#3

@karthikkesarla
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

@karthikkesarla karthikkesarla changed the title Made the changes to test case so that it will work as per the rule. fix : updated the test case so that it will work as per the rule. Jun 17, 2025
@karthikkesarla karthikkesarla changed the title fix : updated the test case so that it will work as per the rule. test: correcting the existing test case so that we will get the alert Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants