CI: Write the AAS schemas where the tests read them

[leogrox]

Fixes #637.

pr.yml downloads the schema files into ./test/adapter/schema, while the tests read ../schemas/, that is test/adapter/schemas, the path .gitignore already covers (L27). The files never reach the tests, so JsonSerializationSchemaTest and XMLSerializationSchemaTest skip their whole class on every run: that is the skipped=2 in a green build.

Renaming the directory in the workflow is enough to make them run.

Testing

Reproduced the CI layout locally, with the schemas in test/adapter/schema, and both classes skip:

setUpClass (…JsonSerializationSchemaTest) ... skipped 'JSON Schema does not exist at …/test/adapter/json/../schemas/aasJSONSchema.json'
setUpClass (…XMLSerializationSchemaTest) ... skipped 'XSD schema does not exist at …/test/adapter/xml/../schemas/aasXMLSchema.xsd'
OK (skipped=2)

With the files in test/adapter/schemas the 13 tests in those classes run. Two of them fail on develop, which is #636, fixed separately; with both changes the suite is green (282 tests).

Two things I left out on purpose, happy to add either if you want them here rather than in a follow-up: making the absence of the schema fatal in CI (a missing file currently turns into a green build), and pointing the workflow and the tests at one shared constant so the two paths can't drift again.

[hpoeche]

Thank you for spotting and fixing this mistake. As you pointed out in #637, the root cause here is that the test are skipped silently in the CI.
We are currently implementing unittests for the server package, where we focused a similar situation with the integration tests: It is okay to skip them in local dev environments, but the CI must not skip them but fail. We solved this by introducing an environment variable that prevents skipping the tests when set.
You can take a look at our implementation here:
https://github.com/rwth-iat/basyx-python-sdk/blob/aeaa5063ff214012529c4fcc25d0f83930189a6b/server/test/_helper/test_helpers.py#L27

If @s-heppner agrees, it would be very helpful to implement this approach here too.

[leogrox]

Thanks, that addresses the actual root cause better than the path fix alone. I've added it here as a separate commit, so it's easy to drop if @s-heppner would rather keep this PR to the path:

• test/_helper/test_helpers.py gets REQUIRE_SCHEMAS, read from REQUIRE_SCHEMA_TESTS, same shape as your REQUIRE_SERVER_INTEGRATION_TESTS.
• JsonSerializationSchemaTest and XMLSerializationSchemaTest raise in setUpClass when it's set and the schema file is missing. Otherwise they skip as before.
• pr.yml sets it on the unittest step.

Checked from sdk/: without the schema files and with the variable set, both classes error out (FAILED (errors=2)); unset or 0, they skip as before. With the files in place this branch still shows the two #636 failures, so #638 needs to go in first; with both, the suite is green (282 tests).

The CouchDB tests skip the same way when the service isn't reachable. I left them alone to keep this about the schemas, but the same switch would work there if you want it.

[zrgt]

@hpoeche please review

[hpoeche]

LGTM, thank you very much!
@zrgt Please double check the CI changes. Afterwards, I would recommend to approve, so the CI checks can run.

[s-heppner]

I bumped the milestone for this to version 2.3.0, as we release 2.2.0 today and this is not ready yet.

[zrgt]

Closed and reopened to re-trigger CI against the current develop. Re-running the old workflow kept testing the original merge commit, which doesn't include #638, so the schema tests kept failing.