Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

Requiring Profiles to include the applicable TCKs #53

Open
paulbuck opened this issue Jun 11, 2021 · 1 comment
Open

Requiring Profiles to include the applicable TCKs #53

paulbuck opened this issue Jun 11, 2021 · 1 comment

Comments

@paulbuck
Copy link

I am starting to think that Profiles need to be required to include the TCKs of their ingredient specifications. If the Profile's TCK is not at least as strong as the individual specification's TCK there may be a compatibility "gap". If that gap exists, code written to the API for an individual specification surfaced in a Profile may not run on a standalone compatible implementation of the the individual specification.

@starksm64
Copy link

My minimum operating assumption is that a profile specifies that all individual TCKs need to be run, and therefore it is at least as strong as the individual TCKs. This would allow that an individual TCK may have levels/profiles that group tests together such that some tests may not apply to a given profile.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants