Schul-Cloud Client

An implementation of the Schul-Cloud client with NodeJS and Express.

Dev: Master:

Requirements

• node.js 8.7 or later

You might take a look at the Dockerfile to see some more dependencies and latest version informations.

Setup

German docs on installing: Setup SC

Short version:

1. Clone directory into local folder
2. Go into the cloned folder and enter npm install
3. Install nodemon and gulp globally by entering npm install -g nodemon gulp

Run

1. Start the schul-cloud server
2. Go into project folder
3. run gulp watch to run gulp
4. Set the ENV-variable TZ=Europe/Berlin (for windows use set TZ=Europe/Berlin). You can also set the variables SC_TITLE=HPI Schul-Cloud and SC_SHORT_TITLE=Schul-Cloud if you want.
5. run npm run watch to boot the application
6. go to http://localhost:3100

Alternative with browser-sync

1. run gulp watch reload to run gulp with browser sync. It also starts the node-client-server.
2. go to http://localhost:7000

For connecting to the SchulCloud Calendar-Service you have to set export CALENDAR_SERVICE_ENABLED=true.

For connecting to the SchulCloud Notification-Service you have to set export NOTIFICATION_SERVICE_ENABLED=true.

For activating Google Analytics tracking you have to set export GOOGLE_ANALYTICS_TRACKING_ID={TRACKING_ID}.

Theming

Add Themes to /theme directory. Call gulp and node with SC_THEME set to name of directory.
then clear build files and gulp cache with gulp clear

Windows

run set SC_THEME={themeName} without spaces around the equal sign!

How to name your branch and create a pull request (PR)

1. Take the Ticket Number from JIRA (ticketsystem.schul-cloud.org), e.g. SC-999
2. Name the feature branch beginning with Ticket Number, all words separated by dash "-", e.g. feature/SC-999-fantasy-problem
3. Create a PR on branch develop containing the Ticket Number in PR title
4. Keep the WIP label as long as this PR is in development, complete PR checklist (is automatically added), keep or increase code test coverage, and pass all tests before you remove the WIP label. Reviewers will be added automatically. For more information check our Definition of Done here.

Testing

Information: Please make sure that all your changes works on Chrome , Firefox and Safari!
For html/css components please check caniuse.

1. Set the password for the demo user [email protected]
   Ubuntu/Mac: export SC_DEMO_USER_PASSWORD={PASSWORD} (Without braces)
   Windows: set SC_DEMO_USER_PASSWORD={PASSWORD} (Without braces)
2. run npm run test
3. If you want to use another backend url than localhost, set the BACKEND_URL and PUBLIC_BACKEND_URL environment variables (see 1)
4. If you want to list the coverage, run npm run coverage

---

Frontend Testing We are currently using nightwatch.js for frontend testing. The current api documentation can be found here.

1. Start a client server with npm run watch
2. Open another command line and type npm run frontendTests to run tests against chrome and firefox.

In case you want browser specific tests use: ./node_modules/.bin/nightwatch --config nightwatch.conf.js --env chrome or switch chrome with firefox.

Adding new tests:

1. Copy any of the existing tests
2. First test cases should be essentially the same, login, checkups, ...
3. Add your test cases in between the checkups and the browser.end()

Add your test to diff.sh: diff.sh compares the PR Branch with the Master Branch and then adds the tests in case any files where changed for which a test exists.

Commiting

Default branch: develop

1. Go into project folder
2. Checkout to develop branch (or clone for the first time)
3. Run git pull
4. Create a branch for your new feature named feature/SC-Ticket-ID-Description
5. Run the tests (see above)
6. Commit with a meanigful commit message(!) even at 4 a.m. and not stuff like "dfsdfsf"
7. Start a pull request (see above) to branch develop to merge your changes