e0b0dfedc1
* feat(session): expose CheckIn method It seems to me the right thing to do is to query the CheckIn API from the Session rather than querying it from InputLoader. Then, InputLoader could just take a reference to a Session-like interface that allows this functionality. So, this diff exposes the Session.CheckIn method. Doing that, in turn, required some refactoring to allow for more and better unit tests. While doing that, I also noticed that Session required a mutex to be a well-behaving type, so I did that. While doing that, I also tried to cover all the lines in session.go and, as part of that, I have removed unused code. Reference issue: https://github.com/ooni/probe/issues/1299. * fix: reinstate comment I shan't have removed * fix: repair broken test * fix: a bit more coverage, annotations, etc. * Update internal/engine/session.go * Update internal/engine/session_integration_test.go * Update internal/engine/session_internal_test.go |
||
|---|---|---|
| .. | ||
| internal/tasks | ||
| .gitignore | ||
| experiment_test.go | ||
| experiment.go | ||
| README.md | ||
| session_integration_test.go | ||
| session_test.go | ||
| session.go | ||
| sessioncontext_test.go | ||
| sessioncontext.go | ||
| sessionlogger_test.go | ||
| sessionlogger.go | ||
| task_integration_test.go | ||
| task_internal_test.go | ||
| task.go | ||
| uuid_test.go | ||
| uuid.go | ||
| webconnectivity_integration_test.go | ||
| webconnectivity_test.go | ||
| webconnectivity.go | ||
Package github.com/ooni/probe-cli/pkg/oonimkall
Package oonimkall implements APIs used by OONI mobile apps. We expose these APIs to mobile apps using gomobile.
We expose two APIs: the task API, which is derived from the
API originally exposed by Measurement Kit, and the session API,
which is a Go API that mobile apps can use via gomobile.
This package is named oonimkall because it contains a partial reimplementation of the mkall API implemented by Measurement Kit in, e.g., mkall-ios.
The basic tenet of the task API is that you define an experiment task you wanna run using a JSON, then you start a task for it, and you receive events as serialized JSONs. In addition to this functionality, we also include extra APIs used by OONI mobile.
The basic tenet of the session API is that you create an instance
of Session and use it to perform the operations you need.