Tatsh / wiswa / 25671022573 / 5

100%

master: 100%

push

github

tests/test_postprocess: cover typescript non-npmjs registry branch

`_project_type_badges`'s typescript arm only emits the npm shield
badges when `package_json.publishConfig.registry` is empty or points
at `https://registry.npmjs.org`. The false branch - registry set to
a non-npmjs host such as `https://npm.pkg.github.com` - was a
branch-coverage gap (`postprocess.py:562->exit`) because every
existing typescript test either left `publishConfig` empty or set
`private=True`, which short-circuits at the case guard above.

Add a focused regression test that drives `post_process_steps` with
`project_type='typescript'`, `private` unset, and
`package_json.publishConfig.registry='https://npm.pkg.github.com'`.
Empty `dependencies` and `devDependencies` are required to keep the
downstream `_typescript_badges` helper from raising `KeyError`.

The assertions target the precise shield URLs
(`img.shields.io/npm/v/`, `img.shields.io/npm/dm/`) rather than the
broader `npmjs.com` string, because `_typescript_badges` legitimately
emits `npmjs.com/package/...` URLs for individual dependency badges
- only the project-level NPM shields are gated by the registry
check.

Branch coverage is now 100%.

Signed-off-by: Andrew Udvare <audvare@gmail.com>

485 of 485 branches covered (100.0%)

Branch coverage included in aggregate %.

2512 of 2512 relevant lines covered (100.0%)

1.0 hits per line