mirror of
https://github.com/IT4Change/Ocelot-Social.git
synced 2025-12-13 07:45:56 +00:00
38f27743f2
I love cypress already. However my suggestion is to create a separate repository that includes `backend` and `web` run full stack tests from there. It is possible to trigger builds in other repositories on Travis CI. So here is my suggestion: We agree to have matching branch names in all related repositories, so `branch-1` in repo `web`, `backend` and `human-connection`. As a start, the developer has to manually update the submodules in the meta repository and trigger a build to run fullstack tests. In the future we might automate this process by triggering builds in other repos. That's possible on Travis CI, see: https://docs.travis-ci.com/user/triggering-builds/ See each repository is responsible to keep their set of unit/integration tests but the meta repository is responsible of carrying out full stack testing. @appinteractive your opinion?
Human Connection - NITRO Web
Build Setup
Install
# install all dependencies
$ cd styleguide && yarn install && cd ..
$ yarn run styleguide:build
$ yarn install
Development
# serve with hot reload at localhost:3000
$ yarn dev
Build for production
# build for production and launch server
$ yarn build
$ yarn start
Styleguide
All reusable Components (for example avatar) should be done inside the styleguide directory.
To show the styleguide
$ yarn styleguide
if you changed design tokens or other styles inside the styleguide, run the refresh command to build the styleguide as a lib
$ yarn styleguide:build