-
Notifications
You must be signed in to change notification settings - Fork 10
test_harness - additional multichain tests #491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_harness - additional multichain tests #491
Conversation
- Fix bugs with math operations - trait FromWhole for easy creation of UnifiedNum from f64 & u64
- div, mul, div_floor, checked_div and other - primitives - targeting - fix whole number conversion to UnifiedNum
…dditional-multichain-tests
…dditional-multichain-tests
…dditional-multichain-tests
- RejectState - Unhealthy ApproveState - transitioning to Healthy ApproveState
// Address 7 | ||
// ( | ||
// *PUBLISHER_2, | ||
// keystore_options(&format!("{}_keystore.json", *PUBLISHER_2), "ganache7"), | ||
// ), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added it as a comment to be easier for addition if the need arises.
channel_tick_timeout = 5000 | ||
# for test_harness make it larger | ||
# Default: 5000 | ||
channel_tick_timeout = 8000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still get timeouts in test_harness sometimes, we have to check why this is - performance issue or something wrong with the services
Test is failing as it's comparing the Validator message, which contains a |
redis_pool: deadpool::managed::Object<crate::db::redis_pool::Manager>, | ||
#[allow(dead_code)] | ||
db_pool: deadpool::managed::Object<crate::db::tests_postgres::Manager>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the Object
was getting dropped tests failed randomly.
Object hold the Pool of Pools, so we must hold these values until the Application struct get drop itself
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comments made the test logic much easier to understand. I will use a similar approach when writing more complex tests.
Adds additional multi-chain tests:
RejectState
for CAMPAIGN_2 (on Chain # 1337) with multiple Events.RejectState
to unhealthyApproveState
(is_healthy: false
) for CAMPAIGN_2ApproveState
to health for CAMPAIGN_2