You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found this when updating the python manager template. The compliance suite tests for a malformed reference in Test_getWithRelationship_All uses the existence of a malformed entity reference fixture as the deciding factor as to whether it should be skipped. I propose it should be including whether the a_relationship_trait_set fixture exists either instead or in addition to this.
The a_malformed_reference fixture is common to other non-optional flows, and is likely to be defined as a globally shared fixture, (which is what BAL does, really the only other example available, and bound to be copy-pasted,) This may give the wrong impression the the relationship functions must be implemented to a new implementer, and could bounce the tentative explorer.
Acceptance Criteria
Tests skipped based on relationship specific fixtures where possible.
Notes
Changes to BAL out of scope
The text was updated successfully, but these errors were encountered:
OpenAssetIO#1022
Alter the skip fixture in certain getWithRelation tests away from
common shared ones to the `a_relationship_trait_set`, which is
less likely to be defined in a shared context.
This is helpful because relationships are an optional feature, so it
is likely managers will want to skip all the relationship tests as a
group, and this makes that more or less the default behaviour without
thinking about it.
Signed-off-by: Elliot Morris <elliot.morris@foundry.com>
OpenAssetIO#1022
Alter the skip fixture in certain getWithRelation tests away from
common shared ones to the `a_relationship_trait_set`, which is
less likely to be defined in a shared context.
This is helpful because relationships are an optional feature, so it
is likely managers will want to skip all the relationship tests as a
group, and this makes that more or less the default behaviour without
thinking about it.
Signed-off-by: Elliot Morris <elliot.morris@foundry.com>
OpenAssetIO#1022
Alter the skip fixture in certain getWithRelation tests away from
common shared ones to the `a_relationship_trait_set`, which is
less likely to be defined in a shared context.
This is helpful because relationships are an optional feature, so it
is likely managers will want to skip all the relationship tests as a
group, and this makes that more or less the default behaviour without
thinking about it.
Signed-off-by: Elliot Morris <elliot.morris@foundry.com>
What
Found this when updating the python manager template. The compliance suite tests for a malformed reference in
Test_getWithRelationship_All
uses the existence of a malformed entity reference fixture as the deciding factor as to whether it should be skipped. I propose it should be including whether thea_relationship_trait_set
fixture exists either instead or in addition to this.OpenAssetIO/src/openassetio-python/package/openassetio/test/manager/apiComplianceSuite.py
Line 686 in 3323a23
Why
The
a_malformed_reference
fixture is common to other non-optional flows, and is likely to be defined as a globally shared fixture, (which is what BAL does, really the only other example available, and bound to be copy-pasted,) This may give the wrong impression the the relationship functions must be implemented to a new implementer, and could bounce the tentative explorer.Acceptance Criteria
Notes
The text was updated successfully, but these errors were encountered: