<p dir="ltr">I think we should only keep the tests for the conversion between the new config and the legacy config (and the other way around), eventually add more of those.<br></p><p dir="ltr"><br></p>
<div class="gmail_quote">Īn data de 20.11.2012 09:57, "Tristan Tarrant" <<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>> a scris:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11/20/2012 03:47 AM, Navin Surtani wrote:<br>
> Hey all,<br>
><br>
> Nearly finished up with cleaning up the compile errors - should be able to run the test-suite by this afternoon in order to make sure that there aren't any failures. I was wondering, though, whether the tests in the package org.infinispan.config.* should still be making use of the deprecated configuration API? I understand that the point of this migration is to eliminate the use of org.infinispan.config.Configuration within the test-suite, but should just these specific tests still be testing the old method?<br>
><br>
> My personal opinion is that we should still have tests making use of the old API as long as it does exist in the code-base. Speaking with Tristan on IRC last week, he mentioned that the org.infinispan.config.* package is likely to be totally removed in due course. I think that until that does actually happen, we ought to have tests for that code - deprecated or not.<br>
><br>
> Thoughts?<br>
Yes, we need to keep a sufficiently diverse set of "retro" tests so that<br>
we don't risk breaking backwards compatibility.<br>
<br>
Tristan<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</blockquote></div>