Do not fail verification test when provider state doesn't exist.

[danilchican]

Is there any way to do not fire error when state on a provider side is not defined?

There are cases when Consumer defines state, e.g. "products exist" but Provider shouldn't do something special inside provider state method. But if method with @State is not defined it fails.

How to do not fail without having @State?

[joklek]

A workaround I see is to use the same @State method for a few states.

This does not avoid having the states in the producer, but you don't have to create a separate method, just use @State({"default", "products exist"}).

OR use the default state in the consumer. Ignoring missing states might lead to unexpected outcomes, but if this option is introduced, it would be nice to get warnings about every missing state

[uglyog]

I've added an @IgnoreMissingStateChange annotation which you can add to your test class

[danilchican]

@uglyog great! Which version has this improvement?

[anto-ac]

@uglyog great! Which version has this improvement?

I don’t think it has been released yet.

[uglyog]

Just been released :-D (4.1.12)

[danilchican]

@uglyog , great! Thanks for quick improvement.