evanion / platform-web Goto Github PK

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Description
We should set up a code review tool for the codebase.

• Code Climate
• SonarQube

Description
The application should have a data driven system to build it's menus.

<Menu name="mainMenu" />

It would ask a menu service that would get the menu structure from a backend service (BE). In this application the BE would just be a mock similar to how the user service works with auth.
Check semantic docs to see what menu items they have as examples by default, and how a menu structure could be represented in a JSON object.

Description
We need to decide on the stratergy for unit tests.
There are a number of options available, and currently included in the codebase.

• puppeteer - ex Routes/Login/__tests__/
• Enzyme
  • Enzyme + react-intl wrapper - ex Routes/ForgotPassword/Routes/Request
• Cypress

It would be good if we could run the E2E tests separately from the regular unit tests.

Puppeteer
Developed by google, successor to Phantom.js. Runs the tests in an actual browser.

• Easy to understand syntax
• Runs in headless Chrome

Enzyme
Developed by AirBnB. Runs the tests in a virtual DOM like environment.

Cypress
Similar to Puppeteer. Have built in support to record videos and screenshots of the tests. In order to assist in resolving failing tests.

Task
Evaluate different options and write a report on each with its pros and cons. as well as how they affect the developer experience (DX). The tests should be able to run in a CI environment.

Validate commit messages and decide convention

Description
We should add additional unit tests to the codebase, in order to cover as much as possible.

Description
We should have a exception manager added to the application. In order to automatically collect exceptions that happens in the browser. it should be tied in to a CI system in order to track in relation to releases.

Description
Flesh out account page to contain sections for account information, etc. mock in the User service