search

marklogic-community / marklogic-unit-test

Automated testing for MarkLogic
https://marklogic-community.github.io/marklogic-unit-test/
Other
13 stars 25 forks source link

marklogic-unit-test migration from roxy #125

Closed thepowderriverfarrier closed 1 year ago

thepowderriverfarrier commented 4 years ago

Can anyone offer some insight please. We followed the online documentation for removing the references for mlUnitTest(Roxy); that included the addition of the mlBundle. Running gradle test against the suites and individual tests allows for the build but does not detect errors in the code.

Subsequent to making the changes we noticed that :8011/test no longer works; it is not reachable.

Any insight would be appreciated.

dmcassel commented 4 years ago

Try /test/, with the trailing slash. I've noticed recently that it doesn't seem to work without anymore (not sure why).

s3-4v commented 4 years ago

I noticed recently too that the trailing slash is definitely required.

thepowderriverfarrier commented 4 years ago

Unfortunately that had been tried also. An mlUndeploy and git pull and mlDeploy did not help.

rjrudin commented 4 years ago

Try going to /test/default.xqy - I know that works for Data Hub tests.

thepowderriverfarrier commented 4 years ago

Thanks but that doesn't work. This became a problem when we migrated from mlUnitTest to marklogic-unit-test 1.0.0.

rjrudin commented 4 years ago

Hmm - try deleting your "build" directory, just to ensure that the ml-unit-test modules are deleted. Also check your modules database after running e.g. mlReloadModules - you want to verify that all the "/test/*" modules are there.

thepowderriverfarrier commented 4 years ago

Thank you but tried that yesterday prior to posting. Removed all references in the cache to ML and did a fresh git pull, mlDeploy. Manually running mlReloadModules results in the error: > Task :mlLoadModules Unable to store properties, cause: build/ml-javaclient-util/module-timestamps.properties (No such file or directory) null It appears the test modules are not being loaded even when called separately.

rjrudin commented 4 years ago

What version of ml-gradle or DHF?

thepowderriverfarrier commented 4 years ago

ml-gradle is 3.12.0. This is currently what the coders are using as a plugin in the build.gradle. I can make the changes locally to test if that would make a difference.

rjrudin commented 3 years ago

Checking in to see if this is still an issue; wondering if an upgrade to ml-gradle would help.

dmcassel commented 1 year ago

@rjrudin the last comment from OP was in 2020 with no response to your comment more than six months ago. I propose closing this ticket as inactive.

rjrudin commented 1 year ago

Agree, closing due to inactivity.