David Winslow wrote: > Hi all, > > Recently I was writing some tests and needed to check the HTTP status > code for some requests. In doing so I started out trying to reuse code > from the ows module's tests, but found that it used > com.mockobjects.servlet.MockHttpServletResponse while my tests (and > GeoServerAbstractTestSupport) are using > com.mockrunner.http.HttpServletResponse . I've already worked around > this, but I wonder whether it would be useful to unify the tests around > a single mock framework. Is there any reason to be using both of these?
Hmmm... probably just a result of my sillyness :). Yeah I definitely would like to just use one framework if we can. Any idea how much work it will be to reconcile them? > > (By the way, if anyone else needs to check status codes there are > assertions in GeoServerAbstractTestSupport for that now, just do: > assertStatusCodeForGet(200, "welcome.do"); > assertStatusCodeForPost(500, "ows", "this isn't xml!", "text/xml"); > assertStatusCodeForPut(501, "welcome.do", "GeoServer homepage", > "text/plain"); > etc.) Nice :). > > -David Winslow > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > !DSPAM:4007,484fd28310591637810514! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
