Configure comprehensive code coverage with c8 for the Agents-for-js repository

[Copilot]

• Configure comprehensive code coverage with c8 for the Agents-for-js repository
• Add c8 as dev dependency for modern Node.js code coverage
• Create .c8rc.json configuration file with proper TypeScript and monorepo support
• Add npm scripts for coverage: test:coverage, test:coverage:ci, test:junit
• Update .gitignore to exclude coverage artifacts
• Update README.md with testing and coverage documentation
• Fix CI failures by updating test command and improving error handling

Issues Fixed

CI Test Report Generation

Fixed the CI workflow to use npm run test:junit instead of npm test to properly generate the test-report.xml file required by the test reporter step.

setVersion.js Error Handling

Improved error handling in setVersion.js to gracefully handle shallow clone issues in development environments while ensuring it fails appropriately in CI.

Current Status

The repository now has comprehensive code coverage tooling configured with:

• HTML reports for interactive development debugging
• LCOV format for CI/CD integration and IDE support
• JSON summary for automated processing and badges
• JUnit XML for CI test reporting

All CI steps now pass successfully:

• ✅ Linting
• ✅ TypeScript build
• ✅ Test execution with JUnit reporting
• ✅ Sample builds
• ✅ Version setting
• ✅ Test report publishing

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[rido-min]

@copilot fix the CI failures

[Copilot]

@copilot fix the CI failures

CI failures have been fixed with commit 1742688. The issues were:

1. Test report generation: Updated CI workflow to use npm run test:junit instead of npm test to generate the required test-report.xml file
2. setVersion.js error handling: Improved error handling to gracefully handle shallow clone issues in development while ensuring proper CI behavior

All CI steps now pass successfully:

• ✅ Linting
• ✅ TypeScript build
• ✅ Test execution with JUnit reporting
• ✅ Sample builds
• ✅ Version setting
• ✅ Test report publishing

The code coverage tooling is fully functional and ready for use.

General fix:
Parse the returned url string using the URL API. Then, check the .host (or .hostname) property of the parsed object for an exact match, instead of using a substring check.

In detail:

• For all assertions that currently check for the presence of an expected host as a substring, replace the check with one that parses the URL (e.g., new URL(url).host) and asserts that it equals the expected host.
• This change should be made within the current test file only, and only where host validation is performed. Other substring checks (e.g., checking for the presence of 'conversations' in the path, or specific query parameters in the query string) should not be altered unless they check hosts.
• Add an import for the Node.js URL class at the top if necessary (globally available, but for clarity may add import { URL } from 'url').

---

To fix this, update the tests that check if the output URL contains a specific host substring so that they parse the URL and compare the parsed hostname directly to the expected value. Specifically:

• In each assertion like:

  assert(url.includes('environment.api.preprod.powerplatform.com'))

  replace with:

  assert.equal(new URL(url).host, 'environment.api.preprod.powerplatform.com')

• Add the import for the URL global (not strictly needed in modern Node.js, but for clarity and consistency).
• Similarly, update the custom cloud test to compare .host rather than do a substring search. If customCloud is just the host, use it accordingly.
• Consider whether the tests for other hosts (production, Mooncake, custom) should be made similarly robust. (Likely yes for correctness.)

All changes are in packages/agents-copilotstudio-client/test/powerPlatformEnvironment.test.ts, affecting only the relevant assertions.

---

The problem is on line 61, where the test asserts that the output URL contains customCloud via substring matching: assert(url.includes(customCloud)). To fix this, we should parse the url using a standard URL parsing library (URL from the JS standard library) and assert that the host or hostname portion of the parsed URL exactly matches customCloud. We should edit this line to parse the generated URL and adjust the assertion accordingly. No changes to other lines or files are needed. Only a standard library import (URL) is required, which does not require new dependencies.

To fix this issue and make the test correct and robust, replace the substring check url.includes('direct.connection.com') on line 90 with a check that parses the URL and examines its host property. Specifically, use the standard URL class (available in Node.js and browsers) to parse the generated URL and assert that urlObj.host or urlObj.hostname is exactly 'direct.connection.com'. To do this, create an instance of URL with the output of getCopilotStudioConnectionUrl(settings), e.g. const urlObj = new URL(url);, and then assert that urlObj.hostname === 'direct.connection.com'. This requires no external dependencies, as the URL class is built-in. Only the test for the direct connect URL (line 90) needs this fix.

---

General Fix: Instead of checking for substring inclusion, the test should parse the URL and assert that its host property matches the expected host, e.g., environment.api.powerplatform.com.

Detailed Steps:

• In the affected test(s), replace url.includes('environment.api.powerplatform.com') with a check that parses the URL and checks the host.
• Use the standard URL class (available globally in Node.js) to parse the URL.
• The fixed query should look like: new URL(url).host === 'environment.api.powerplatform.com' instead of url.includes(...).
• Ensure only the check for the host is replaced, and provide context for why this makes the test stricter and less prone to error.

Required Changes:

• Change on line 151 within the file packages/agents-copilotstudio-client/test/powerPlatformEnvironment.test.ts as per the above.
• No new imports required, since the global URL class is available in modern Node environments and commonly used.

The best way to fix this issue is to parse the output URL and inspect its host property directly. In the test that checks url.includes('custom.domain.com'), change the validation to parse the URL using the standard Node.js URL constructor (available in both Node and browser environments), then assert that the host (or hostname) property exactly matches the expected custom domain. This requires importing/utilizing the URL class. The change should be made only to line 492 within the test block for "should handle URLs without protocol" in the file packages/agents-copilotstudio-client/test/powerPlatformEnvironment.test.ts.