Skip to content

Conversation

@bogdanS98
Copy link
Contributor

@bogdanS98 bogdanS98 commented Jul 19, 2024

This PR introduces a new pallet used to mock block skipping when testing wasm-deploy.
The idea behind it is described in this ticket in detail.
I'll add a broader description before marking the PR as ready for review.

Closes #486.

@bogdanS98 bogdanS98 changed the title Implement and test potential solution for mock-skip blocks on runtimes Implement pallet for mock-skip blocks on runtimes Jul 19, 2024
Comment on lines 34 to 38
#[cfg(test)]
mod mock;

#[cfg(test)]
mod tests;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the whole content of mock and test are only supposed to be used when instant-seal is available, wouldn't it make more sense to instead move the feature flag macro above the mod imports here? Then we can remove all the annotations from the mock.rs and test.rs files itself.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True 👍🏼 I forgot about those macro flags when testing some things earlier

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can even move them into the pub mod pallet {} definition? Not sure if that works but then no extra macros were needed.

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.

Implement and test potential solution for mock-skip blocks on runtimes

3 participants