Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Current »

  1. Code Formatter: Integrate attached formatter in your respective IDE and all files should be formatted using this formatter only.

  2. Sonar Issues: Integrate ‘SonarLint’ in your IDE and configure it for url ‘https://tools.publicis.sapient.com/sonar ’. Select project ‘ENGINEERING.KPIDASHBOARD.CUSTOMAPI’ for ‘customapi’ and ENGINEERING.KPIDASHBOARD.PROCESSORS for processors Please ensure that the file in commit do not have any sonar issue/bug.

  3. Code Coverage: Install ‘Emma’ plugin for code coverage. Code coverage should be at least 90% for any file that is to be merged in ‘Dev_Trunk’ branch. Share screenshot/report of code coverage with the reviewer.

  4. PMD Violations: Integrate 'PMD plugin' in your IDE and configure the rule set - "pmd.xml" which is available in the parent directory of source code.

Documenment

FOR UI :

  1. Code Formatter: Integrate BEAUTIFY (HookyQR) in your respective IDE (suggested : VSCODE)  and all files should be formatted using this formatter only.

  2. Sonar Issues: Integrate ‘SonarLint’ in your IDE and configure it for url ‘https://tools.publicis.sapient.com/sonar/ ’. Select branch ‘ENGINEERING.KPIDASHBOARD.UI’ for ‘UI’ . Please ensure that the file in commit do not have any sonar issue/bug.

  3. TS Lint Issue :  Integrate ‘TSLint By Microsoft’ &&  ‘CSS Lint By Raymond’  in your IDE . Please ensure that the file in commit do not have any TSLINT issue .

  4. Code Coverage: Run Command 'ng test --code-coverage' for code coverage. Code coverage should be at least 90% for any file that is to be merged . Open 'coverage/index.html' and  Share screenshot/report of code coverage with the reviewer. 

  • No labels