Alex ShtinandGitHub 2e9635e1ee Refactor: use Eventually in xdc tests (#7243) ...

## What changed?
<!-- Describe what has changed in this PR -->
1. Use `Eventually` in xdc tests.
2. Extract namespace creation logic into helper functions.
3. Created few other namespace management helpers which blocks until
operation is committed.
4. Left approximately 1 million TODOs for future refactoring.

## Why?
<!-- Tell your future self why have you made these changes -->
1. Random sleeps is a source of flakiness and slowness. 
2. Unify namespace creation code, reduce code duplication.

Before: 

![image](https://github.com/user-attachments/assets/c5d6ffea-a937-4082-aa92-45d6f4513082)
On this PR:

![image](https://github.com/user-attachments/assets/b3e4b776-6ef4-47f4-bf21-47c93a42e90d)


## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
Run tests multiple times.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
I might create some new flakiness. Future monitoring over xdc tests is
needed. With all new helpers, fixes should be simple.

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->
No.

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
No.

2025-02-05 21:49:27 -08:00

..

history_require_test.go

Improve historyrequire test helper (#6674)

2024-10-21 10:16:07 -07:00

history_require.go

Refactor: use Eventually in xdc tests (#7243)

2025-02-05 21:49:27 -08:00