[Rt-commit] rt branch, 4.0/rest-string-eval, updated. rt-4.0.0-278-g662bde0

Alex Vandiver alexmv at bestpractical.com
Thu Jul 28 14:49:04 EDT 2011


The branch, 4.0/rest-string-eval has been updated
       via  662bde0eb24e97780f691e99f80902eeb9ab6ca1 (commit)
      from  17988e6b5c626f2d530826974d5d9af840f8cae8 (commit)

Summary of changes:
 t/web/rest-sort.t |   47 -----------------------------------------------
 1 files changed, 0 insertions(+), 47 deletions(-)

- Log -----------------------------------------------------------------
commit 662bde0eb24e97780f691e99f80902eeb9ab6ca1
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Thu Jul 28 14:48:56 2011 -0400

    Remove inaccessible code copied from t/web/rest.t

diff --git a/t/web/rest-sort.t b/t/web/rest-sort.t
index a759e9d..75439e1 100644
--- a/t/web/rest-sort.t
+++ b/t/web/rest-sort.t
@@ -44,50 +44,3 @@ sub sorted_tickets_ok {
 
     is_deeply(\@lines, $expected, "sorted results by '$order'");
 }
-
-__END__
-
-$m->post("$baseurl/REST/1.0/ticket/new", [
-    format  => 'l',
-]);
-
-my $text = $m->content;
-my @lines = $text =~ m{.*}g;
-shift @lines; # header
-
-# CFs aren't in the default ticket form
-push @lines, "CF-fu()n:k/: maximum"; # old style
-push @lines, "CF.{severity}: explosive"; # new style
-
-$text = join "\n", @lines;
-
-ok($text =~ s/Subject:\s*$/Subject: REST interface/m, "successfully replaced subject");
-
-$m->post("$baseurl/REST/1.0/ticket/edit", [
-    content => $text,
-], Content_Type => 'form-data');
-
-my ($id) = $m->content =~ /Ticket (\d+) created/;
-ok($id, "got ticket #$id");
-
-my $ticket = RT::Ticket->new(RT->SystemUser);
-$ticket->Load($id);
-is($ticket->Id, $id, "loaded the REST-created ticket");
-is($ticket->Subject, "REST interface", "subject successfully set");
-is($ticket->FirstCustomFieldValue("fu()n:k/"), "maximum", "CF successfully set");
-
-$m->post("$baseurl/REST/1.0/search/ticket", [
-    query   => "id=$id",
-    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",
-     "CF.{fu()n:k/}: maximum",
-     "CF.{severity}: explosive",
-     "Status: new") {
-        $m->content_contains($_);
-}
-

-----------------------------------------------------------------------


More information about the Rt-commit mailing list