# Description
Currently conformance tests are one and done, meaning they simulate one
update, and that's it. However it's often useful to simulate multiple
steps, e.g. resources being created and later destroyed. This PR adds
support for just that, having multiple steps in each conformance test,
that all happen in the same stack.
Note that this will be much easier to review ignoring whitespace
changes, since a lot of code indentation changed.
---------
Co-authored-by: Fraser Waters <fraser@pulumi.com>