This removes some boilerplate in test code, better exploiting pytest fixtures.
Some repetition m...

Not necessary anymore.

As that name can only be ensured for managed services, not for external ones.

This leaves `Serv...

Both for fixture and standalone script.

If needed, the corresponding test fixture should be used.

To help avoid boilerplate in path computation.

They have session scope so that the tests servic...

Not needed as service programs are part of the `caterva2` package now.

To avoid duplication. Also, remove unused example dir name there.

For consistency and to avoid weird errors.

Here it is more work for adopting package conventions inside Caterva2. Now, services, clients an...

Since all of them import the `caterva2` package now.

This updates changes from pull request #7 (which replaced the Supervisor-based
tests services wi...

The configuration file was quite dependent on the test setup and not very
useful to others, anyway.

It is now needed since service scripts import `caterva2`.

Tests with subproc

The global values from `sys` and `os` modules are being used.

For better visibility.

This should detect if a service is already running when a test session is
started which is expec...

Availability of the required services is checked. Still not configurable.

Package

Latest blosc2

SIGHUP should kill the process without leaving a core dump.

For easier programmatic handling.

Instead, do a partial fill of the downloaded data, and deliver the
slice of it. The result is e...

Only leave state directory and main source directory. The rest are computed
locally.

When acting as a plain script, use the already existing directory for safety.

For consistency and to avoid weird errors.

For instance, by doing `from .services import services`.

The fixture uses `_caterva2_tests` as ...