There's an issue open for this but I think it's more of a milestone. WWT believes strongly in good testing practices. We value TDD, a robust automated test harness, and fast feedback. SwiftCurrent shouldn't just be a joy to use to enable powerful, flexible production code. It should also provide a really great testing experience.

Maybe this means a new package designed specifically for testing, maybe it just means writing code that is friendly to test, that's for the team to figure out.

We know we've succeeded at this milestone when there's an easy-to-use API for testing workflows (as quantified by usability tests). At minimum it should include things like:

• asserting that the correct workflow was launched
• asserting that a workflow abandons
• asserting that a FlowRepresentable proceeded
• asserting that a FlowRepresentable backed up
• having a friendly end-to-end experience that moves through a workflow and finishes.