* Integration tests moved from uitest to separate test modules
* Run TB4 tests with maven profile
* Remove old ant/ivy build scripts from uitest
* Add 'needs-ssh' test category for reconnection test
* Add default values for testing and validation builds
* Add placeholder build.xml with instructions to run Maven
The target allows running both normal and server integration tests
without cleaning the screenshot directory in between.
Change-Id: Ic0d5db325b831114434a83c7d77be36ac8b20a61
This change removes publishing related Ivy files and Ant targets etc.
Further cleanup will be done in later changesets.
Change-Id: Ibe430495e85a1b0f3538072a4823c627ddac2924
Create a Valo icon font for icons used in Valo (#18472)
Valo uses only a handful of icons from Font Awesome. This change
introduces a separate icon font for valo (9KB instead of 80KB) and
decouples Valo from Font Awesome to enable updating Font Awesome
without taking Valo into account.
This change also makes it easy to not load Font Awesome when using Valo
by setting $v-font-awesome:false
For backwards compatibility, Font Awesome is loaded by default
Change-Id: Ib01e3cf34e2468c885fcb8c7859cd1d1af4491aa
A new variation named “Light”, similar to iOS7 style.
Fix some valo-menu styles to accommodate the new light style better.
Change-Id: Ib7c396263db7838c972d75a6b79fed1caf7ca576
Output test results in XML reports instead of to standard output
This is a workaround for a problem with the integrated TeamCity JUnit
listener which is not thread safe. Without this the test results are
completely mixed up in TeamCity. For more information, see
http://youtrack.jetbrains.com/issue/TW-33176.
All standard JUnit test reports is put in result/reports. For uitest
there are three report directories: result/reports-tb2,
result/reports-tb3 and result/reports-integration to be able to clean
the directories before running a given type of tests.
This change is based on the separate fixes by John.
Change-Id: I2f0dee416f6745544636f2f3dcea0d0832ff8076
Refactored build scripts to support TB2, TB3 + integration tests (#12572)
* Main build configuration triggers unit tests for all modules and uitest/build.xml testbench tests in parallel
* uitest/build.xml triggers Jetty startup and integration (server) tests in parallel. After the server has started, TB2 and TB3 tests are run in parallel.
* Server integration tests for servlet containers are run using TB3 and the com.vaadin.tests.tb3.ServletIntegrationTests test suite.
* Portlet integration tests are still run using TB2 test scripts
Change-Id: Ie6bffd4e68b4889074e9c470faa3c65f923e55c4
Renamed "tests" target to "test" and added "test-all" (#9998)
The "test" target runs all tests which do not require additional servers or setup. Can be run immediately after cloning the project.
The "test-all" target runs also integration tests and UI tests which require access to servers or additional setup.
Change-Id: I2f5371dc5be805ba12766c8187a2b58fbc7f7db4
* Validates that all java files contains a license file and fails the build if a license is missing
* For now runs a lot of checks with a severity less than error to avoid failing the build
* Outputs test results to TeamCity for reporting
Change-Id: I24ca9cd0646a4bc530ef3a183eef1bc4addc555d
Teemu Suo-Anttila
Henri Sara
Artur Signell
Teemu Suo-Anttila
elmot
Jouni Koivuviita
Sauli Tähkäpää
Leif Åstrand
Pekka Hyvönen