Incorporate aas-test-engines for server testing #429
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Frosty2500
force-pushed
the
incorporate_aas_test_engines
branch
4 times, most recently
from
46f52e4 to
104580c
Compare
Frosty2500
force-pushed
the
incorporate_aas_test_engines
branch
2 times, most recently
from
9eee9c9 to
ac28736
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, we lacked a way to test our server for compliance to the specification.
This PR incorporates the aas-test-engines project into our ci pipeline. Using only operations we have implemented (where we do not return a 501) we can check our server for compliance.
Fixes #302