@distantcam@CFDevelop If you imagine something like tasks you can assign, change status, update, close, delete, comment on, and especially if some of those actions should be prohibited in some states, then you'll get more benefit
@TheTechGoose@mpocock1 You model your app/component/business logic as a finite state machine and tell your test runner how to verify the current state and move between them, then generate test cases based on that finite state machine. Essentially, each test case generated is a path around the graph
@mpocock1@arahansen I like not having to define the return type (is it JSX.Element, React.ReactNode or React.ReactElement<any, any>? Oh right, I need to add null), plus it shows errors near the problem.
Playground: https://t.co/cY36fXLgph