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
You can also write pure JUnit (not GWT JUnit) tests in a separate project
and use syncproxy for calling your RPC services synchronously (very desired
behavior for testing RPC services). In this tutorial I try to explain, step
by step how to do it:
It seems you dont have defined the rpc servlet in the
com/TestGreeting.gwt.xml used
for testing
If you want to take a look how a rpc test looks like you could take a look
to the example test generated by webAppCreator:
/path_to_gwt_sdk/webAppCreator -maven -noant -out hello com.example
then
Did you ever figure out what was going wrong? I'm having the same error.
On Tuesday, October 2, 2012 12:15:15 PM UTC-4, Manuel Carrasco wrote:
What is the content of your com/TestGreeting.gwt.xml file ?
On Fri, Sep 28, 2012 at 11:18 AM, Ronsen sonne...@hotmail.dejavascript:
wrote:
Hi.
I want to test a rpc call. I use the standard GWTproject and this
testclass:
public class TestGreetingService extends GWTTestCase {
/**
* Must refer to a valid module that sources this class.
*/
public String getModuleName() {
return com.TestGreeting;
}
What is the content of your com/TestGreeting.gwt.xml file ?
On Fri, Sep 28, 2012 at 11:18 AM, Ronsen sonne.1...@hotmail.de wrote:
Hi.
I want to test a rpc call. I use the standard GWTproject and this
testclass:
public class TestGreetingService extends GWTTestCase {
/**
*
http://gwt-code-reviews.appspot.com/1224801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
.
Did you mean to run as a GWT JUnit Test instead of a JUnit Test?));
On 2010/12/16 19:43:39, rdayal wrote:
Suggestion:
No GWT devjar property found. Did you mean to run as a GWT JUnit Test
instead
of a JUnit Test? --
The gwt.devjar property has not been set. If you are using the Google
Plugin
On Tue, Dec 21, 2010 at 11:09 AM, p...@google.com wrote:
On 2010/12/16 19:43:39, rdayal wrote:
Is this system property required?
This is a tough one, because I don't think it's strictly required, but
the devjar has things such as the GWT devmode bridge and the GWT
compiler. Can you think
Reviewers: jlabanca, rdayal,
Description:
Add a warning in GWTTestCase to help users that accidentally run a GWT
JUnit Test as a JUnit Test.
This mistake is easy to make (especially in Eclipse.) Therefore, we
display a helpful error suggesting the user run as a GWTJUnitTest if an
exception
LGTM
http://gwt-code-reviews.appspot.com/1224801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
devjar property found.
Did you mean to run as a GWT JUnit Test instead of a JUnit Test?));
Suggestion:
No GWT devjar property found. Did you mean to run as a GWT JUnit Test
instead of a JUnit Test? --
The gwt.devjar property has not been set. If you are using the Google
Plugin for Eclipse, you
Hi,
Agree with Lukasz on separating the two layers.
Also, if your DAO class (or any other class you want to test) needs a
full J2EE container (which I suspect it might), then I don't think it
will run properly under JUnit. I ran into problems trying to test my
persistence code with JUnit
Usually you would separate this two layers of your application - you
would have a service layer and a DAO layer. The service classes
contains the logic accessible for the client and DAO takes care only
of the data access. In this case you can write nice unit tests for
your DAO and you don't need
Hi Lukasz,
Thanks for the reply. About my test logic (which I'm starting to
believe that it's wrong) is this:
I want to test my Hibernate DAO (let's call it UserDAO) which extends
GWT's RemoteService, so my project looks like this:
- GWT
- com.gwt.client
- interface userDAO
Can you post your actual test logic? I don't understand why do you
need to go through the GWT servlets to do some unit testing of your
DAO. It would be better to test the DAO logic separately.
On 8 Okt., 04:33, VrmpX vrm...@gmail.com wrote:
Hello,
I'm currently using GWT 2.0.4 with Hibernate3,
Hello,
I'm currently using GWT 2.0.4 with Hibernate3, on Eclipse Helios, to
create a simple web application. So far, I'm able to reach the
database and do some RPC's to the server perfectly without any
problem.
The problem arises whenever I try to test out my server classes (the
data access
Hi John,
John Tamplin wrote:
...
EmbeddedTomcatServer creates a tomcat directory inside of the current
working directory (via the user.dir system property) at line 340. It
looks like you could maintain your own copy of
com/google/gwt/dev/etc/tomcat and point the system property
+[jat]
Hi Marc,
On Thu, Apr 1, 2010 at 8:34 AM, Marc Guillemot mguille...@yahoo.fr wrote:
Hi,
running a unit test that extends GWTTestCase using Eclipse's Run As GWT
JUnit test generates two folders in my project root:
- tomcat
- www-test
This is just garbage and it pollutes my folder
On Tue, Apr 6, 2010 at 10:58 AM, Rajeev Dayal rda...@google.com wrote:
The tomcat folder is surprising, I thought that GWT was using Jetty now.
www-test can be configured in the run configuration for the test but it
is very annoying to have to do it again and again for all the tests.
Tomcat
Hi,
running a unit test that extends GWTTestCase using Eclipse's Run As GWT
JUnit test generates two folders in my project root:
- tomcat
- www-test
This is just garbage and it pollutes my folder. I'm force to see them
and to add them to SVN ignore. Is there a way to avoid it and to tell
32 matches
Mail list logo
