new versions released !

[Gael Lazzari]

Hi everybody,

I'm glad to announce the release of gwt-test-utils-0.36 for GWT 2.4.0.

As usual, it includes a lot of changes / new features / fixes, such as :

• New GwtFinder API to be able to find attached Widgets by id, text, html, introspection path...
• Reduce de memory footprint of gwt-test-utils by cleaning the DOM heriarchy after each test
• HTML parsing improvements
• Improvements on Browser class
• Improvements on the CSV API
• Implement requested feature 46 : provide support for PlaceHistoryMapper
• Fix issues 104 & 105 : Gin support attempts to bind a Provider, and Guice complains
• Fix issue 106 : Support for @UiTemplate
• Fix issue 110 : Refactor the computing mechanism of resources relative URL
• Fix issue 112 : ignore XML namespaces while parsing XML with DOM (.gwt.xml and web.xml files)
• Fix issue 113 : implement JSONObject.toString()
• Fix issue 114 : handle @Source path relative to the classpath
• Fix issue 117 : Improve support for Window.Location and History
• Fix issue 119 : provide support for Grid UiBinding
• Fix issue 122 : don't substitute IsSerializable with Serializable when a class implements both interfaces
• Fix issue 124 : enable creation of Resources with multiple @Source paths
• Fix issue 127 : support for RepeatingCommand in Scheduler
• Fix issue 129 : implement support for @UiChild
• Fix issue 130 : patch gxt CSS class
• Fix support of RadioButton in radiogroup

At the same time, I released versions :

• 0.33.2 : for GWT 2.3.0
• 0.28.9 : for GWT 2.2.0
• 0.25.6 : for GWT 2.1.0 and 2.1.1
• 0.22.6 : for GWT 2.0.2, 2.0.3 and 2.0.4

Those "branches" versions include the same fixes and features as in the mainstream one.

gwt-test-utils would'nt be so advanced without your feedback and contributions. So thank you very much ! And never forget to communicate on it ;-)

--
Gaël Lazzari

[vasanth...@gmail.com]

Hi,

Can you please provide with a working sample of  writing test with gwt-test-utils + GIN ?. 

Our company wanted to use gwt--test-utils to test our GWT projects (with GIN)  . We could not move forward since your website does not have enough documentation for GIN integration with gwt-test-utils.

Can you please send us some links so that we see how really gwt-test-utils works with GIN?

[Gael Lazzari]

Hi Vasanth,

Is the GInjectorCreateHandler not working for you ? (https://github.com/gwt-test-utils/gwt-test-utils/wiki/Integration-with-GIN)

Whenever you try to create a GINInjector through deferred binding (GWT.create(MyInjector.class), gwt-test-utils will use the registered GInjectorCreateHandler to create the MyInjector class based on the @GinModules configuration.

If you want to customize the depencendy injection, for example you might want to inject a custom ServiceMock instance instead of a ServiceImpl one, you might want to look at jukito, which can be used in gwt-test-utils by using @RunWith(JukitoGwtTestRunner.class)

There are some gwt-test-utils + GIN tests examples available in gwt-test-utils sources : https://github.com/gwt-test-utils/gwt-test-utils/tree/master/gwt-test-utils/src/test/java/com/googlecode/gwt/test/gin

Hope that helps

Cheers,
Gael

 

2013/12/30 <vasanth...@gmail.com>

--
 
---
You received this message because you are subscribed to the Google Groups "gwt-test-utils-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gwt-test-utils-u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Gaël Lazzari

[vasanth...@gmail.com]

Thank you very much Gael that worked like charm :)

I was able to test my  activities (GIN) by jukito but in the view side i need to test the view by extentending GwtTestWithMockito  but it is giving me out of memory when i run the test.

Is there any problem with gwt-test-utils 0.45 with 2.5.1...

It works fine with GWT 2.4.0 and gwt-test-utils 0.41  but my project uses GWT 2.5.1 

Any suggestions would be really appreciated because i really really want to use gwt-test-utils . it is very easy to use.

This is the code.. Even the sample  test is not running it takes very very long time to run and in the end it gives out of memory exception

@GwtModule("com.hellomvp.HelloMVP")

public class HelloViewImplMockitoTest extends GwtTestWithMockito {

@Test

public void testSample() {

fail("Test executed but failed");

}

}

2013/12/30 <vasanth...@gmail.com>

To unsubscribe from this group and stop receiving emails from it, send an email to gwt-test-utils-users+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Gaël Lazzari