Known Tradeoffs and Pitfalls

[cspray]

A library in early-development with big ambitions and 1 developer is bound to have some form of tradeoff or pitfall when running it. While these are intended to be kept to a minimum there are some things that I have intentionally punted down the road to be addressed in future versions while the core functionality of the framework is fleshed out. When I knowingly make one of these tradeoffs I'll document it here.

• You can currently only define a #[TestSuite] using the TestSuite::class syntax. Parsing different argument types statically presents challenges that we can best address in a version release focused on static analysis improvements.
• If you have multiple TestCase hooks defined the order in which they are invoked is non-deterministic. This is due to the way the underlying parser library works. There are plans to have an explicit invoking order in future versions.
• The paths passed to the CLI tool are fairly brittle and may not resolve relative paths correctly. This is an issue I anticipate resolving in the 0.4.0 release.