[Rt-commit] r15522 - in rt/branches/3.999-DANGEROUS: t/web

[sunnavy at bestpractical.com]

Author: sunnavy
Date: Wed Aug 27 09:39:12 2008
New Revision: 15522

Modified:
   rt/branches/3.999-DANGEROUS/   (props changed)
   rt/branches/3.999-DANGEROUS/t/web/rest.t

Log:
 r16158 at sunnavys-mb:  sunnavy | 2008-08-27 21:32:47 +0800
 name fixes for t/web/rest.t


Modified: rt/branches/3.999-DANGEROUS/t/web/rest.t
==============================================================================
--- rt/branches/3.999-DANGEROUS/t/web/rest.t	(original)
+++ rt/branches/3.999-DANGEROUS/t/web/rest.t	Wed Aug 27 09:39:12 2008
@@ -35,7 +35,7 @@
 
 $text = join "\n", @lines;
 
-ok($text =~ s/Subject:\s*$/Subject: REST interface/m, "successfully replaced subject");
+ok($text =~ s/subject:\s*$/subject: REST interface/m, "successfully replaced subject");
 
 $m->post("$baseurl/REST/1.0/ticket/edit", [
     user    => 'root',
@@ -57,16 +57,16 @@
     user    => 'root',
     pass    => 'password',
     query   => "id=$id",
-    fields  => "Subject,CF-fu()n:k/,CF.{severity},Status",
+    fields  => "subject,CF-fu()n:k/,CF.{severity},status",
 ]);
 
 # the fields are interpreted server-side a hash (why?), so we can't depend
 # on order
 for ("id: ticket/1",
-     "Subject: REST interface",
+     "subject: REST interface",
      "CF.{fu()n:k/}: maximum",
      "CF.{severity}: explosive",
-     "Status: new") {
+     "status: new") {
         $m->content_contains($_);
 }