I have been working with the Pipelines builtin stages (again). I have been creating a comprehensive (I hope) test suite for each
with all its options. I am also comparing them to the CMS
Pipelines User's Guide and Reference V6R4. And as a result, have
some updates for some stages. For example, for the BETWEEN stage there are 11 tests similar to
this: [note: your email agent may wrap long lines]
[The o: ? stage collects the outputs from all the tests and formats them.] These tests for BETWEEN are collected into a single .njp pipe file, with some documentation. For BETWEEN, there are actually 14 tests because the current version fails 3 tests, the new one passes all. When compiled and run, it looks like this:
Here, because the failures cause runtime errors, I have actually put them in as comments. In cases where simply the output is wrong, it and the expected value are displayed. The repeated tests then use the new version of BETWEEN. (Separately, all the tests have been run with the new version, and all pass.) I have two versions of the test pipe. The one above, between_tests_new.njp and a similar one, between_tests.njp without the second, "_new", tests. It is this version that I think should be published along with the new version of the stage between.nrx. Actually I have not been able to test that new stage version with
it's real name. Java/NetRexx complains that there are multiple
versions of the between class. So I have named the new version between_new.nrx.
It also has the package statement commented out, as it causes
errors in testing. I do have and almost identical file, between.nrx,
with the "right names," and package statement ready for
publication; I have not been able to actually test it. I believe
the package statement, package org.netrexx.njpipes.stages,
is correct, but maybe things have changed. Bottom line: I have 4 files ready for submission. Two with "_new" suffixes for testing, and two without probably ready for publication. What is the best way to proceed and submit these? (Recognizing that I have several more such sets nearly ready to go.) Jeff _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
Hi Jeff,
If you have a SourceForge id, I’ll grant you committer privileges so you’ll be able to jsut push changes to the source cose repository. That seems the best way going forward. René. On 24 Oct 2019, at 19:26, Jeff Hennick <[hidden email]> wrote:
_______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
Free forum by Nabble | Edit this page |