Skip to content

Add property coverage to @uncompliant tests#294

Draft
smanes0213 wants to merge 7 commits into
masterfrom
development/uncompliant-property-coverage
Draft

Add property coverage to @uncompliant tests#294
smanes0213 wants to merge 7 commits into
masterfrom
development/uncompliant-property-coverage

Conversation

@smanes0213

@smanes0213 smanes0213 commented Jul 3, 2026

Copy link
Copy Markdown
Contributor
  • Both @uncompliant:extended and @uncompliant:collapsed are deprecated (Thunder docs/plugin/interfaces/tags.md) and tested here solely to pin existing generator behaviour against regressions.
  • Both test interfaces previously only contained a single echo method — for @uncompliant:extended this meant the test exercised zero distinguishing behaviour: the mode's only effect is on property parameter encoding, not methods, making the test identical to @compliant.
  • Added a Value read/write @Property to both interfaces so the tests actually expose what each mode does differently:
    1. @uncompliant:extended: property SET sends a bare scalar (42 not {"value":42}); methods remain wrapped — only properties are affected
    2. @uncompliant:collapsed: property SET and single-param methods both send bare scalars; collapsed tests additionally assert that sending a wrapped object to a collapsed method is rejected

NOTE: The Branch addition in ProxyStubFunctionalTest.yml is temporary to run the tests on current branch.

Both @uncompliant:extended and @uncompliant:collapsed are deprecated (Thunder docs/plugin/interfaces/tags.md) and tested here solely to pin existing generator behaviour against regressions
Both test interfaces previously only contained a single echo method — for @uncompliant:extended this meant the test exercised zero distinguishing behaviour: the mode's only effect is on property parameter encoding, not methods, making the test identical to @compliant
Added a Value read/write @Property to both interfaces so the tests actually expose what each mode does differently:
@uncompliant:extended: property SET sends a bare scalar (42 not {"value":42}); methods remain wrapped — only properties are affected
@uncompliant:collapsed: property SET and single-param methods both send bare scalars; collapsed tests additionally assert that sending a wrapped object to a collapsed method is rejected

Signed-off-by: smanes0213 <sankalpmaneshwar46@outlook.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant