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
{{ message }}
Repository navigation
[Feature]: Verify REST Api client against compliant server #407
I have verified that I am running the latest version of the SysML2.NET
I have searched open and closed issues to ensure it has not already been reported
Description
Verify implementation of the REST Api client first against the http://sysml2.intercax.com:9000 server. Investigate the testing against Flexo (from OpenMBEE) by creating a default model that could be used later as first stable seeded data
Steps to Reproduce
System Configuration
SysML2.NET version:
Environment (Operating system, version and so on):
Retry the intermittent 409 Conflict that Flexo answers on the first commit to a new branch. When it hits step 10, the project-usage reads don't run and 2 more operations show as uncovered.
Accept the operations that Flexo can't serve as warnings in KnownServerDivergences, each with a narrow matcher, so the verdict lists only what the client misses:
GET /projects/{projectId}/commits/{compareCommitId}/diff (no 2xx, no 4xx; 501)
POST /projects/{projectId}/branches/{targetBranchId}/merge (no 2xx, no 4xx; 501)
GET /projects/{projectId}/query-results (no 2xx, no 4xx; 501)
PUT /projects/{projectId}/queries/{queryId} (no 4xx; creates a missing query)
DELETE /projects/{projectId}/branches/{branchId} (no 4xx; succeeds on an unknown branch)
Step 7: give the at and after triggers their arguments, typed from the model library, which needs the model library in the scenario.
Documentation and upstream
Tick off Appendix A of SySML2.NET.REST.Tests/INTEGRATION_TEST_PLAN.md against what the scenario now covers.
Report the Flexo divergences upstream (Open-MBEE/flexo-mms-sysmlv2), one item per entry in SySML2.NET.REST.Tests/Helpers/KnownServerDivergences.cs, including:
deletes don't cascade, and references to the deleted element are stripped;
previousCommit is sent as an object instead of an array;
the required project, branch and commit properties are missing;
roots are computed from the derived owner;
query results without @type;
200 instead of 201 on create;
error answers without an application/json Error body.
Activity
[Add] Integration test plan for the REST client against Flexo (#407)
[Add] Flexo integration scenario stage 1: test host, OpenAPI conforma…
[Add] Flexo integration scenario stage 2: KerML Core, Kernel and upda…
[Add] Flexo integration scenario stage 3: SysML structure, behaviour …
[Update] Flexo integration scenario: read lists in large pages, check…
[Add] Flexo integration scenario stage 4: queries, project usage and …
[Add] Flexo integration scenario stage 5: delete and teardown steps 1…
[Add] Flexo integration scenario triage: every property set and chang…
samatstariongroup commentedon Nov 9, 2026
Open items after the triage (run of 2026-11-09, rebased on
development)Verdict against Flexo
836d904d: 0 missing metaclasses, 0 unset properties, 0 unchanged properties, 0 missing literals. 8 uncovered operations remain; Flexo cannot serve any of them (see below).Client and SDK defects (the scenario stays red on these by design)
memberElement,memberName,sourceandtarget(red in steps 2–12)LiteralRational, steps 4–9)AssignOwnershipduplicates the member when a membership is re-assigned, and there is no public way to shrink or reorder an ownership list (worked around by a separate after-state builder inMoveModel)MergeAsyncsends resolution elements without the derived properties that theDataschema requires (step 8)nullfor optional references that the OpenAPI document doesn't make nullable (fixed, confirmed against Flexo)ModelBuilder)Scenario fixture
409 Conflictthat Flexo answers on the first commit to a new branch. When it hits step 10, the project-usage reads don't run and 2 more operations show as uncovered.KnownServerDivergences, each with a narrow matcher, so the verdict lists only what the client misses:GET /projects/{projectId}/commits/{compareCommitId}/diff(no 2xx, no 4xx; 501)POST /projects/{projectId}/branches/{targetBranchId}/merge(no 2xx, no 4xx; 501)GET /projects/{projectId}/query-results(no 2xx, no 4xx; 501)PUT /projects/{projectId}/queries/{queryId}(no 4xx; creates a missing query)DELETE /projects/{projectId}/branches/{branchId}(no 4xx; succeeds on an unknown branch)atandaftertriggers their arguments, typed from the model library, which needs the model library in the scenario.Documentation and upstream
SySML2.NET.REST.Tests/INTEGRATION_TEST_PLAN.mdagainst what the scenario now covers.SySML2.NET.REST.Tests/Helpers/KnownServerDivergences.cs, including:previousCommitis sent as an object instead of an array;owner;@type;application/jsonError body.Delivery
development.[Add] Integration test plan for the REST client against Flexo (#407)
[Add] Flexo integration scenario stage 1: test host, OpenAPI conforma…
[Add] Flexo integration scenario stage 2: KerML Core, Kernel and upda…
[Add] Flexo integration scenario stage 3: SysML structure, behaviour …
[Update] Flexo integration scenario: read lists in large pages, check…
[Add] Flexo integration scenario stage 4: queries, project usage and …
[Add] Flexo integration scenario stage 5: delete and teardown steps 1…
[Add] Flexo integration scenario triage: every property set and chang…
[Update] Flexo integration scenario: drop the #428 workaround in Mode…
Fix #407: single integration fixture with assertions and status checks
[Update] Flexo integration scenario: resolve SonarQube findings in th…