(This wiki is based on the personal experience of Oleksandr Antonenko)
Nightmare is a high-level browser automation library from Segment.
The goal is to expose a few simple methods that mimic user actions (like
click), with an API that feels synchronous for each block of scripting, rather than deeply nested callbacks. It was originally designed for automating tasks across sites that don't have APIs, but is most often used for UI testing and crawling.
How to run a particular scenario (loan_renewal) for the current state of the platform:
All scenarios are stored in the platform-core module and easiest way to run tests is to clone this repository, install dependencies and run tests.
The important thing - to run tests it is needed to checkout on the snapshot branch, as far as I understood only this branch is currently up to date.
git clone email@example.com:folio-org/platform-core.git
git checkout snapshot
yarn test-int --run WD:loan-renewal
How to test local changes for UI modules:
I want to demonstrate you flow of running test for new branch:
- Let's create a new directory and go there.
create a package.json file with such content:
- clone platform core (and checkout snapshot branch)
- clone module (or modules) where we have added changes (and checkout branch with new feature)
After that, we should install dependencies for our modules. So we should run yarn in the folder where we have modules and package.json file.
So you should install dependencies in a folder similar to what we have in the screenshot (In this case I have made changes in the ui-circulation module, so I have cloned this module) :
- After that we can go to the platform-core directory and run tests:
- In tests, you should use CSS selectors instead of [data-test...] attributes, cause these attributes will be stripped from the production build and therefore are unavailable when the integration tests run against folio-testing or folio-snapshot.
- Always check the current state of the back-end, cause some dependencies may cause unexpected behavior. (the possible way is to destroy and restart vagrant before running tests)
- You can check out what is going on by:
- providing the
yarn test-int --show
- adding show: true property in nightmare config or particular scenario ( as it shown in the screenshot ):