Home

• [Git flow rules] (working-with-git)

Development rules

• [Test driven development] (#tdd)
• [Review process] (#review-process)
• [Code styles] (#code-styles)

TDD

Development process is based on Test Driven Development. This approach means test-first development where you write a test before you write the implementation.

**:exclamation:**For us, it's generally means that no commits are allowed without unit / integration tests covered the new functionality (no excuses about adding them later).

Usual process for adding new feature:

1. Create navigation map (list) - story decomposition;
2. Create tests for new functionality;
3. Run all tests and see if the new tests fail;
4. Implement the task;
5. Run tests again and make sure they all passed;
6. Refactor code until it's perfect.

Review process

Usually when you are working on the task you have a choice to work:

• in the separate branch or
• clone the repository

And, then, create a pull request in the end to merge changes into the master.

Every pull request firstly must be reviewed inside the team. It must collect at least 3 ninja stars in general (usually, 2 stars from the team members and, at least, one star outside the team).

Code styles

• [TypeScript] (../wiki/code-style:-typescript)
• [HTML + CSS] (../wiki/Code-style:-HTML)