From: Lee P. <le...@sa...> - 2007-12-13 16:02:58
|
OK, If I understand correctly, I should be committing the "new" BIF testGroups to both \test\branches\test.3.2.0\ooRexx\base\bif\ AND \test\trunk\ooRexx\base\bif\ Take another look and see if what I just committed is correct. Lee Rick McGuire wrote: > Lee, > > The test cases are done the same way the main code tree is done. The > trunk version is ALWAYS for the release under development. For other > releases, there's either a branch under a branches directory or a > releases directory. Releases branches are frozen and should not be > getting updated. > > So, what Mark was saying is if you are developing tests for/using 3.2.0, > then you should be working from this SVN directory branch: > > http://oorexx.svn.sourceforge.net/svnroot/oorexx/test/branches/test.3.2.0/ > > That branch will be specifically for testing 3.2.0, and at some point, > we'll freeze the branch by moving it to releases. Tests in this branch > will test only the 3.2.0 behavior. > > Tests added to that branch should also be merged into the trunk test > build (the one you are currently using) and will get updated as > appropriate for changes in 3.3 (or whatever we end up calling it). So, > what you really need to be doing at this point is taking all of the new > tests groups that have been developed, and merging them back into the > 3.2.0 branch. I think Mark has sort of been doing this, but it looks > like his last update was a week ago. > > The segregation by release number is not by creating a subdirectory in > the SVN tree, but rather by leveraging the capabilities of SVN itself to > manage things as different branches. > > Rick > > On Dec 13, 2007 10:20 AM, Lee Peedin <le...@sa... > <mailto:le...@sa...>> wrote: > > I am writing the testGroups and testing using the 3.2 interpreter. > > The framework I am using is whatever happens to be in > \test\trunk\framework. I do a fresh SVN > update every morning to pull any changes to the framework. > > It might help if the test folder was named as "test320" and then > another test folder be created > named "test330". The test330 folder would be a duplicate of > test320. As changes are made to the > interpreter that affects a testGroup, then the corresponding > testGroup in test330 could be modified > to reflect the change. > > Just my 2 cents. > > Lee > > > > > Mark Miesfeld wrote: > > On 12/11/07, Lee Peedin <le...@sa... > <mailto:le...@sa...>> wrote: > >> I'm writing the testGroups using 3.2. Since the development of > 3.3 is still quite "young", I wonder > >> if these tests that behave differently under 3.3 should be > flagged with an "if" statement that tests > >> the current version of ooRexx (3.2 do one thing, anything else > do a different thing). > > > > I think it is a big mistake to be developing the tests using the 3.x > > version of the test suite. > > > > (It is an even bigger mistake to put in 'if's so that the test would > > pass under different versions of the interpreter.) > > > > I spelled this out in detail in a post to the list a while back. I'm > > not sure if no one read it, or if people disagreed and just > didn't say > > anything. > > > > We should be doing the test development using: > > > > oorexx/test/branches/test.3.2.0 > > > > and the 3.2.0 version of the interpreter. > > > > The 3.2.0 branch of test should test the 3.2.0 interpreter. If there > > is *any* change in the 3.3.0 interpreter, then running the 3.2.0 test > > suite under the 3.3.0 interpreter should produce an error. > > > > We need to develop a really good 3.2.0 test suite, that actually > > *tests* the 3.2.0 interpreter. That test suite should catch any > > changes between the 3.2.0 and the 3.3.0 interpreter. > > > > Tests added to the 3.2.0 branch of the interpreter should be forward > > ported to trunk. If there is a change in the 3.3.0 interpreter then > > the test forward ported to trunk should fail. The test in *trunk* > > should be fixed and a good comment put into the commit log as to why > > the test is changed. Then, if you take the 3.3.0 version of the > test > > and run it on 3.2.0 it *should* fail. > > > > If a test uncovers a bug in the 3.2.0 interpreter, then the test > > should not be changed in the 3.2.0 branch of the test suite. It > > should *always* fail under a 3.2.0 interpreter. When / if the bug is > > fixed in the 3.3.0 interpreter then the test should be updated in > > trunk with a good comment in the test log as to why it was changed. > > > > If there is some change in the interpreter from version x.x.x to > > y.y.y, like the syntax error number returned under a specific > > situation, then the x.x.x version of the test should *fail* when > it is > > run under a y.y.y interpreter. The y.y.y version of the test should > > pass under a y.y.y interpreter and it should fail under a x.x.x > > version of the interpreter. > > > > -- > > Mark Miesfeld > > > > > ------------------------------------------------------------------------- > > > SF.Net email is sponsored by: > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services > > for just about anything Open Source. > > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > <mailto:Oor...@li...> > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > ------------------------------------------------------------------------- > > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > <mailto:Oor...@li...> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > > ------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel |