Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

test command crashes if no triggers database is defined #254

Closed
michaelgursky opened this issue Jun 9, 2014 · 2 comments
Closed

test command crashes if no triggers database is defined #254

michaelgursky opened this issue Jun 9, 2014 · 2 comments
Labels
Milestone

Comments

@michaelgursky
Copy link

If there is no triggers database defined, "ml test" crashes with an XDMP-NODB error, making it difficult to integrate into a CI build. It would be good if this were caught in the xquery code and returned in a different manner. It seems the testing UI turns this into a "NO TESTS RUN" message.

@dmcassel dmcassel added the bug label Nov 21, 2014
@grtjn
Copy link
Contributor

grtjn commented Feb 23, 2015

I think it should be pretty easy to test if ml.triggers-db is empty, but how should the system respond? It could skip the CPF related tests silently. Depends what purpose those CPF tests really serve I guess, not sure I know them well enough to judge. Moreover, the UI should ignore it too. That is not ignoring it silently, but failing (red border) with no particular message..

@grtjn grtjn modified the milestone: 1.7.3 Jul 7, 2015
dmcassel added a commit that referenced this issue Aug 17, 2015
Fixed #254: skipping cpf tests if no triggers db
@grtjn
Copy link
Contributor

grtjn commented Aug 17, 2015

Fixed in dev

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants