3 Commits

Author	SHA1	Message	Date
Naz	ff1c17d661	Bumped e2e test coverage thresholds ... refs fc9f8aebc1 - With integration & regression test suites included in the e2e coverage reports the coverage has jumped up nicely. We should keep the threshold as hight as possible from accidentally reducing the coverage quality	2022-11-30 10:41:32 +07:00
Naz	5dd6cb909f	Tweaked code coverage config for e2e tests ... refs https://github.com/TryGhost/Toolbox/issues/475 refs https://github.com/TryGhost/Toolbox/issues/117 - The frontend/src folded would never get picked up by a code coverage tooling as scripts there are dynamically minimized and served from the server - There's nothing to cover under frontend/public - Logic behind these changes is the same as in second referenced issue	2022-11-29 14:22:27 +07:00
Naz	3e0ec26408	Introduced separate config for e2e tests ... refs https://github.com/TryGhost/Toolbox/issues/475 - Having a single coverage config file for unit and e2e type of tests doesn't play well for tracking coverage progress. The unit test ones are run often when developing, so one can observe the changes in coverage. The e2e tests are ran mostly on CI environment and have different purposes/reach comparing to unit tests.	2022-11-17 09:58:39 +07:00