You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently there's a few things that are not so great with the test schema
the only way to ignore a test is to set the attribute regressionTest to false, which is... weird
there's no way to execute a single test ("focus" a test). Some IDEs may provide this facility (eclipse), but some don't (intellij), and having an ide-independent way to do this would be nice
the attribute reinitializeRule of test-code is useless. I can't see a reason not to reinitialize the rule.
we could remove the pattern from the source-type element, as we do the validation at runtime anyway. This means we wouldn't have to update the schema when we add/remove languages, which makes pmd easier to extend
validation of consistency between expected-problems, expected-messages and expected-linenumbers is buggy. Sometimes it throws a validation error, sometimes it's silent. For instance
Describe the solution you'd like Update the schema and its parser to support focus and disabled attributes, deprecate useless things
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Some other things that we should keep in mind and fix later:
the <rule-property> element has ad-hoc syntax, instead of just reusing the syntax for <property> that's from the ruleset schema. This will be awkward when the XSD for rulesets is updated ([core] Implementation plan for property framework changes #1432)
Is your feature request related to a problem? Please describe.
Currently there's a few things that are not so great with the test schema
regressionTestto false, which is... weirdreinitializeRuleof test-code is useless. I can't see a reason not to reinitialize the rule.source-typeelement, as we do the validation at runtime anyway. This means we wouldn't have to update the schema when we add/remove languages, which makes pmd easier to extendthrows a validation error, but the following doesn't
Describe the solution you'd like Update the schema and its parser to support
focusanddisabledattributes, deprecate useless thingsDescribe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Some other things that we should keep in mind and fix later:
<rule-property>element has ad-hoc syntax, instead of just reusing the syntax for<property>that's from the ruleset schema. This will be awkward when the XSD for rulesets is updated ([core] Implementation plan for property framework changes #1432)useAuxClasspathattribute doesn't look useful. Related to [java] Improve rule tests with auxclasspath #2649