[wildfly-dev] Elytron integration tests in WildFly testsuite

Darran Lofthouse darran.lofthouse at jboss.com
Fri Dec 2 06:08:18 EST 2016


On 02/12/16 11:03, Tomaž Cerar wrote:
>
> On Fri, Dec 2, 2016 at 9:11 AM, Josef Cacek <jcacek at redhat.com
> <mailto:jcacek at redhat.com>> wrote:
>
>     The modules would just live side by side - basic would use Elytron
>     configuration, basic-legacy-security would use configuration similar
>     to (or same as) the current server configuration.
>
>
>
> What would this actually mean?
> we will have two copies basic tests suites one running with elytron
> another with legacy security subsystem?
>
> Do I read that right? Please say I am not.

That is correct - we have two security implementations they both need 
testing.

One needs testing for backwards compatibility and regressions, the other 
for equivalent behaviour and then new features and bugs.

Needing to test both was discussed previously so this is more about how 
to separate both and also give the Elytron testing a good foundation to 
start from.

>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>



More information about the wildfly-dev mailing list