Open loosebazooka opened 3 days ago
this case is handled in the Makefile I believe but I suppose we could handle this in pytest as well: just refuse to run without faketime being available
I think my "make dev" succeeded without faketime. Happy if it fails there
oh right, it probably only fail when running the included clients (make test-go-tuf
) : this is not helpful in your case.
So options would be
make dev
should fail without faketimeThis might matter a lot less when we're conformant. But getting started is confusing if it errors like this. Local dev feel like critical path for getting started
tests in test_expiration require the existence of "faketime" on the system. Perhaps failures on missing infrastructure pieces can be surfaced differently?