Expose component testing code to outsiders

[ilyvion]

I wanted to test my component's output, and I was informed of TestLayout:

yew/yew/src/virtual_dom/mod.rs

Line 327 in a4eb965

pub(crate) struct TestLayout<'a> {

Unfortunately, it's private to the crate, so it cannot be used by outsiders. Consider making TestLayout public or possibly create something more suitable for general use that could help with testing component output expectations.

Questionnaire

• I'm interested in implementing this myself but don't know where to start
• I would like to add this feature
• I don't have time to add this right now, but maybe later

[jstarry]

Thanks for the issue!

I think it makes sense for this functionality to live in a yew-test crate. It can start with a simple with a way to render a component to an empty dom and assert the shape of the resulting html.

[bobbbay]

It's been over a year, any update on this?

[ranile]

This will be in a tests module:

#[cfg(tests)]
pub mod tests;

It can't be in it's own crate because it depends on interval APIs (like VDiff)