jakartaee / jakartaee/batch-tck
Parameterize (or eliminate) high-level qualifier (schema) for TCK test application table names
Open
enhancement
- Dominant language
- Java
- Stars
- 2
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
See discussion in https://github.com/eclipse-ee4j/batch-tck/issues/51, where we agreed to workaround the limitation and close the TCK challenge, while opening a new issue (this issue) to enhance the TCK in the future.
Contributor guide
Research direction
Start with the discussion in eclipse-ee4j/batch-tck#51, then inspect how the TCK test application table names use a high-level schema qualifier. Done means agreeing on and implementing a future approach that parameterizes or eliminates that qualifier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100