to remove the -ea argument worked too. i could remove the comment in my xml
file and got a positive result.
Thank you
by the way, yes i am using gwt version 2.7
Am Dienstag, 14. Februar 2017 11:52:33 UTC+1 schrieb Daniel Kln:
>
> Hi,
>
> i setted in the run config the arg:
Thank you thomas, caused by your hint i could find the mistake.
in my gwt.xml file i added a block comment around:
this solved the problem.
Am Dienstag, 14. Februar 2017 11:52:33 UTC+1 schrieb Daniel Kln:
>
> Hi,
>
> i setted in the run config the arg: -Dgwt.args="-runStyle Manual:1".
>
>
One workaround that just came to my mind: because code does not run in Java
(prod mode), you don't need to run tests with Java assertions enabled (i.e.
remove -ea from JVM arguments); GWT assertions are governed by an -ea flag
in -Dgwt.args=, independent from the -ea flag of the JVM.
HTH.
On
This looks like https://github.com/gwtproject/gwt/issues/9413
IIRC, it's triggered depending on how the tests are run, and which binding
properties are defined in the gwt.xml files (in the reprocase for the
issue, there's a binding property that's never used in any rebind rule;
commenting it
My source code:
@Override
public String getModuleName() {
return "de.abc.application.Application";
}
/***
* Test 1
*/
@Test
public void testBrowserVersion() {
System.out.println("Test 1: Starting test to validate the browser
version");
Hi Jens,
i tried also tried your solution. Result:
java.lang.AssertionError
at com.google.gwt.dev.Permutation.assertSameAnswers(Permutation.java:105)
at com.google.gwt.dev.Permutation.mergeFrom(Permutation.java:80)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:322)
at
You have to use -Dgwt.args="-prod -runStyle Manual:1" so that the test
will be compiled to JS without the need of the legacy DevMode plugin.
-- J.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving
the image shows my browser result. they say in the text that this should
happen, but it doesn t work. so i need an alternativ with the same result
except selenium.
Am Dienstag, 14. Februar 2017 11:52:33 UTC+1 schrieb Daniel Kln:
>
> Hi,
>
> i setted in the run config the arg:
i am following this instruction
(http://www.gwtproject.org/doc/latest/DevGuideTesting.html):
Running your test in Manual Mode
Manual-mode tests allow you to run unit tests manually on any browser. In
this mode, the JUnitShell main class runs as usual on a specified GWT
module, but instead of
Hi,
so i am using eclipse. Right click on the package, which contains the test
class which extends from GWTTestCase -> Run as -> Run configurations ->
Arguments -> VM arguments -> Setting argument -> Apply -> Run
Console shows:
Please navigate your browser to this URL:
I think if you provide details of your deployment process it could be
easier to diagnose the issue.
On Tuesday, February 14, 2017 at 5:52:33 AM UTC-5, Daniel Kln wrote:
>
> Hi,
>
> i setted in the run config the arg: -Dgwt.args="-runStyle Manual:1".
>
> When i start running the gwt unit test, i
Hi,
i setted in the run config the arg: -Dgwt.args="-runStyle Manual:1".
When i start running the gwt unit test, i get a link, which i have to paste
into a browser of my choice. This is what i expected. But than the browser
shows:
Development Mode requires the GWT Developer Plugin
My
12 matches
Mail list logo
