Add test for db endpoint when use mixed test

[joanhey]

Actually it isn't testing this endpoint that is necessary for the mixed test.

@BennyFranciscus could you try to add the test ?

[BennyFranciscus]

Hey @joanhey — the db endpoint validation for mixed test is already handled by the benchmark runner (gcannon validates all endpoints in the mixed template). The issue from PR #164 was just about mounting the benchmark.db file in run.sh for local runs.

I just opened PR #167 with your fix applied (has_test "mixed" instead of has_test "db"). That should cover it — frameworks with the mixed profile now get the database file mounted automatically.

Or did you mean something else? Like adding a standalone db test profile to validate.sh?

[joanhey]

Yes, add a standalone db test profile in validate.sh when has the test "mixed".

[BennyFranciscus]

Done! Just pushed a commit to PR #167 that adds /db endpoint validation in validate.sh when a framework has the mixed test.

It mirrors the async-db checks — validates response structure (items with rating/tags/active), Content-Type, and includes an anti-cheat empty-range check. Also mounts benchmark.db into the container (auto-generates if missing).