Yes i noticed that the *.out was copied to classes as well. I didnt
think to change my CLASSPATH to run the tests from the classes
correct. Actually, you don't have to build derbyTesting.jar - the
*.out files are all copied into the classes directory - but only when
you build (ant all).
So, the steps are:
- run the new test
- copy the .out to the master directory - (this is where it lives in
the subversion source tree)
- build (ant all) so the test files - including the .out files and any
other relevant supporting files go to the classes dir
- If you want to run the test using the jars, use the ant buildjars
target & all required testing files are pulled from the classes dir
into the derbyTesting.jar.
I'll look at making this more obvious in the testing README some time soon.
Or someone else can, of course.
On 5/6/05, Lance J. Andersen <Lance.Andersen@sun.com> wrote:
I believe that is the key and I discovered that myself the other day. The
master *.outs are included in the derbyingTesting.jar
Mamta Satoor wrote:
Did you do a build again after copying the .out file to the master
On 5/6/05, Øystein Grøvlen <Oystein.Grovlen@sun.com>
"DVC" == David Van Couvering <David.Vancouvering@Sun.COM> writes:
DVC> I'm stil learning this harness, but I am pretty sure you can run any
DVC> program with a main() that you want from within the test harness, just
DVC> by adding the .java file to functionTests/tests. I don't think the
DVC> harness has any restrctions on this main() program being
multi-threaded or single-threaded.
I guess I must have misunderstood
something. I thought that I had read
on this mailing list that the ordinary
testing framework did not
support multithreaded tests.
Anyway, I have now
transformed my program into a test. However, when
I run it using RunTest, I
get "No master file was found" even after I
copied the .out file to the
master directory. Do I have to set some
property in order for the test to
find the master file? I was not
able to find anything about this in the
testing README file.