Add maven based server tests for Wildfly and Jetty (#10116)
This patch refactors the generic integration test war into
two jar dependencies and individual modules for different servers.
There is now a common approach for making configurations for the
remaining server tests still executed through an Ant build script.
* 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
Use PhantomJS2 for server integration tests (#8030)
* Run server integration tests with PhantomJS2
* Add delay to integration test screenshots
Otherwise, the progress indicator might still be fading when the
screenshot is taken, and the screenshots are not fully stable.
* Reduce integration test startup delays
* Add PhantomJS2 screenshots for integration tests
* Add PhantomJS2 screenshots for tomcat 7 proxy test
Seems like the randomization is not thread safe and from time to time
causes all server tests to fail with
"integration_tests.xml:251: Only 1 operation can be specified"
Change-Id: I41774fb4d7637e3485a82ef0096193c73a201eb5
The theme was designed for Liferay 6.0 and was following its look.
Liferay 6.0 is no longer officially supported by Vaadin 8.
Change-Id: I79e8ecd6674b1dce2424121d4c298b69d3f932d4
WebSphere 8 prior to 8.5.5.9 does not support Java 8.
Glassfish 3 does not support Java 8 out of the box.
Change-Id: I623951ec2fa180a3c520ae24b27837f8b6d81ea2
Remove all integration tests whose servers do not support Servlet 3.0
and some other obsolete servers.
Change-Id: I648bda9a74579be69cb54864fa526d3105742b9b
Nginx + Wildfly 9 test for various proxy configurations (#11733)
* /nonbuffering a proxy without any buffering
* /buffering tests a buffering proxy
* /nonbuffering-timeout tests a proxy without any buffering but with a 10s timeout set
* /buffering-timeout tests a buffering proxy with a 10s timeout set
Change-Id: I5d99cc29364e3ed888371fa18ee404f912d73223
GAE related fixes: another GAE app, new license, javadoc mistake fix(#18168)
Google forces applications owners to migrate all applications to
a new [High Replication] DataStorage. An old Vaadin application is deleted,
and a new one is created because of that migration.
GAE license is replaced with latest one.
Change-Id: Ie6de09f0c1c621308ad8e0cfc2ba7b42bfb10429
- Based on TB4 Parallel testing.
- Browser setup no longer uses static capabilities.
- Some code cleanup here and there.
Change-Id: I5c419316cd36f4f5041eaa8da8fda3d8b46596c4
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
Unified all portal integration tests to be based on JSR286Portlet (#8013, #9566, #11314)
All portal tests are now based on the same test script. Portal tests avoid Vaadin locators to avoid random problems with the portlet id changing between test runs.
* eXo 3 test must be run on Firefox, does not work in Chrome
* Liferay theme test is now a separate test which does not depend on the Liferay integration test
* Changing to maximized state using an action URL does not work with GateIn or eXo
* The edit mode link does not work in WebLogic Portal as WebLogic feels it is not an allowed mode for the portlet
Change-Id: I7a683688d8ffc611e211f8a60889a34b233b81c9