Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Scout/Concepts/Testing Support
The Scout documentation has been moved to https://eclipsescout.github.io/.
This page describes the support included in Scout to test your Scout Application.
Contents
Type of tests
JUnit is probably one of the most well-known tools in the library community. In the context of testing scout application, it is used as base for different kind of test (not only unit tests).
Unit tests
Those tests are plain JUnit tests. They need to be executed quickly and provide immediate feeback on what a method is doing. They are useful for testing small units of code without any other dependencies.
Unit tests with Scout context
ClientTestRunner, ServerTestRunner
Tests with UI interaction
You write code for the model thread and for the UI thread. It is possible to write JUnit assertion.
Test with automated testing tool
These tools (have a look at Jubula if you want to use an open-source eclipse project) are working on a different layer: they consider the whole application as a black box. There is some scripting possibility to execute UI operation but this isn’t coding as a developer understand it. The target users are more Q&A members.
These tools are great for Acceptance testing and Regression testing. It is recommended to test the happy path with these tools, to ensure that the key feature of the application can be used.
Executing your tests
For the tests writen with JUnit (plain JUnit or with some extensions).
With maven tycho surefire
With an application
Scout additions to support tests
- ScoutAssert, ScoutClientAssert
- Test runners
- Test executor
- @DevTestMarker