Integration tests setup #947
Conversation
shaunxw
added
the
tests
tests/integration/src/setup.rs
Outdated
| DappsStaking::on_finalize(System::block_number()); | ||
| System::set_block_number(System::block_number() + 1); | ||
| DappsStaking::on_initialize(System::block_number()); |
There was a problem hiding this comment.
Can we run the hooks for all pallets?
AFAIK, they cannot be just fetched and iterated over, while being able to call hooks on them (hope I'm wrong though!).
There was a problem hiding this comment.
Not a problem. I was originally thinking to add them as needed. After some second thoughts, I agree with you, will do so that we don't need to worry about adding more pallets overtime.
There was a problem hiding this comment.
Great! Now that I rethink what I wrote, there has to be a way to do it since it's done when network is live 😅
There was a problem hiding this comment.
Updated. I checked all pallets manually and added hooks if there are defined. ParachainSystem was skipped as it requires extra mocks but not required for tests. The pallets could be iterated via some tricky way, like macro or the runtime enum definition, but IMO it would be a bit overkill and edge cases would make more complicated.
| mod setup; | ||
|
|
||
| #[cfg(any(feature = "shibuya", feature = "shiden"))] | ||
| mod proxy; |
There was a problem hiding this comment.
I will add astar as well after we merge pallet-proxy-astar PR.
Pull Request Summary
Set up integration tests. Moved current
pallet-proxytests into integration tests.Check list