1. Node.js version 12, and npm
2. Contentful CMS account

##Configuration Configuration options can be set in a .env file(see .env.example) or vie ENV variables on your machine. For Europeana API connections you may additionally use a .apisrc.js file in the root of your project, see the relevant README for more explanation.

# install package dependencies
$ npm install

# serve with hot reload at localhost:3000
$ npm run dev

# build for production and launch server
$ npm run build
$ npm start

# generate static project
$ npm run generate

# serve storybook with hot reload at localhost:6006
$ npm run storybook

# generate static storybook
$ npm run build-storybook

For detailed explanation on how things work, refer to Nuxt.js docs.

To run end-to-end tests, you will need Docker Engine and Compose installed and the docker service running.

Run tests with:

$ npm test

npm run test:unit just runs everything.

To run a single file: npm run test:unit -g tests/unit/[REST_OF_FILE_PATH]

npm run test:e2e and npm run test:e2e:ci just run everything.

If you've manually started the test server with: NODE_ENV=test npm run stack:up, then you can for example:

Run only the header.feature file using path.

npm run test:chrome:headless tests/features/header.feature

Run only the "header" feature test using its name.

npm run test:chrome:headless -- -p all --name header

Run only the "header" feature in the header file.

npm run test:chrome:headless tests/features/header.feature -- --name header

Run everything with your driver of choice.

npm run test:chrome:headless -- -p all

test:chrome:headless can be substituted for the other avialable driver commands test:gecko and test:chrome.

Be aware however that with geckodriver some tests are known to fail as it is not yet feature complete. It is therefore at present of limited use.

Licensed under the EUPL v1.2.

For full details, see LICENSE.md.