Probably should add - any duplication should only be for security tests
- not everything else in there!
On 02/12/16 11:08, Darran Lofthouse wrote:
On 02/12/16 11:03, Tomaž Cerar wrote:
> On Fri, Dec 2, 2016 at 9:11 AM, Josef Cacek <jcacek(a)redhat.com
> <mailto:firstname.lastname@example.org>> 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
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
> wildfly-dev mailing list