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
common/src/main/java/tck/arquillian/protocol/common/TsTestPropsBuilder.java is setting wrong test_classname property for ee.jakarta.tck.persistence.core.EntityGraph.ClientPuservletTest
#133
Closed
scottmarlow opened this issue
Aug 29, 2024
· 1 comment
Instead of setting "test_classname" property to "ee.jakarta.tck.persistence.core.EntityGraph.ClientPuservletTest" we seem to be setting it to the super class ee.jakarta.tck.persistence.core.EntityGraph.Client.
Currently, we set via:
// The vehicle harness operates on the legacy CTS superclass of the Junit5 class.
// unless the Junit5 test class directly extends the EETest/ServiceEETest class.
if(isAbstract(testSuperclass)) {
props.setProperty("test_classname", testClass.getName());
} else {
props.setProperty("test_classname", testSuperclass.getName());
}
For ee.jakarta.tck.persistence.core.EntityGraph.ClientPuservletTest, we should use the testClass
The text was updated successfully, but these errors were encountered:
That is what is required for most tests and the generated test class is really just a shell that adds the junit test annotations and arquillian deployment method. The real test logic is still in the base class for these tests. With the jpa refactoring, I guess that is not the case. I'll look at the ee.jakarta.tck.persistence.core.EntityGraph.ClientPuservletTest.
Instead of setting "test_classname" property to "ee.jakarta.tck.persistence.core.EntityGraph.ClientPuservletTest" we seem to be setting it to the super class ee.jakarta.tck.persistence.core.EntityGraph.Client.
Currently, we set via:
For ee.jakarta.tck.persistence.core.EntityGraph.ClientPuservletTest, we should use the
testClass
The text was updated successfully, but these errors were encountered: