Open starksm64 opened 2 years ago
Emily has created a template in the Platform project
ACTION: Figure out a way to propagate this to all specification repositories. Either by scripting or manually. Ask IT team if Otterdog can be used for this
https://github.com/jakartaee/platform/blob/main/.github/ISSUE_TEMPLATE/tck_challenge.md
Next step is create PR against the specification projects, this issue will be used to track the progress of notifying the specification projects. The first PR to be used as a "template".
Create a PR for the spec projects below like this:
Subject: Update issue template for TCK challenges
Description: A uniform issue template for TCK challenges across all Jakarta EE Specifications
File to update: <project repository>/.github/ISSUE_TEMPLATE/tck_challenge.md
---
name: TCK Challenge
about: Create a TCK Challenge
title: ''
labels: 'challenge'
assignees: ''
---
**Challenged tests**
List the challenged tests with the fully qualified classnames and then the test methods, e.g.
ee.jakarta.tck.faces.test.javaee7.multiFieldValidation.Spec1IT#testFailingPreconditionsNotAfterAllInputComponents
**TCK Version**
Specify the version of the TCK, e.g. Jakarta Faces 4.0.x
**Description**
A clear and concise description of why you think the tests are wrong.
**Additional context**
Add any other context about the challenge here.
Tick off the checkbox when done for a specification.
I have done about half. An example of the PR can be found here. Please help out if you have any spare time.
Related to #57, one way to fix the current problem of not being able to apply challenge labels to issues would be to create issue templates that did so automatically. It appears that only users with write access can assign labels to issues. I don't see a way to assign permissions on a per label basis, so an issue template would be the only way.