O11y artifact changes

[AakashHotchandani]

No description provided.

[xxshubhamxx]

The pull request introduces several updates to the Nightwatch BrowserStack plugin, primarily focused on expanding support for "Test Reporting and Analytics" in addition to the existing "Test Observability" terminology and features. Here are the main points from the review:

Summary of Changes

• Terminology Update: All logs, error messages, and user-facing strings have been updated from "Test Observability" to "Test Reporting and Analytics" to reflect a broader scope. This includes error logging, informational messages, and documentation within the code.
• Configuration Flexibility: The plugin now recognizes both testObservability and testReporting flags in the configuration. It also supports new options like testReportingOptions and maintains backward compatibility with testObservabilityOptions.
• Environment Variables: The plugin sets and checks for both BROWSERSTACK_TEST_OBSERVABILITY and BROWSERSTACK_TEST_REPORTING environment variables. It also ensures they are initialized only if not already set, and disables both when respective CLI flags are used.
• Helper Improvements: The helpers now resolve project names, build names, and tags from both test observability and test reporting options, prioritizing new options when both are present.
• Error Handling: All error and debug messages have been updated to include the new terminology, ensuring clarity for users migrating to the new reporting system.
• URL Update: The build report link in logs now points to https://automation.browserstack.com/builds/ instead of the older observability URL.

Files Modified

• nightwatch/globals.js
• src/testObservability.js
• src/utils/helper.js
• src/utils/requestQueueHandler.js

Review Notes

• The migration is comprehensive and should allow users to configure either test observability or reporting options without breaking changes.
• No breaking changes to existing configuration structures, but users are encouraged to migrate to the new naming for future compatibility.
• All error and info logs are now consistent with the new product naming, which improves clarity.
• The changes are well-scoped and do not appear to introduce any regressions based on the diffs provided.

Suggestions

• Documentation should be updated to reflect the new configuration options and environment variables.
• Consider adding migration notes for users upgrading from previous versions.

Overall, the PR is well-structured, clear in its intent, and maintains backward compatibility while supporting the new feature set.