How to test DHF project that uses multiple databases about marklogic-unit-test HOT 4 CLOSED

My proposal includes:

1. Using a filter parameter that will filter the suites and or tests

• The new nested structure introduced with 1.0.beta helps in structuring the tests and is a good start already but filtering brings more flexibility as like selecting different tests or suites in different folders (think tags and folder)
• filters can be regex, basic substring, etc.
  • We can use a simple textbox for typing the filter, the filtered tests and or suites will then be returned after applying the filter (async ?)
• It will be really cool for the web ui to somehow reproduce that nested structure so that unticking a suite will also untick all the descendants and vice-versa

2. Offering an optional application parameter (port, db, more ?) to switch on the fly or otherwise fall back to the default config (the properties offered in ml-gradle cover parts of that)

• this is easier with api calls as the dbClient can be changed from one suite to another
• the web ui currently does not offer any capability in this regard (switching the port might be useless though, the context db could be enough)

from marklogic-unit-test.

+1 to this request - at the moment, my test database has indexes mimicking both the staging and final databases in a DHF4 project.
It would be useful to have marklogic-unit-test support the creation of two databases as per the data-hub and the ability to unit test groups against their corresponding database.

from marklogic-unit-test.

The general case for this issue (selecting a subset of tests to run) is being tracked and managed with #77.

I think the DHF specific issues are being tracked and worked as a part of the DHF itself. There are efforts under way to make it easier to perform test setup and run tests against specific sets of DHF databases. At this point in time I don't believe marklogic-unit-test needs to make any specific set of changes to support testing DHF projects, but that DHF will need to set forth patterns and helper methods to make it easier to test DHF project code.

from marklogic-unit-test.

I'm going to close this issue as I believe the solution lies within the DHF project. I also believe there are several open issues that reference testing a DHF project.

from marklogic-unit-test.