Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All spec projects should have issue templates for TCK challenges #58

Open
starksm64 opened this issue Jun 29, 2022 · 4 comments
Open

All spec projects should have issue templates for TCK challenges #58

starksm64 opened this issue Jun 29, 2022 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@starksm64
Copy link
Contributor

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.

@paulbuck paulbuck added the enhancement New feature or request label Jul 26, 2022
@ivargrimstad
Copy link
Member

ivargrimstad commented Jul 10, 2024

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

@paulbuck
Copy link

paulbuck commented Sep 4, 2024

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".

@ivargrimstad
Copy link
Member

ivargrimstad commented Sep 4, 2024

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.

  • Jakarta Activation
  • Jakarta Annotations
  • Jakarta Authentication
  • Jakarta Authorization
  • Jakarta Batch
  • Jakarta Concurrency
  • Jakarta Config
  • Jakarta Connectors
  • Jakarta Contexts and Dependency Injection
  • Jakarta Data
  • Jakarta Debugging Support for Other Languages
  • Jakarta Dependency Injection
  • Jakarta Deployment
  • Jakarta Enterprise Beans
  • Jakarta Enterprise Web Services
  • Jakarta Expression Language
  • Jakarta Faces
  • Jakarta Interceptors
  • Jakarta JSON Binding
  • Jakarta JSON Processing
  • Jakarta Mail
  • Jakarta Managed Beands
  • Jakarta Management
  • Jakarta Messaging
  • Jakarta MVC
  • Jakarta NoSQL
  • Jakarta Pages
  • Jakarta Persistence
  • Jakarta RESTful Web Services
  • Jakarta RPC
  • Jakarta Security
  • Jakarta Servlet
  • Jakarta SOAP with Attachments
  • Jakarta Standard Tag Library
  • Jakarta Transactions
  • Jakarta Validation
  • Jakarta Web Services Metadata
  • Jakarta WebSocket
  • Jakarta XML Binding
  • Jakarta XML Registries
  • Jakarta XML RPC
  • Jakarta XML Web Services

@Emily-Jiang
Copy link

Emily-Jiang commented Sep 19, 2024

I have done about half. An example of the PR can be found here. Please help out if you have any spare time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants