#1114: Rename AgaviViewTestCase Assertions to something more explicit
-------------------------+--------------------------------------------------
 Reporter:  felix        |        Owner:  felix 
     Type:  enhancement  |       Status:  closed
 Priority:  normal       |    Milestone:        
Component:  testing      |      Version:  1.0.1 
 Severity:  normal       |   Resolution:  fixed 
 Keywords:               |    Has_patch:  0     
-------------------------+--------------------------------------------------
Changes (by felix):

  * status:  assigned => closed
  * resolution:  => fixed


Comment:

 (In [4160]) - Renamed assertions in the View to better reflect their
 scope.

 * assertResponseHasRedirect => assertViewRedirects
 * assertResponseHasNoRedirect => assertViewRedirectsNot
 * assertResponseRedirectsTo => assertViewRedirectsTo
 * assertResponseHasContentType => assertViewSetsContentType
 * assertResponseHasHeader => assertViewSetsHeader
 * assertResponseHasCookie => assertViewSetsCookie
 * assertResponseHasHTTPStatus => assertViewResponseHasHTTPStatus
 * assertResponseHasContent => assertViewResponseHasContent
 * assertForwards => assertViewForwards

 - Changed the unit tests accordingly.
 - Made the message in assertHasLayer() configurable by the user

 fixes #1114

-- 
Ticket URL: <http://trac.agavi.org/ticket/1114#comment:2>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5


_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets

Reply via email to