TP/NGSI-LD/DistributedOperations/Provision/EntityAttributes/AppendEntityAttributes/D003_01_inc.robot
+3
−2
Loading
Upstream added isParked, reliability, availableSpotsNumber and
totalSpotsNumber to the test suite's own @context. Twelve Test Purposes
had been relying on those names NOT being defined: a name that lands in
the default context compacts back to its short form under the core
context alone, and a name the suite context claims does not.
Nothing about the brokers changed - the same names now mean something
else, so the tests were asking the wrong questions.
Three shapes of fix, all of them the pattern the suite already uses
elsewhere:
- expectations compared against a core-context retrieval now carry the
expanded name, because that is what comes back
- the two _inc appends pass context= on both the append and the
retrieval, exactly as their _exc siblings already do; without it the
fragment's isParked expanded into the default context and appended a
SECOND attribute instead of overwriting the first
- the Context Source mocks serve the .jsonld payload rather than the
bare .json, so the attribute the Context Source contributes is the
same attribute the test then looks for - it was arriving compacted
as "ngsi-ld:default-context/isParked"
The suite context branch is now an env var (NGSILD_TEST_SUITE_BRANCH),
still defaulting to develop. It cannot default to this branch: 343
payload and expectation files name the develop URL literally, so moving
only the variable makes the suite disagree with itself.
1046/1046 against coraine.