Hey Figs, I wrote an early draft of an API for interoperability of back-end components in test-frameworks.
That's kind of wordy, so for now I'm referring to this as "test-interop". The draft and interfaces are here: https://bitbucket.org/mindplaydk/test-interop/src/master/ The idea is to provide a simple kind of streaming message protocol for test-frameworks to back-end components, e.g. pretty-printers, reporters, etc. For now, it's a few interfaces based on the semantics and properties of JUnit XML reports, which are fairly universal. The interfaces can't really enforce call order, so for now, there's a mandate about dispatching messages chronologically, and for test-listeners to throw exceptions if messages arrive out of order. (It's not too shaky, but not exactly rock-solid, and I'm definitely open to ideas.) Anyhow. Wondering if there's any interest in this? Cheers, Rasmus -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/51203204-0ac8-42b2-a301-2f729bb0e60a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
