improve examples and notes in README

Author: mattloveparasoft

README.md

@@ -50,24 +50,43 @@ Add the following dependency to your Maven project:
 </dependencies>
 ```
 
-When coverage agents are running in multi-user mode or tests execute in parallel, browser requests must include the current test's `Baggage` header so that coverage can be correctly associated with the executing test.
+When coverage agents are running in multi-user mode or tests execute in parallel, browser requests must include an additional HTTP `Baggage` header so that coverage can be correctly associated with the executing test. See [Browser Integrations](#browser-integrations) for more detail.
 
-The following example retrieves the current `Baggage` header, creates a proxy that injects the header into browser requests, and configures the Chrome driver to use that proxy.
+The following example retrieves the current `Baggage` header and creates a proxy that injects the header into HTTP requests.
 
 ```java
 String baggageHeader = CoverageIntegration.getBaggageHeader();
 if (baggageHeader == null || baggageHeader.isBlank()) {
     return;
 }
 
-ChromeOptions options = new ChromeOptions();
-ParasoftHeaderInjectingProxy coverageProxy =
-        new ParasoftHeaderInjectingProxy(PROXY_BIND_HOST, 0, baggageHeader);
-SeleniumCoverageIntegration.configureChromeOptions(options, coverageProxy);
+try (ParasoftHeaderInjectingProxy coverageProxy =
+        new ParasoftHeaderInjectingProxy(PROXY_BIND_HOST, 0, baggageHeader)) {
+    String proxyHost = coverageProxy.getHost();
+    int proxyPort = coverageProxy.getPort();
+    // run test HTTP traffic through the coverage proxy
+} // implicitly close the proxy at the end of the try-with-resources block
 ```
 
 For rare standalone use cases, such as tests launched from a `main` method, use `CoverageApiClient` from the API module to start and stop sessions and tests directly.
 
+```java
+CoverageApiClient client = CoverageApiClient.createFromSettings();
+String sessionId = client.startSession();
+CoverageTestContext context = client.startTest("ExampleTest", "runsFromMain");
+
+try {
+    // Execute the code under test here. Send context.getCurrentTestOperatorIdHeader()
+    // as HTTP headers when calling an application under test.
+    client.stopTest("ExampleTest", "runsFromMain", context, CoverageTestResult.PASS, null);
+} catch (RuntimeException e) {
+    client.stopTest("ExampleTest", "runsFromMain", context, CoverageTestResult.FAIL, e.getMessage());
+    throw e;
+} finally {
+    client.stopSession();
+}
+```
+
 ## Coverage Configuration
 
 Create a coverage-integration.properties file to configure communication with CTP during the testing workflow. This file also provides the information needed to publish test results and coverage after all tests have completed.
@@ -85,20 +104,22 @@ parasoft.coverage.integration.dtp.sessionTag=unit-testing-session
 # Authentication username for CTP
 parasoft.coverage.integration.ctp.auth.username=admin
 
-# Password for CTP with support for variable resolution
-parasoft.coverage.integration.ctp.auth.password=${env_var:PASSWORD}
+# Password for CTP with support for variable resolution such as ${env_var:PASSWORD}
+# It is recommended that passwords be protected by a credentials manager.
+parasoft.coverage.integration.ctp.auth.password=password
 
 # OAuth bearer token in the case where CTP is setup with OIDC authentication
 parasoft.coverage.integration.ctp.auth.token=<bearer token>
 
 # Enables support for parallel test execution. When enabled, the
 # coverage-integration library isolates coverage data for each test.
+# Note: Requires Parasoft CTP version 2026.2 or later.
 parasoft.coverage.integration.parallel.test.enabled=true
 
 # Identifies the user associated with the coverage session. When running
-# tests in parallel, this value is used to isolate coverage data between
-# concurrent test executions.
-parasoft.coverage.intergration.ctp.userId=tester
+# test sessions in parallel, this value is used to isolate coverage data between
+# concurrent test execution sessions.
+parasoft.coverage.integration.ctp.userId=tester
 ```
 Place this file on your project's classpath, for example in src/test/resources.
 
@@ -177,6 +198,13 @@ Enable JUnit extension auto-detection by setting the following system property w
 
 -Djunit.jupiter.extensions.autodetection.enabled=true
 
+Enable per-test coverage isolation for JUnit parallel test execution (-Djunit.jupiter.execution.parallel.enabled=true) by setting the following in the coverage-integration.properties file:
+
+```properties
+# Note: Requires Parasoft CTP version 2026.2 or later.
+parasoft.coverage.integration.parallel.test.enabled=true
+```
+
 ### TestNG
 
 Add the Maven dependency for the TestNG coverage integration:
@@ -220,6 +248,13 @@ Add both listeners to your `testng.xml` file as shown below:
 </suite>
 ```
 
+Enable per-test coverage isolation for TestNG parallel test execution (parallel="tests") by setting the following in the coverage-integration.properties file:
+
+```properties
+# Note: Requires Parasoft CTP version 2026.2 or later.
+parasoft.coverage.integration.parallel.test.enabled=true
+```
+
 ### Cucumber
 
 The `coverage-integration-cucumber` module automatically reports Cucumber 7.x scenario execution and coverage to CTP. It manages the coverage session for the duration of the Cucumber test run and reports each scenario as an individual test case.
@@ -404,6 +439,10 @@ To set explicit headers instead, use `configureCdpHeaders(driver, headers)`.
 
 Call `configureCdpBaggageHeader` separately for each Chrome or Edge browser session used by parallel tests. The proxy-based approach works with all supported browsers. CDP is an alternative available only for Chrome and Edge.
 
+> [!NOTE]
+> Cross-container Selenium Grid
+> Coverage isolation in multi-user or parallel testing with cross-container Selenium grid takes extra care to configure. The `SeleniumCoverageIntegration.configureCdpBaggageHeader(driver)` approach above is recommended for Google Chrome and Microsoft Edge.  However, the Parasoft coverage proxy used with Firefox only binds to the loopback address `127.0.0.1` by default. Use the `ParasoftHeaderInjectingProxy` constructor from the API to bind the proxy to a different host.
+
 ## Logging
 
 This project uses SLF4J and includes only the `slf4j-api` dependency. It does not provide or configure a logging backend, so debug logging is not shown by default. Applications that use this library control logging through their own SLF4J backend, such as Logback, Log4j 2, JUL, or `slf4j-simple`.