Giter VIP home page Giter VIP logo

Comments (6)

dgagne avatar dgagne commented on August 22, 2024

We should change the term "skip" for "not implemented"
This way the semantic will be clear.

from tck.

DanielThanner avatar DanielThanner commented on August 22, 2024

"skipped" is currently used if the vendor doesn't support this feature. Therefore we should rename it to "unsupported". "not implemented" would be also okay.

Additionally we can introduce a new category: "currently under development" or "available in future releases" This category can be used to signal that the vendor has planned to support this feature in the near future.

If a vendor does not publish results for all test cases, unpublished test results are currently marked as "skipped". What about using the new category "unknown"?

Overview of all categories:

  • unsupported
  • unknown
  • available in future releases
  • succeeded
  • failed

from tck.

etirelli avatar etirelli commented on August 22, 2024

I agree that we should re-vamp the statuses and I like the suggestions from @DanielThanner , except for the "available in future releases". Unfortunately, I am afraid that this would then become the new go to status and would just replace "skipped" for all tests not supported by a vendor.

I think the following list provides proper reflection of what the current status of each product is:

  • unsupported
  • unknown
  • succeeded
  • failed

from tck.

etirelli avatar etirelli commented on August 22, 2024

As discussed in the call, the following statuses will be supported going forward:

  • result missing: the vendor did not submit a result for the test
  • succeeded: the test runs successfully
  • failed: the test fails on execution
  • not supported: the test is not supported

from tck.

etirelli avatar etirelli commented on August 22, 2024

Submitted PR #189 to implement the change discussed here. Please note that at the moment I did not make any change to the way vendors report results, as it wasn't necessary. I just changed the way the website reported the results:

  • succeeded
  • failed
  • not supported
  • missing

For not supported tests, vendor will continue to report the status on the results file as "IGNORED", to avoid changing their runners and old reported files. On the website, these tests will show as "not supported".

Please review the PR and if approved we can close this ticket.

from tck.

agilepro avatar agilepro commented on August 22, 2024

PR has been merged that takes care of this.

from tck.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.