| [jakarta.ee-spec.committee] Requirements for Platform/Profile TCKs |
| Here's the TCK Process document: This is what says the TCK requirements are that must be met by specification projects and what must be done by implementations to claim those requirements are met. If there's going to be a requirement that details a platform/profile must ensure tests for the technologies they include be runnable within the platform/profile implementation that requirement would be part of this document. The likely place would be somewhere in the opening in the "Role and Restrictions" section. The idea behind the that section, which could potentially use a better name, is to spell out that TCKs are meant to verify things from the user's perspective and that leads to the following requirements. The only following requirement mentioned is the namespace, specifically that `jakarta` cannot be used as users themselves are forbidden from using it. Ensuring tests can be run in the context that users will use the spec is another logical addition. Some scenarios: - If the spec says users can consume these technologies in Java SE, the tests should be runnable in Java SE - If the spec says users can consume these technologies in a Server, the tests should be runnable in a Server - If the spec says users can consume these technologies in an app client (heaven forbid we do that again), the tests should be runnable in an app client Ideally we write a requirement that is broad enough to address not just the situation at hand, but the concept broadly. Maybe some day we have the reverse situation where a spec that normally runs in a container decides to add Java SE flavor, but doesn't provide tests that can be run in Java SE. We'd want our requirement to be clear that this isn't allowed and if running in Java SE is promised, tests that verify it are required and relying on the in-container tests is not enough. Feel free to rework the "Role and Restrictions" section to the extent you're happy. Perhaps "Role and Restrictions" should be something more positive and extendable like "Role and Requirements" |