SWTBot UI Test Set and Test Structure

In the package org.eclipse.fordiac.ide.test.ui.swtbot contains the 4diac IDE specific extensions, as 4diac has some characteristics that require these extensions to the test framework. E.g. SWTBot would jump from one point to another when dragging a FB. However, 4diac also needs a small mouse movement to perform this action. The overwritten method mouseDrag of the class SWTBot4diacFigureCanvas adds the necessary mouse movement, and also the necessary changes of the calling classes were made.

The 4 classes are:

The base class for all SWTBot UI tests is the Abstract4diacUITests class in package org.eclipse.fordiac.ide.test.ui. It takes care of the generally defined @BeforeAll, @AfterEach and test execution methods. The class is not intended for tests but for smooth test execution so that every test has the same execution conditions.

An exception is the class New4diacProjectTest, which does not require any preparatory actions, as it tests whether a project can be created with permitted and non-permitted names.

The Abstract4diacUITests class is the base class for all SWTBot UI Tests and it has 2 types of assisting classes in the package org.eclipse.fordiac.ide.test.ui.helpers. The final helper classes and the supporting Bot classes.

In the final helper classes (blue) are all static constants of names outsourced. As the name suggests, the supporting Bot classes (orange) contain a Bot for a particular sub-test task.

The tests are divided into serveral packages and classes.