feat: add basic browser support #26
Conversation
|
cc @achingbrain if you want to take a look |
|
@laurentsenta this one is ready for a re-review! All checks pass now and comments have been applied. |
|
Added functionality to be able to move args from host Env to Browser Env, without having to expose the required keys explicitly: 06df3ce (required for: testground/testground#1502 (comment)) |
this way browser can wait for it, given it lives in a different process than the main driver
- logger needs to handle winston-like usage, making sure we log everything nicely as-is, instead of passing it directly we first need to manipualte it in a winston like manner to get a good effect - process was used in sync, but we cannot use this, env extraction is now cross-inner-package - this comples the env usage for node-browser-crossing
|
You can see this version of |
There was a problem hiding this comment.
Thanks for recreating the PR, it looks great now, two last questions before we can merge:
- Could we keep the TODO comments if they were not introduced in this PR? I don't have context on these.
- Could we go back to the initial logging approach? I'd rather keep it simple & use the code before implementing optimizations, json outputs, etc. That might be related to testground/testground#1355 (comment)
|
|
(updated description and title and merging, thanks for the PR!) |
|
Congratulations @GlenDC and @laurentsenta for this milestone! |
|
Agreed - way to go! |
browserfield to supportregisterTestcaseResultto communicate end of test with a node runner when running in-browsergetEnvParametersto let a client gather and move testground variables (used for browser support).Supersede #25, having applies all the previous feedback.