Unit Test refactor

.gitignore

@@ -7,6 +7,7 @@
 .vscode/
 
 assets/newrelic.js
+output/
 coverage/
 tests/
 platforms

.npmrc

@@ -0,0 +1 @@
+audit-level=moderate

angular.json

@@ -230,7 +230,10 @@
             "include": ["projects/v3/src/**/*.spec.ts"],
             "assets": ["./projects/v3/src/assets/icon/favicon.ico", "projects/v3/src/assets"],
             "styles": ["projects/v3/src/styles.scss"],
-            "scripts": []
+            "scripts": [],
+            "watch": false,
+            "progress": false,
+            "sourceMap": false
           }
         },
         "lint": {

docs/coverage-run-cookbook.md

@@ -0,0 +1,82 @@
+# Coverage Run Cookbook (v3)
+
+> Fast, repeatable coverage workflow for this repo.
+
+## Quick Rules
+
+- Use targeted coverage runs first; use full-suite only after targeted changes pass.
+- Use workspace-relative include paths starting with `projects/v3/src/...`.
+- Save logs under `./output` for every run.
+- Prefer `ChromeHeadless` for CI-like behavior.
+
+## 1) Targeted Coverage Run (Single Spec)
+
+```bash
+npm test -- --code-coverage --browsers=ChromeHeadless --include='projects/v3/src/app/pages/tabs/tabs.page.spec.ts' > ./output/coverage-targeted-tabs.log 2>&1
+```
+
+## 2) Targeted Coverage Run (Multiple Specs)
+
+```bash
+npm test -- --code-coverage --browsers=ChromeHeadless \
+  --include='projects/v3/src/app/pages/activity-mobile/activity-mobile.page.spec.ts' \
+  --include='projects/v3/src/app/pages/topic-mobile/topic-mobile.page.spec.ts' \
+  --include='projects/v3/src/app/pages/tabs/tabs.page.spec.ts' \
+  --include='projects/v3/src/app/pages/chat/chat-list/chat-list.component.spec.ts' \
+  --include='projects/v3/src/app/pages/chat/chat-preview/chat-preview.component.spec.ts' \
+  > ./output/coverage-targeted-mobile-chat-tabs-topic.log 2>&1
+```
+
+## 3) Full-Suite Coverage Run
+
+```bash
+npm run test -- --code-coverage --browsers=ChromeHeadless > ./output/full-suite-coverage.log 2>&1
+```
+
+## 4) Open HTML Coverage Report
+
+```bash
+open coverage/v3/index.html
+```
+
+Open folder-level reports directly when needed, for example:
+
+- `coverage/v3/src/app/pages/activity-mobile/index.html`
+- `coverage/v3/src/app/pages/topic-mobile/index.html`
+- `coverage/v3/src/app/pages/tabs/index.html`
+- `coverage/v3/src/app/pages/chat/chat-list/index.html`
+
+## 5) Tail Logs Quickly
+
+```bash
+wc -l ./output/full-suite-coverage.log && tail -n 60 ./output/full-suite-coverage.log
+```
+
+## 6) What Is Noise vs Blocker?
+
+Usually non-blocking during this repo’s test runs:
+
+- `NG0303/NG0304` unknown element/property warnings
+- Ionic runtime warnings in templates
+- SVG/asset `404` warnings in Karma output
+
+Treat as blockers:
+
+- TypeScript compile errors
+- Karma `ERROR` status
+- `Some of your tests did a full page reload!`
+
+## 7) Prevent Common Flaky Failures
+
+- Do not assign `window.location.href`/`location` directly in unit tests.
+- Spy/mock navigation helpers or Angular Router instead.
+- If a component destroys external instances in `ngOnDestroy`, initialize mocks with `destroy` spies in tests.
+- Add explicit branch tests for keyboard guards (`Enter`, `Space`, unsupported keys).
+
+## 8) Suggested Workflow
+
+1. Run targeted specs for changed files.
+2. Fix compile/runtime test failures.
+3. Verify folder-level coverage HTML for target modules.
+4. Run one full-suite coverage pass.
+5. Save/hand over logs from `./output`.