This pull request fixes the failing test for the alert actions in the Redux store. The test was previously failing due to an assertion error where the expected and received states did not match## Screenshots
Before:
After:
< add a screenshot of the UI af
ter your change >
Open questions and concerns
@ragesoss , @Abishekcs Could it be that some promises were not being resolved, leading to excessive waits and causing the 'call retries were exceeded' error? I opted to use async/await to ensure that actions complete in the intended order. Does this approach improve the readability and reliability of the tests?
Odd that this was failing locally, but not on CI. It must be something related to behavior that differs between different node environments, or something else particular to the testing environment.
What this PR does
This pull request fixes the failing test for the alert actions in the Redux store. The test was previously failing due to an assertion error where the expected and received states did not match## Screenshots
Before:
After: < add a screenshot of the UI af
ter your change >
Open questions and concerns
@ragesoss , @Abishekcs Could it be that some promises were not being resolved, leading to excessive waits and causing the 'call retries were exceeded' error? I opted to use async/await to ensure that actions complete in the intended order. Does this approach improve the readability and reliability of the tests?