Bug 577538: Mark certain tests in xt/search.t as being broken only on Pg

(and a few as being not broken at all on Pg).
r=mkanat, a=mkanat (module owner)

1 files changed, 24 insertions, 0 deletions

diff --git a/xt/lib/Bugzilla/Test/Search/Constants.pm b/xt/lib/Bugzilla/Test/Search/Constants.pm
index 28f0a3f93..c9d2ef088 100644
--- a/xt/lib/Bugzilla/Test/Search/Constants.pm
+++ b/xt/lib/Bugzilla/Test/Search/Constants.pm
@@ -45,6 +45,7 @@ our @EXPORT = qw(
     NUM_SEARCH_TESTS
     OR_BROKEN
     OR_SKIP
+    PG_BROKEN
     SKIP_FIELDS
     SUBSTR_SIZE
     TESTS
@@ -482,6 +483,29 @@ use constant KNOWN_BROKEN => {
     },
 };
 
+# This tracks things that are broken in different ways on Pg compared to
+# MySQL. Actually, in some of these cases, Pg is behaving correctly
+# where MySQL isn't, but the result is still a bit surprising to the user.
+use constant PG_BROKEN => {
+    'attach_data.thedata' => {
+        allwords       => { },
+        allwordssubstr => { },
+        anywords       => { },
+        notregexp      => { contains => [5] },
+        nowords        => { contains => [5] },
+    },
+    percentage_complete => {
+        'allwordssubstr-<1>' => { contains => [3] },
+        anywordssubstr  => { contains => [2,3] },
+        casesubstring   => { contains => [3] },
+        'notregexp-<1>' => { contains => [3] },
+        notsubstring    => { contains => [3] },
+        nowordssubstr   => { contains => [3] },
+        'regexp-<1>'    => { contains => [3] },
+        substring       => { contains => [3] },
+    },
+};
+
 #############
 # Overrides #
 #############