Skip to content
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

cli/engine: expose commands to facilitate testing the API #2152

Closed
bassosimone opened this issue Jun 17, 2022 · 1 comment
Closed

cli/engine: expose commands to facilitate testing the API #2152

bassosimone opened this issue Jun 17, 2022 · 1 comment
Assignees
Labels
priority/medium Normal priority issue

Comments

@bassosimone
Copy link
Contributor

bassosimone commented Jun 17, 2022

We discussed with @FedericoCeratto that it would be useful to have commands for testing the APIs in the same way in which the probe actually uses them. This basically means having a simple way of calling the right session method. It could either be a subcommand of ooniprobe or another private binary build from ./internal/cmd. Maybe the former is better.

BTW, we should ensure that we test the same codepath of a real probe.

@bassosimone bassosimone added the triage Should be triaged through the triage board label Jun 17, 2022
@bassosimone bassosimone self-assigned this Jun 17, 2022
@bassosimone bassosimone added priority/medium Normal priority issue and removed triage Should be triaged through the triage board labels Jul 25, 2022
@hellais hellais added this to Roadmap Jan 7, 2025
@hellais
Copy link
Member

hellais commented Jan 27, 2025

This will probably happen as part of engine split work: #2826

@hellais hellais closed this as completed Jan 27, 2025
@github-project-automation github-project-automation bot moved this to Done in Roadmap Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/medium Normal priority issue
Projects
Archived in project
Development

No branches or pull requests

2 participants