This is a draft.

Our team is currently cracking away at creating more content to make our Handbook something increggdible. Soon, you'll be able to explore it fully. In the meantime, think of it as a carton of eggs, each section packed with the potential to deliver something eggceptional.

Testing and Quality Assurance

We develop high-quality software, which is why we not only test our code base but always employ the most suitable and simple solutions.

On the Front-end, it really depends on the project, but we mostly focus on testing specific calls that handle logic or data processing.

On the Back-end side, we fully test our applications with unit tests and integration tests through the database.

The minimum coverage requirement does not increase the quality of the software – developers should feel encouraged to test their code, and this should be a discussion in pull request reviews. Coverage is a great tool that can be used to indicate missing tests, but it is not enforced.

Great tooling and developer happiness are prominent factors to make developers want to write tests for their code.

Good code reviews are the fundamental step to achieving code quality. Discussions taken during pool requests are what most elevates the quality of software, not a rule in some computer program.

Style consistency is key for us, and for that reason, we use tools to ensure that all the code is style-consistent. This is run on the developers’ machine but also during continuous integration.