We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Capture client, server, and kernel coverage with robot tests.
Being able to gather fine-grained coverage of JS, python, and maybe other languages from a single test increases the value of executed robot tests.
Client coverage:
Server coverage:
Kernel coverage could be gathered by copyinh a custom kernel.json, and adding some more data:
kernel.json
{ "argv": [ "$PREFIX/bin/python", "-m", "coverage", "run", "-m", // ... add this line, with more args "ipykernel_launcher", "-f", "{connection_file}" ], "display_name": "Python 3 (ipykernel)", // add the context name? "language": "python", "metadata": { "debugger": true } }
Finally, some reporting keywords could be added, optionally embedding the reports inside the robot HTML if they can be generated as a single file.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Elevator Pitch
Capture client, server, and kernel coverage with robot tests.
Motivation
Being able to gather fine-grained coverage of JS, python, and maybe other languages from a single test increases the value of executed robot tests.
Design Ideas
Client coverage:
Server coverage:
Kernel coverage could be gathered by copyinh a custom
kernel.json
, and adding some more data:Finally, some reporting keywords could be added, optionally embedding the reports inside the robot HTML if they can be generated as a single file.
The text was updated successfully, but these errors were encountered: