Skip to content

Improve reports #31

@berezovskyi

Description

@berezovskyi

I have finally managed to:

  1. Run the suite against the RefImpl 2020 CM server.
  2. Generate a report from the command line without Eclipse (but with Ant, potentially we may be able to replace it with a standalone XSLT processor like Saxon).

The idea behind this is to run the test suite against the RefImpl server containers via GH Action (+taking advantage of their support for the "service" containers that run along the Action container) and publish the reports via GH Pages.

The output looks like this:

image

Here are a few things that are wrong with it:

  1. It hardcodes the number of expected MUSTs and corresponding tests that have to pass in order for the OSLC server to be considered conformant.
  2. It uses the word "Provider". We agreed long time ago to call it "OSLC Server" AFAIK.
  3. It defines levels arbitrarily just based on the number of MUSTs, SHOULDs, and MAYs satisfied. As discussed in the OSLC OP call on 2021-07-29, we might want to define a "bare minimum" level (just MUSTs) with new levels on top but focused on business-level features offered by conformant OSLC Servers (e.g. error reporting if the TRS supported well or graphical resource creation and selection if all DUI capabilities are in places and CORS/CSP are set correctly).
  4. It says on top " OSLC Unit Test Report". It should be "OSLC Conformance Test Report (Eclipse Lyo TestSuite)" or similar. Better yet, "'OSLC RefImpl 2020 CM' Server OSLC Conformance Test Report". And on the next line, "Generated by Eclipse Lyo TestSuite v4.1.0.alpha2 (2020-08-01)".
  5. It says in the image "OSLC TestSuite Execution Summary". I am confused a bit by the font size, took a little while to understand it's not a page heading but a title of the image. Maybe we can make it smaller.
  6. "Error (MUSTS)" in the picture is misleading. As you see at the bottom of the report, 55 tests were actually run and 0 failed. This is because I tweaked the test suite config for the RefImpl 2020 CM server to turn off checking various (optional) OSLC capabilities. "Error (MUSTS)" makes the server look completely non-conformant. Cf. point 1 on hardcoding.
  7. The "OSLC TestSuite Execution Summary" table only lists the server MUST conformance and does not mention SHOULDs and MAYs. Why?
  8. Some tests fail on conditions that do not have a corresponding CC in the spec. See AbstractCreationAndUpdateRdfTests requires at least one instanceShape property value to update a resource #30, for example.
  9. The "Unit Test Summary" table is useless. We should go over a mapping between unit test methods and CM RFC clauses and add CC IDs and maybe the definitions of levels as discussed in the meeting such that we could print them all in a table and show which CCs are violated and group them by "levels" such as QC, DUI etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions