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

feat(session): implement CallWebConnectivityTestHelper #1581

Merged
merged 51 commits into from
May 2, 2024
Merged

Conversation

bassosimone
Copy link
Contributor

@bassosimone bassosimone commented May 2, 2024

Part of ooni/probe#2725

This diff includes a first attempt at consolidating the patterns with
which we invoke OONI and third-party API calls.

I have refactored the code of httpx and httpapi into a new package
called httpclientx, added some tests, started converting some parts
of the tree, and explained myself in a design document.

Part of ooni/probe#2700
Spotted thanks to a very paranoid check inside ./internal/oonirun.

Was not a problem before for `httpx` because of its usage pattern and may
or may not be a problem for the `httpapi` package (did not check since
this work is focused on replacing both `httpx` and `httpapi`).
Previously, we were gracefully handling this case, but honestly it is
not the best approach to pretend there's an empty structure if the server
breaks the API and returns `"null"` rather than an object.

That said, it was still awesome to have this test in place because it
helped us to figure out this extra condition of which httpclientx should
be aware and that this problem needs to be dealt with systematically
inside the httpclientx package.
Conflicts:
	internal/enginelocate/cloudflare.go
	internal/enginelocate/ubuntu.go
Conflicts:
	internal/oonirun/v2_test.go
As before, here I am going to ensure there's redundancy.
Conflicts:
	internal/httpclientx/DESIGN.md
	internal/httpclientx/getraw.go
	internal/httpclientx/overlapped.go
Conflicts:
	internal/probeservices/login_test.go
Conflicts:
	internal/testingx/oonicollector.go
Conflicts:
	internal/probeservices/collector_test.go
Conflicts:
	internal/probeservices/bouncer.go
	internal/probeservices/collector.go
	internal/probeservices/login.go
	internal/probeservices/measurementmeta.go
	internal/probeservices/psiphon.go
	internal/probeservices/register.go
	internal/probeservices/tor.go
While there, add additional tests ensuring that we're actually
writing into the key-value store after check-in.

Also, ensure that failure to write into the key-value store
does not break check-in for good.
@bassosimone bassosimone changed the title Issue/2725 feat(session): implement CallWebConnectivityTestHelper May 2, 2024
@bassosimone bassosimone marked this pull request as ready for review May 2, 2024 12:40
@bassosimone bassosimone requested a review from hellais as a code owner May 2, 2024 12:40
@bassosimone bassosimone merged commit 9a3abfc into master May 2, 2024
19 checks passed
@bassosimone bassosimone deleted the issue/2725 branch May 2, 2024 12:40
bassosimone added a commit that referenced this pull request May 2, 2024
The #1581 pull request missed that
adding a `CallWebConnectivityTestHelper` method to `*engine.Session`
means we need to mock such a method in `webconnectivityqa`.

I could have mocked the method, but I was not super happy about doing
this, because I would rather have wanted to add more QA tests inside of
`webconnectivityqa` making sure we're indeed falling back when using
test helpers. (We have unit tests testing that, but it would be nice to
have integration tests, so we could observe the overall code behavior.)

My initial approach for allowing this was to create a
`CallWebConnectivityTestHelper` function inside the engine, taking a
`model.ExperimentSession` as its fourth argument and then modifying the
`CallWebConnectivityTestHelper` method to just invoke the function
passing to it the session. However, this approach created import cycles
in tests.

To avoid import cycles, I moved the `CallWebConnectivityTestHelper`
function to `webconnectivityalgo` and modified the mocks inside
`webconnectivityqa` to call such a function. This is where I paused and
realized that the cleanest solution is actually to just always call the
`CallWebConnectivityTestHelper` function in `webconnectivityalgo` and
undo part of the changes in #1581
to avoid having a `CallWebConnectivityTestHelper` method inside of
`model.ExperimentSession`. And so I also implemented this change.

All of this leads us to the current diff, which is part of
ooni/probe#2725.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant