added non-collaborative file based#237
Conversation
|
Thx for opening a PR @emekaokoli19 - CI is showing red, could you take a look? |
Yea |
|
The failures are due to some awkwardness of the otel-related test harnesses. @emekaokoli19 chances are you were probably testing against some intermediate version, with otel feature added with partial test coverage or something. I have reworked the test harnesses to let otel and non-collaborative tests coexist, my version is here -- abbbe#4. Unfortunately, I saw no easy way to fix it and keep the test suite clean and legible, so changes are quite extensive... Unless you have better ideas, feel free to merge into your branch & tests or whatever. |
|
@emekaokoli19 are you ok with the modifications to your PR I have proposed? |
Add test fixture for non-collaborative (file-based) code path
This PR introduces a new test fixture to exercise the non-collaborative (file-based) execution path for Jupyter cell mutation tools, addressing the gap described in issue #224.
Key changes:
jupyter_server_no_collabfixture to start Jupyter without collaboration enabled.