I can't stress enough how important this is to me and IMO the project. As we found out in the past, no amount of code coverage, JUnit and Mockito are really a substitute for actually running our software in various scenarios.
As part of the IVariables API changes for HOP-2268 I've added a number of topics to integration-tests in PR https://github.com/apache/incubator-hop/pull/451) - variables and parameters : setting, getting, passing, default values, ... - partitioning : static, dynamic, repartitioning - xml : tests the XML Join and XML Add transforms Evaluating results is done simply through logging values and then checking the log to see if certain strings appear. The JavaScript action that I'm using is a test-case not the eventual goal. I've logged https://issues.apache.org/jira/projects/HOP/issues/HOP-2265 and will get to that as soon as I can. Let's write more tests! Cheers, Matt On Mon, Dec 7, 2020 at 4:16 PM Hans Van Akelyen <[email protected]> wrote: > Hi All, > > I am happy to announce that we now have a very basic way of doing > integration tests on workflows and pipelines. A new folder has been > introduced in our repository to contain all these integration tests. They > are easy to create and maintain as they are all standalone Hop projects > that can be added to the gui and be tested locally. > > A small write up has been made here > <https://hop.apache.org/dev-manual/latest/integration-testing.html>. > > Now we have to make/add as many tests as possible, to test as many aspects > of Hop as we can. > > Cheers, > Hans > -- Neo4j Chief Solutions Architect *✉ *[email protected] ☎ +32486972937
