Introduce the concept of a "mock bridge" that supports the ability to use a variety of mocking systems. #83
Allow hooks to define the order in which they should be ran. #84
TestSuite to define which
TestCase should be associated by namespace or file path. #85
DisabledIf(string $method, ?string $reason = null) attribute that will only disable the test,
TestSuite if the
$method returns true. #86
Show information about which data set was used when a
#[DataProvider] test fails. #98
Better differentiate between a test failing with a
TestFailedException and a test failing because of an error that was unexpected. #99
Allow ability to override which configuration file should be used on the command line.
Implement ability to define your own plugins defined in
async-unit.json that should be registered with the Application automatically. #80
Allow filtering the tests that are run based on a
TestCase, or test name. #87
Design a comprehensive CLI display for showing a variety of test information.
AssertionFailedException to not require custom methods to display appropriate data. All information that needs to be displayed for a given exception should be part of the
Introduce some functionality that allows showing the diff between things that are/should be diffable.
Introduce a concrete logging implementation that can be defined by the
async-unit.json configuration. #11
Make expectations on active Loop watchers before and after a test is processed
These are features we'd like to support at some point but are not sure how they would be implemented or where they should fall within the timeline.
Support code coverage
Build artifacts for common test reporting formats
Run each TestSuite in its own parallel Worker
Cache the results of the parser step so we can skip it if possible