<div dir="ltr"><div>That is probably fine, but! it should be done differently.<br><br></div><div>instead of duplicating whole testsuite (and adding extra hour to execution and extra headaches with intermittent problems and duplication of maintenance)<br></div><div>I would suggest that all security related tests get extracted to new "security" testsuite module and than only that part is duplicated.<br><br></div><div>This way we will have all security related stuff in one place.<br></div><div><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 2, 2016 at 12:09 PM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Probably should add - any duplication should only be for security tests<br>
- not everything else in there!<br>
<div class="HOEnZb"><div class="h5"><br>
On 02/12/16 11:08, Darran Lofthouse wrote:<br>
> On 02/12/16 11:03, Tomaž Cerar wrote:<br>
>><br>
>> On Fri, Dec 2, 2016 at 9:11 AM, Josef Cacek <<a href="mailto:jcacek@redhat.com">jcacek@redhat.com</a><br>
>> <mailto:<a href="mailto:jcacek@redhat.com">jcacek@redhat.com</a>>> wrote:<br>
>><br>
>> The modules would just live side by side - basic would use Elytron<br>
>> configuration, basic-legacy-security would use configuration similar<br>
>> to (or same as) the current server configuration.<br>
>><br>
>><br>
>><br>
>> What would this actually mean?<br>
>> we will have two copies basic tests suites one running with elytron<br>
>> another with legacy security subsystem?<br>
>><br>
>> Do I read that right? Please say I am not.<br>
><br>
> That is correct - we have two security implementations they both need<br>
> testing.<br>
><br>
> One needs testing for backwards compatibility and regressions, the other<br>
> for equivalent behaviour and then new features and bugs.<br>
><br>
> Needing to test both was discussed previously so this is more about how<br>
> to separate both and also give the Elytron testing a good foundation to<br>
> start from.<br>
><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> wildfly-dev mailing list<br>
>> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
>><br>
><br>
<br>
______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>