-
Notifications
You must be signed in to change notification settings - Fork 18
feat : load config from local context instead of global variables #96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat : load config from local context instead of global variables #96
Conversation
- Replaced direct usage of credentials from config with a new utility function `getBrowserStackAuth` to retrieve authentication details. - Updated multiple functions across various modules to accept `server` parameter for improved flexibility and maintainability. - Ensured all API calls to BrowserStack now utilize the new authentication method, enhancing security and code clarity. - Adjusted related function signatures and calls to accommodate the new parameter structure.
…rver parameter - Updated createTestRun, listTestCases, listTestRuns, updateTestRun, and uploadFile functions to include a server parameter. - Modified related test cases to pass mock server instances for better test isolation and accuracy. - Enhanced error handling and logging in test management tools. - Improved test coverage for various scenarios in test management utilities.
…ameters and handle local URL errors
…ated binary setup
…of server parameter - Updated listTestCases, listTestRuns, pollLCAStatus, createTestCasesFromFile, updateTestRun, uploadFile, and other related functions to accept BrowserStackConfig. - Modified the corresponding test cases to reflect the changes in function signatures and ensure proper configuration handling. - Enhanced error handling and logging for better debugging and traceability.
…e proper URL opening
…or BrowserStack integration
…ts implementation
…ove process management
…ith improved error handling and environment variable checks
sync with main
….json and package-lock.json
….ts has consistent import style fix: modify device cache to store live response data correctly
Tested with the pipeline — all tools are working. |
@@ -38,6 +38,7 @@ | |||
"@types/form-data": "^2.5.2", | |||
"axios": "^1.8.4", | |||
"browserstack-local": "^1.5.6", | |||
"chitragupta": "github:browserstack/chitragupta-node", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this needed in OSS version ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we need logs from the remote server for tool execution, then yes, having them is needed.
Since the Chitragupta Node SDK is open source, I believe it's acceptable to include it in our OSS.
No description provided.