itsallcode / openfasttrace-intellij-plugin Goto Github PK

Situation

In order to be able to parse the specification items, we first need a grammar.

Acceptance Criteria

• SpecItem grammar exists

Follow the example from the Webinar: https://youtu.be/vAlor5-hC0Q?t=3302

Situation

At the moment there is no synchronization between the IntelliJ containing the Remote Robot server and the actual test.

So you have to start the Gradle task that runs an instrumented version of IntelliJ first and then the task that runs the test.

There are two possible options to fix this:
a) A Gradle task that ensure the server is up and running before we execute the tests
b) Starting the IDE from within the test: https://github.com/VirtusLab/ide-probe

Acceptance Criteria

• Can start the test from the command line with the server guaranteed-ready before the test.

Situation

IntelliJ uses a Gradle-based build setup for plugin development. The first step to developing a plugin is to get this build running.

Acceptance Criteria

• build an IntelliJ plugin that does nothing but load in IntelliJ

Acceptance Criteria

• CI Gradle build added
• CI Link checking added

Situation

IntelliJ plugins can be tested on two different levels: model/controller or directly on the UI.

UI tests are required to see if menu entries are there for example.#4

We need a basic UI tests to get the initial setup right.

Acceptance Criteria

1. UI tests proves that the menu entry for opening the OFT user guide exists.