Addition:

When running a UI module's test suite there are three potential sources for the actual version of the test being pulled in:

FOLIO's release repository: npm-folio
FOLIO's continuous integration repository: npm-folioci
A local checkout of the module, brought into ui-testing by yarn link or otherwise

Pulling the tests from the release repository makes sense if the purpose is to test a candidate for a stable Stripes platform release, since it will pull in a version of the test matching a released version of the UI module.

Otherwise, the intention is probably to test the very latest version of the UI module(s) and for that, uI-testing should be installed from npm-folioci.

In order to develop the test itself (not just run it against a developing UI module), the test programmer would probably yarn link a local checkout of the UI module into ui-testing

To run a Stripes module's Nightmare tests:

and then, to test the users module:

Options for running individual tests from a module are explained in test-module's help page:

These commands would test a module in the default FOLIO application with default test settings (see URL and settings in ui-testing/folio-ui.config.js). The current README.md in ui-testing explains how to change the test URL and other test settings.

Have added help page to test-module.js: