I think VASTParserTest shouldn't be a GWTTestCase, that would be more useful when testing entry points than the file parse itself. so I was thinking maybe we could have that as a normal JUnit test. Also, I remember that a GWTTestCase loads the entry point xml file (gwt.xml) and it takes much longer than a regular JUnit test =/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Imported gwt-test-utils to improve our GWT unit testing, works much faster than the default GWTTestCase and we can also mocks stuff. I adapted the current tests.
I think VASTParserTest shouldn't be a GWTTestCase, that would be more useful when testing entry points than the file parse itself. so I was thinking maybe we could have that as a normal JUnit test. Also, I remember that a GWTTestCase loads the entry point xml file (gwt.xml) and it takes much longer than a regular JUnit test =/
Imported gwt-test-utils to improve our GWT unit testing, works much faster than the default GWTTestCase and we can also mocks stuff. I adapted the current tests.
https://github.com/gwt-test-utils/gwt-test-utils