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
[merge from 6.7] Attempt at evening the load of the integration tests by starting all lightweight servers immediately and the more heavy servers later on
Artur Signell
Henri Sara
elmot
Miki
Teemu Suo-Anttila
Sauli Tähkäpää
Thomas
John Ahlroos
Leif Åstrand
Automerge
Artur Signell
Johannes Dahlström