| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Add a base test class that runs the portal and an arbitrary set of endpoints
in a DBus sandbox, so that different combinations of permissions can be tested.
|
| |
|
|
|
|
|
|
| |
This isn't needed since tracker-store is no longer a separate daemon.
Some tests still connect to the session bus but they should no longer
autostart any services. Callers should use `dbus-run-session` to
create a separate session bus if worried about having test processes
talking on the real session bus.
|
| |
|
|
|
|
|
|
|
|
| |
This timeout interferes with debugging. If you attach GDB to a daemon
as it starts up and step through the code, the timeout can cause
dbus-daemon to kill the process that you're debugging.
We can rely on `meson test` to kill tests that actually don't finish,
and the `meson test` timeout can be conveniently increased with the
`--timeout-multiplier` commandline option.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of manually running and managing Tracker daemon processes
manually in the test, we now rely on our private D-Bus daemon to
do so.
This makes the test environment more like a real Tracker deployment.
Log output from the D-Bus daemon is now captured and output through
the Python logging system. This allows for finer-grained filtering
of output from the tests themselves and from the Tracker daemons.
Some test code is changed to support the new model.
|
|
|
Run dbus-run-session with the --config-file parameter in order to allow to run
tests without installing tracker before.
Closes: https://gitlab.gnome.org/GNOME/tracker/issues/24
|
