Skip to content

[Feature]: Verify REST Api client against compliant server #407

Closed

Description

@antoineatsoprasteria

What type of issue is this?

  • Bug report
  • Feature request

Prerequisites

  • I have written a descriptive issue title
  • 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):
  • .NET Framework version:
  • Additional information:

Activity

  1. samatstariongroup commented on Nov 9, 2026

    @samatstariongroup
    Member

    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)

    Scenario fixture

    • 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.

    Delivery

  2. added a commit that references this issue on Nov 10, 2026
    a637625
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions