search

jcp-org / jsr358

0 stars 0 forks source link

JSR358-31: Strengthen TCK quality requirements #26

Open apastsya opened 12 years ago

apastsya commented 12 years ago

Jira issue originally created by user pcurran:

The Process Document contains language intended to ensure TCK quality, but this is typically not enforced.

EC members have an obligation to review TCKs for quality before voting their Final Approval, but many do not.

Should we enforce or strengthen TCK quality requirements?

apastsya commented 12 years ago

Comment created by lightguard:

How would you propose we go about doing this? Seems like a tool would be useful. Perhaps something like what was done for CDI? http://docs.jboss.org/cdi/tck/reference/1.0.1-Final/html_single/#d0e791

apastsya commented 11 years ago

Comment created by ebresie:

Hope this is not out of scope...

To me Quality requirement implies a requirement is implemented as expected.

TCK seems more low level "Unit Test" level as opposed to higher level "Acceptance Test" level. Acceptance testing may have some overlap with unit test but they are still slightly different.

Maybe the Spec could better spell out the Acceptance criteria requirements.

Or maybe some form of TCK (Acceptance Test Plan) Spec with Acceptance requirements defined could help. Drawback is could potentially add extra "work" to the mix, but this could potentially allow "clean implementations" to implement there own TCK relative to the TCK Spec requirements.

apastsya commented 11 years ago

Comment created by ebresie:

I assume this is address by other non-implementer involvement, but there may still be some bias among participants.

Should an "independent" participant not involved in the group be considered to insure quality? Maybe a Quality EG?