624892 - Mozmill test for Panorama tab search filter

Status: RESOLVED WONTFIX

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Description

[Clay Earl Uyenghua]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Build Identifier: 

Create new automation test for testcase id #12845. Testing the tab search filter of the TabView.

https://litmus.mozilla.org/show_test.cgi?id=12845

Reproducible: Always

Steps to Reproduce:
1. Open several tabs
2. enter group view
3. press the search button
4. type two or more letters, test matching and non-matching results


Expected Results:  
1. The search should highlight any open tabs that match the search
2. Tabs that don't match the search should not be highlighted

Comment 1

[Clay Earl Uyenghua]

Attachment: Automation script for testcase 12845

I have attached the automation script for review.

In this script it contains three texts to search. Search for a single letter which should not highlight any tabs, two letters that matches tabs which should highlight tabs matched and a word which should not match and should not highlight any tabs.

Comment 2

[Clay Earl Uyenghua]

Attachment: Automation script for testcase 12845

Comment 3

[Clay Earl Uyenghua]

Attachment: Automation script for testcase 12845

Changed module variables to capital letters and changed assert() calls to waitFor().

Comment 4

[u279076]

Comment on attachment 503068 [details] [diff] [review]
Automation script for testcase 12845

>diff --git a/firefox/testTabView/testTabSearchFilter.js b/firefox/testTabView/testTabSearchFilter.js
>+function teardownModule() {
>+}

Make sure you include the module parameter.

>+  LOCAL_TEST_PAGES.forEach(function (page) {
>+    controller.open(page.url);

url should be URL as it is an acronym.

>+
>+    // Check that tabs only gets highlighted when expected to match
>+    controller.waitFor(function () {
>+      return wordMatched === searchWord.match;
>+    }, null, null, "Unexpected result for search");

Can you update the error message to include "got" and "expected"?

Comment 5

[Clay Earl Uyenghua]

Attachment: Automation script for testcase 12845 revision 1

Implemented required changes.

Comment 6

[u279076]

Comment on attachment 504931 [details] [diff] [review]
Automation script for testcase 12845 revision 1

>diff --git a/firefox/testTabView/testTabSearchFilter.js b/firefox/testTabView/testTabSearchFilter.js
>+    // Check if there is a tab highlighted that matched to search
>+    var wordMatched = false;
>+    tabs.forEach(function (tabItem) {
>+      if( tabItem.getNode().classList.contains(TAB_HIGHLIGHTED) ) {
>+        wordMatched = true;
>+      }
>+    });
>+
>+    // Check that tabs only gets highlighted when expected to match
>+    controller.waitFor(function () {
>+      return wordMatched === searchWord.match;
>+    }, "Unexpected result for search - got " + wordMatched + ", expected "
>+    + searchWord.match);

I'm wondering if we couldn't simplify this by combining the two.  In other words, do the waitFor() inside the forEach() without using wordMatched.  Please see if you can refactor this.

Comment 7

[Clay Earl Uyenghua]

Attachment: Automation script for testcase 12845 revision 2

I have revised the script and placed waitFor inside the forEach loop.

Comment 8

[u279076]

Comment on attachment 509676 [details] [diff] [review]
Automation script for testcase 12845 revision 2

>+const SEARCH_WORDS = [
>+  {word: "!allizoM", match: [false,false,false,false,false]},
>+  {word: "moz", match: [true,true,true,true,false]},
>+  {word: "m", match: [false,false,false,false,false]}
>+];

Why is match an array of FALSE instead of just a single false?

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Bug 836758 will remove Panorama from Firefox soon and make it available as add-on. That means no new tests are necessary. Closing as WONTFIX.