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
Enforcing subclassing of TestBenchTestCase makes integration in various contexts problematic.
If I would try to implement a Test using TestBench and another tool which forces subclassing of its own XyzTestCase, it would be impossible to use both.
UI Testing is just one aspect of a test, but very often not the only aspect.
JUnit 4 provides Rules, JUnit 5 provides Extensions and I guess TestNG also has a convenient way to integrate with multiple test libraries.
It would be great if Vaadin could provide a TestBenchRule for JUnit 4 and a TestBenchExtension for JUnit 5 if that would allow dropping the extends TestBenchTestCase.
The text was updated successfully, but these errors were encountered:
skiedrowski
changed the title
allow TestBench usage with subclassing
allow TestBench usage without subclassing
Apr 30, 2021
I'm currently on JUnit5 migration and that's a good point. I've already switched to extensions but still parent class is required. I will analyze it and try to do some PoC's within #1551
Enforcing subclassing of
TestBenchTestCase
makes integration in various contexts problematic.If I would try to implement a Test using TestBench and another tool which forces subclassing of its own
XyzTestCase
, it would be impossible to use both.UI Testing is just one aspect of a test, but very often not the only aspect.
JUnit 4 provides Rules, JUnit 5 provides Extensions and I guess TestNG also has a convenient way to integrate with multiple test libraries.
It would be great if Vaadin could provide a
TestBenchRule
for JUnit 4 and aTestBenchExtension
for JUnit 5 if that would allow dropping theextends TestBenchTestCase
.The text was updated successfully, but these errors were encountered: