Challenge Overview
Welcome to the “CRM - Claims Unit Test Coverage”. We are currently building an internal web application for a client. This application will be divided into frontend and backend, and has numerous modules. This challenge will focus on the claims module.
CONTEXT
PROJECT CONTEXT
The client has requested to build a full stack application that involves both the backend REST API (Nest.JS) and a frontend application (Angular 9). This application will allow customer service representatives to view claims details about their members.
CHALLENGE CONTEXT
The goal of this challenge is to improve the unit test coverage of both the backend and frontend applications.We are going to measure unit test coverage on a per-file basis, not averaged across all files, so please make sure that you take that into account for figuring out what your coverage percentage actually is.
CHALLENGE DETAILS
Technology and Framework
- NestJs
- Typescript
- NodeJs 12.x
Existing integration
Note - the current code is integrated between the frontend and backend, and is deployed to Heroku. You MUST NOT break this integration or introduce mocks into the code to support your tests! You can enhance the mock data by adding new records, but you can't break any existing code.
Requirements
- The main goal of the challenge is to bring the backend unit test coverage to 100% and the frontend unit test cover to 85%, on a *per file* basis
- For each 1% less in UT coverage will be 1 point deduction in major requirements
- Unit test must not depend on any external system (database, etc...)
- All lint errors must be fixed
- Existing source code will be provided in the forum
- Any errors in the existing tests will need to be fixed - the current tests likely fail and aren't complete