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
I think the ultimate goal here is to replace robot tests with ide-probe tests and after this change probe tests should be easier to write, maintain, setup etc.
Generally probe will help with accessing intellij api through javascript put inside strings, need for reflection due to different classloader, reimplementing waiting for background tasks, opening projects and so on.
If we want to invoke internal intellij methods and have tests, we need to setup 4 modules (api, intellij plugin, driver, tests) vs. just tests module needed for robot. We have a way to do this with sbt (which is not perfect, we have hacks for sbt-intellij-plugin to be able to build more than one plugin in one project, yet it still is imperfect and can cause problems), also most of intellij plugins will use gradle rather than sbt. Perhaps we may want to prepare a drop in seed project with the 4 modules I mentioned with sbt and CI (similar what was done in pants) or better, figure out how to setup such layout with gradle.
The text was updated successfully, but these errors were encountered:
Git machete intellij plugin has some tests here: https://github.com/VirtusLab/git-machete-intellij-plugin/tree/develop/uiTests that use remote robot directly. This is nice set of scenarios we didn't cover so far
I think the ultimate goal here is to replace robot tests with ide-probe tests and after this change probe tests should be easier to write, maintain, setup etc.
Generally probe will help with accessing intellij api through javascript put inside strings, need for reflection due to different classloader, reimplementing waiting for background tasks, opening projects and so on.
If we want to invoke internal intellij methods and have tests, we need to setup 4 modules (api, intellij plugin, driver, tests) vs. just tests module needed for robot. We have a way to do this with sbt (which is not perfect, we have hacks for sbt-intellij-plugin to be able to build more than one plugin in one project, yet it still is imperfect and can cause problems), also most of intellij plugins will use gradle rather than sbt. Perhaps we may want to prepare a drop in seed project with the 4 modules I mentioned with sbt and CI (similar what was done in pants) or better, figure out how to setup such layout with gradle.
The text was updated successfully, but these errors were encountered: