open gui test to sight-dependant projects
Description
The GUI tests are a great accet of sight, allowing the automatisation of applications' tests by automatically running it.
However, the gui core headers are not exported, which makes it impossible to use this part of sight in sight-dependant projects.
Functional specifications
the GUI test should run in sight-dependant projects
Technical specifications
- rename the gui test core folder to testCore
- change the ITest profile path handling, by geting the full path, and not using "getWorkingDir()". It will be up to the GUI tests to provide the full profile path.
- add the profile modules. The clasicall sightrun looks for the modules situated relatively to the profile path. This allows to load automatically the project modules; This will be done in the ITest too, at the test setup()
- add -B bundlesPath in the cppunit_main. Similarly to classical applications, the -B argument allows specifying additional bundles path. This will be handled in the unit test too.
- change test templates to add external libs path in the PATH variable and bundles path