Marvin, Definitely interesting. I've considered such an approach before, but never saw it implemented, so kudos. There's a few things I see missing.
- Examples. How do I use these things? What does a test based on Justify look like with CDI support? - Publishing. This library isn't built/deployed out to maven central or bintray as far as I can tell. This means users need to build it themselves. Convenience binaries are so useful, especially when there's no build script. John On Mon, Feb 22, 2016 at 11:39 PM Marvin Toll <[email protected]> wrote: > DeltaSpike Colleagues, > > > > We haven't shared this until now. since there was not a lot to talk about > until it was working. > > > > Ford has partnered with an Open Source team to utilize a 100% rule-based > testing approach that wraps JUnit 4. As part of this effort, the CdiRuner > was mostly eliminated in favor of a JstConfigureCdiForMethodRule Rule: > > > > > > http://ped.gtcgroup.com/_jst_configure_cdi_for_method_rule_8java_source.html > > > > > A light weight JstSatisfyAnnotationOnTestMethodRunner runner does remain if > required: > > > > > > http://ped.gtcgroup.com/_jst_satisfy_annotation_on_test_method_runner_8java_ > source.html > <http://ped.gtcgroup.com/_jst_satisfy_annotation_on_test_method_runner_8java_source.html> > > > > The Open Source project is called Justify at: > > > > http://pedcentral.com/hands-on/justify/ > > > > Any thoughts or feedback are welcomed. > > > > _Marvin > >
