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

Latest commit

 

History

History
58 lines (40 loc) · 2.97 KB

README.md

File metadata and controls

58 lines (40 loc) · 2.97 KB
Raw

Shopozor consumer frontend

Docker images

Development

As a backend developer, you might need to connect your application to the Shopozor's consumer frontend. The development docker image is produced manually upon every PR merging into the dev branch. You can start the consumer frontend like this:

docker run -p 4000:4000 -it softozor/shopozor-consumer-frontend:production-dev

Pull requests

Workflow

  • All Softozor members are whitelisted

  • When a white-listed author opens a PR, she is triggering the corresponding unit and acceptance tests automatically

  • When a white-listed member updates a PR, she is triggering the corresponding unit and acceptance tests again

  • The end-to-end tests are not run automatically because not all necessary components might be ready for such tests, thus reducing the relevance of their results (e.g. it can be that the frontend implements a login functionality but that functionality is not present in the backend yet; in that case, the e2e would fail)

  • When a non-whitelisted member opens a PR, the builder will publish the question Can one of the admins verify this patch? to the PR's comment; in that case, one of Softozor's admins can

    • comment ok to test to accept the PR for testing
    • comment test this please for one time test run
    • comment add to whitelist to add the PR's author to the whitelist

Useful build commands

You can use the following commands in your comments:

  • retest this please: this runs the unit and acceptance tests again
  • test consumer e2e: this runs the end-to-end tests (seems to be currently buggy)

Build statuses

e2e Build Status Acceptance Build Status Unit Build Status

Development setup

Pre-commit hooks

Pre-commit (and pre-push) hooks are configured with husky (see husky section of package.json). You also need to activate the hooks for the graphql and fixtures submodules. To do that, you run

./common/scripts/activate-hooks.sh

Troubleshooting

Upon running the unit tests, you might get an error of the kind (especially on Windows machines):

Cannot find module '[..]/consumer-frontend/node_modules/@quasar/babel-preset-app/node_modules/@babel/runtime/helpers/interopRequireDefault' from 'jest.setup.js'

Following this advice, you can fix it this way:

cd node_modules/@quasar/babel-preset-app && yarn