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
As an extension developer, I want to be able to easily write unit tests for the java classes I write.
The RefineTest and TestUtils classes that we use in the main module are test classes that are not designed for public consumption.
We could have a separate Maven module which would offer basic utilities (covering things such as workspace initialization, teardown and project creation) so that extensions can easily depend on such utilities for their tests.
We could also investigate how to do the same for Cypress tests, but I would keep that for a separate issue.
I intend to tackle this as part of the Maven modularization effort.
The text was updated successfully, but these errors were encountered:
And then one can use RefineTest and TestUtils directly.
It's not ideal because the artifact actually contains all of our tests as well, so it's rather big and stability is even less guaranteed than code in the main code base. So I'm hopeful that the Maven modularization will help trim that down to only contain stuff that we can reasonably keep quite stable.
As an extension developer, I want to be able to easily write unit tests for the java classes I write.
The
RefineTest
andTestUtils
classes that we use in themain
module are test classes that are not designed for public consumption.We could have a separate Maven module which would offer basic utilities (covering things such as workspace initialization, teardown and project creation) so that extensions can easily depend on such utilities for their tests.
We could also investigate how to do the same for Cypress tests, but I would keep that for a separate issue.
I intend to tackle this as part of the Maven modularization effort.
The text was updated successfully, but these errors were encountered: