As per your feedback, pleas find updates as below:
1) Remove commented code. Done
2) Make coverage report optional using command line flag --reporters. Add a new cmd in yarn - test:karma-coverage. - Updated package.json for : "test:karma-coverage" & "test:karma-coverage-once"
3) Add the new coverage directory to .gitignore. Done
From: Dave Page <dpage@pgadmin.org> Date: Thursday, 6 August 2020 at 6:18 PM To: Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> Cc: Pramod Ahire <pramod.ahire@enterprisedb.com>, pgadmin-hackers <pgadmin-hackers@postgresql.org>, Akshay Joshi <akshay.joshi@enterprisedb.com> Subject: Re: Code coverage report generation for JS files
Hmm, this makes me think - if we have enough of the JS infrastructure on the SonarQube scanner server (which is easy to create in the Jenkins job), we could import the lcov reports into SonarQube.