LegacyApplication explicitly uses "reindeer" as default theme.
Extended AbstractTestUI to AbstractReindeerTestUI, that all old tests now inherit.
All new tests should be based on AbstractTestUI.
Also added AbstractReindeerTestUIWithLog for those that needed it.
Removed all found @Theme("valo") and used proper parent test class.
Change-Id: I0bb45850f3f1d39c6f78dac35dfa08acbad427ad
Move and rename server classes which go into the compatibility package
* Use com.vaadin.v7
* Use the same class name as in Vaadin 7
* Use a "vaadin7-" declarative prefix for Vaadin 7 components
Change-Id: I19a27f3835b18980b91a4f8f9464b2adde1a5fd5
IE hacks cause calls to onScroll in situations where the cache row fetch
logic is not working correctly (causes JS exception). This change has an
optimization to pass this logic if there are no rows available and this
way fixes the JS exception as well.
Change-Id: I3425f3d75cad8b65e605638343b167abf7b48067
Update TB3+ convention to use a separate *Test file
For any issue there should be a UI class, e.g. LabelSomething and a
Test class which has the name of the UI + Test, e.g. LabelSomethingTest.
The LabelSomethingTest contains ALL tests which depend on LabelSomething
and are named accordingly to what they test.
For special and legacy cases also LegacyApplication and UIProvider are
supported in addition to UI classes
Change-Id: Ifc0180b377284bbd029202494ad194d324f8213b
* openTestUrl() must be called in the beginning of each test. Before that setPush and setDebug can be used to determine whether /run-push or ?debug should be used in the URL
Change-Id: Ie70996fcbdb2769fcd4ec56cb878e20198e02bf6