Skip to content

feat(4915): Terms negative path – integration test fixes#143

Open
OMpawar-21 wants to merge 9 commits intodevelopmentfrom
enhc/DX-4915
Open

feat(4915): Terms negative path – integration test fixes#143
OMpawar-21 wants to merge 9 commits intodevelopmentfrom
enhc/DX-4915

Conversation

@OMpawar-21
Copy link

Terms negative path – integration test fixes

Scope

  • Terms negative-path only (Test040–Test059 in Contentstack017_TaxonomyTest.cs).
  • No new test cases; no Taxonomy-only or positive-path changes.

Changes

  1. LogContext alignment
    Fix TestScenario so it matches the test method name (e.g. Test046_... logs "Test046_Should_Throw_When_Move_NonExistent_Term" instead of "Test047_..."). Apply for all Terms negative-path tests (Test040–Test059).

### Summary
Adds an automated HTML report generator for the .NET CMA SDK integration tests.
### Changes
- Test helpers for capturing HTTP traffic, assertions, and test context
- Python script to parse TRX, Cobertura coverage, and structured output into an HTML report
- Shell script to orchestrate test execution and report generation
- Updated integration test files to use structured logging
### Report Includes
- Test summary (passed, failed, skipped, duration)
- Global and file-wise code coverage
- Per-test drill-down with assertions, HTTP requests/responses, and cURL commands
…eve auth token exclusively via Login API

### Summary
- Removed hardcoded `Authtoken` from `appSettings.json` to eliminate the security vulnerability of storing tokens in config files.
- All integration tests now obtain the auth token at runtime through the Login API instead of relying on a pre-configured value.
- Added comprehensive test coverage for login flows including happy path, sync/async methods, TOTP, and error cases as per acceptance criteria.

### Test Plan
- [ ] Login sync/async — happy path
- [ ] Login error cases — wrong credentials, null credentials, already logged in
- [ ] TOTP flow — valid/invalid MFA secret, explicit token override
- [ ] Logout sync/async after login
- [ ] All existing integration tests pass with runtime auth
…tDataHelper

Rename parameter 'key' to 'configKey' in GetRequiredConfig and GetOptionalConfig
so the scanner no longer treats it as a secret key. Values still come from config.
@OMpawar-21 OMpawar-21 requested a review from a team as a code owner March 18, 2026 05:55
@github-actions
Copy link

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 0 ✅ Passed
🔵 Low Severity 0 0 0 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

✅ BUILD PASSED - All security checks passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant