On 02.02.2023 18:02, Rick McGuire wrote:
On Thu, Feb 2, 2023 at 11:53 AM Rony G. Flatscher <rony.flatsc...@wu.ac.at>
wrote:
While looking into what is needed to formulate native tests I found
... cut ...
The native test code is not located under test/trunk, but rather in
main/trunk/testbinaries.
Why are these files not located under test/trunk/testbinaries? What is the
reason for this?
They were moved there years ago so that they always get built as part of the build rather than
requiring a separate build step that was more difficult to set up.
Thank you.
So the testbinaries get generated whenever ooRexx gets built (residing in the bin directory
afterwards), so they just do not get installed.
Hmm, then speculating from test/trunk/ReadMe.first:
1.) Simple command line, running the entire test suite at one time.
--------------------------------------------------------------------
NOTE: Starting with ooRexx 4.0.0, the test suite contains tests that require
external executables. These are tests to exercise the ooRexx native API.
Running these tests makes things slightly more complex. There are 3 options
here, simplest to hardest.
1.) Skip the native API tests altogether. The best option if you are just
getting familiar with the test suite.
2.) Download the pre-compiled external binaries for your system. Details on
picking and installing the proper set are in the Release.notes in the doc
directory.
NOTE: at this time the pre-compiled binareies are NOT available. If you are
interested enough to want the pre-compiled binaries, post a note to either
the ooRexx developers list or the ooRexx users list requesting the binaries
and one of the developers will make thenm available.
3.) If you understand, somewhat, compiling C / C++ files you can compile
your own binaries as part of running the automated test suite. Details for
this step have not been written, just post a question on the ooRexx
developers list or the ooRexx users list.
Start in the root directory, the directory that contains this file. The
Rexx program that runs the tests is: testOORexx.rex
That is the only file you need to use to begin with. We will assume that
you are using option 1 above, skipping the tests for the native API
binaries. The program file will run the ooRexx test suite. Depending on
the horse power in your system this could take 5 or 6 minutes, maybe longer
on a real old system.
Once you invoke testOORexx everything runs automatically and you will see
the results printed on the screen when the test finishes.
The argument: '-X native_api' in the following examples tells the framework
to eXclude the native API tests.
So one needs to build ooRexx and then make its bin directory available on PATH and can then run the
native tests successfully?
Is that correct? Is there anything else to be aware of?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
