Challenge Overview
Welcome to the Hestia CC QA - I | Unit test Integrated App Challenge. In this challenge, we are looking for you to unit test the existing Angular 2+ Application.
Let us know any question you have!
Project Overview
Hestia is a wholesale distributor of a variety of plumbing and building-related products. Hestia Control Center will be an internal application that will help Hestia modernize its current spreadsheet process and allow their employees better access to data for reporting and analysis.
Technology Stack
- Angular 7
- Jasmine
- Karma
- JavaScript
- NodeJS
General requirements
Code Formatting
- Make sure code is well documented, all classes, methods, variables, parameters, return values must be documented in every single code file, and appropriate inline comments should be provided too where the code is not straightforward to understand.
- Please use clean INDENTATION for all HTML code so future developers can follow the code.
Framework Specific
- Follow the best practices of Jasmine & Karma listed here https://angular.io/guide/testing
- Ref these for guidelines on code coverage. The code coverage is expected to be greater than 85%.
- The test file extension must be .spec.ts so that tooling can identify it as a file with tests (AKA, a spec file).
- Put then spec file next to the file it tests.
Platform
- Desktop: Chrome Browsers (Mac & Windows).
- All other browsers are out of scope. This is an internal application and the client will only be using Chrome.
App Testing requirements
Resources & links
- Existing application to unit test can be found in the forum.
0. General requirements
- Code coverage reports should be enabled.
1. Service tests
- Test all the services created in the application.
- Ref these for guidelines.
2. Component tests
- Test all the components created in the application.
- Test all types of components: component classes, component DOM test, components with async service, components with inputs and outputs, components inside a test host, routing components, routed components, next component tests, components with RouterLink.
- Ref these for guidelines.
3. Pipe Testing
- Test all the pipes created in the application.
- Ref these for guidelines.
Final Submission Guidelines
- Full source code with all the requirements tested.
- Detailed readme in markdown format that describes how to configure and test the app.
- Separate verification document that describes how to verify each of the tested features.
Licenses & attribution
- Third-party assets used to build your item must be properly licensed or free for commercial use. MIT, some modified BSD, Apache 2 licenses are ok. If a library is not commercial friendly you will need to get our approval first.
- Sufficient information regarding third-party assets must be present in your documentation. This includes the author, license info and a direct link to the asset online.
FAQs
After submission as a submitter what should be my next step?
Once the challenge submission phase is over the assigned reviewers are going to review all the submissions based on the challenge scorecard. They are expected to raise all issues found in the submissions they are reviewing. After the completion of review phase the Appeal phase status. In this phase, the submitters should go to the Online Review page, select the project & have a look at the issues raised by the reviewers. If you disagree with the reviewer on any issue/comment, raise an appeal by clicking the "Appeal" button associated with the section and entering the appeal comment.
When & where I can see the challenge results?
After the Appeal response phase is over the results are displayed on the challenge specification page as well as on the online review page.