| Added unit tests for the PingServiceImpl. |
|
More...
|
almost 11 years ago
|
| Update the apptbook-gwt archetype to include unit and integration tests. |
|
More...
|
almost 11 years ago
|
| Added a GWT Sync Proxy test for the PingService in the Appointment Book GWT project. |
|
More...
|
almost 11 years ago
|
| Added GWT Test Case integration tests for the GWT Appointment Book project. |
|
More...
|
almost 11 years ago
|
| Added unit tests for the PingServiceImpl. |
|
More...
|
almost 11 years ago
|
| Update the airline-gwt archetype to include integration tests that run against a deployed GWT web application. |
|
More...
|
almost 11 years ago
|
| Added an integration test that uses GWT Sync Proxy to invoke the airline's PingService in a running GWT web application. |
|
More...
|
almost 11 years ago
|
| Added an integration test for the airline GWT original project that is run by the failsafe plugin and makes sure that the GWT web app can be deployed in a Jetty container. |
|
More...
|
almost 11 years ago
|
| Use GWT SyncProxy to remote invoke the DivisionService from an integration test. |
|
More...
|
almost 11 years ago
|
| Rename files in hopes of getting file name capitalization right |
|
More...
|
almost 11 years ago
|
| Rename files in hopes of getting file name capitalization right |
|
More...
|
almost 11 years ago
|
| Rename files in hopes of getting file name capitalization right |
|
More...
|
almost 11 years ago
|
| Rename files in hopes of getting file name capitalization right |
|
More...
|
almost 11 years ago
|
| Add integration tests to the GWT project that are not GWTTestCases. These tests are run using the failsafe plugin and test the deploy GWT web application. |
|
More...
|
almost 11 years ago
|
| Don't try to run GWT integration tests with the failsafe plugin. |
|
More...
|
almost 11 years ago
|
| Ignore the generated "war" directory |
|
More...
|
almost 11 years ago
|
| Deploy GWT example application to /gwt in Jetty. Deploying it to the root context was weird. |
|
More...
|
almost 11 years ago
|
| To begin to address issue #30, add GWTTestCase integration tests to the airline GWT project archetype. |
|
More...
|
almost 11 years ago
|
| Depend on the subset of Guava that works with GWT client-side code. |
|
More...
|
almost 11 years ago
|
| Refactor AirlineGWT so that it can be tested with integration tests. |
|
More...
|
almost 11 years ago
|
| Added a simple GWT Integration Test for the airline application. |
|
More...
|
almost 11 years ago
|
| Add integration test sources and resources for all GWT projects. Note that these extra classes and resources are added to the plain-old "test" sources and resources and not the "integration test" sources and resource because the gwt:test goal does not allow additional classpath entries (it-classes) to be added. |
|
More...
|
almost 11 years ago
|
| Use concrete types in GWT interfaces to avoid casting. |
|
More...
|
almost 11 years ago
|
| Merge pull request #137 from DavidWhitlock/issue-122-send-412-with-missing-parameter |
|
More...
|
almost 11 years ago
|
| Add an integration test to the phone bill web archetype that verifies that the expected HTTP error code is issued when a parameter is missing. |
|
More...
|
almost 11 years ago
|
| Add an integration test to the original phone bill web application that verifies that the expected HTTP error code is issued when a parameter is missing. |
|
More...
|
almost 11 years ago
|
| Add an integration test to the appointment book web archetype that verifies that the expected HTTP error code is issued when a parameter is missing. |
|
More...
|
almost 11 years ago
|
| Add an integration test to the original appointment book web application that verifies that the expected HTTP error code is issued when a parameter is missing. |
|
More...
|
almost 11 years ago
|
| Add an integration test to the airline web archetype that verifies that the expected HTTP error code is issued when a parameter is missing. |
|
More...
|
almost 11 years ago
|
| Begin to address issue #122 by adding an integration test to the original airline web application that verifies that the expected HTTP error code is issued when a parameter is missing. |
|
More...
|
almost 11 years ago
|
