minor enhancements

[duncdrum]

found some oddities while looking into #800. This makes error handling for faulty test-suites more robust, and adds an alternative means of using a local copy when developing.

There is a regression from upstream with npm.Install that still needs more investigation.

see #649

[joewiz]

@duncdrum Could you explain the purpose of the "exception fixture"? Looking elsewhere in the commit, I don't see where it's used.

[joewiz]

@duncdrum A minor thing, not about this PR per se: I just noticed that view.xql wasn't included in the cleanup of XQuery file extensions in #701. You consider slipping that into this PR too - as another minor enhancement?

[duncdrum]

@joewiz sure the fixtures are normally used in the unit test of the custom mocha interface to exist's xqsuite. they are all based on real responses and corner cases observed in the wild.

generator-exist/test/mock_xqs.js

Lines 6 to 9 in c4585f6

	const monoCase = require('./fixtures/mono-case.json')
	const multiCase = require('./fixtures/multi-case.json')
	const multiSuite = require('./fixtures/multi-suite.json')

I added the xml in the hope to have an idea for how to use it in a future test, that doesn't involve debugging/fixing exists, mochas, and my own code. My current approach can't handle mocha encountering errors of this type, much like xqsuite can't handle NPEs.

Ultimately users get more descriptive errors now, and the CI fails when it should. Designing a working test for this will be a lot of work for very little actual gain.

[joewiz]

Thanks for the info on fixtures! That's a neat capability. The PR looks good to me.

[github-actions]

🎉 This PR is included in version 6.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀