MD Settings: Migrate enable-translation toggle from non-MD settings page.

chrome/test/data/webui/settings/languages_page_browsertest.js

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 /** @fileoverview Suite of tests for settings-languages-page. */
 
 /** @const {string} Path to root from chrome/test/data/webui/settings/. */
 var ROOT_PATH = '../../../../../';
 
 // Polymer BrowserTest fixture.
@@ skipping 217 matching lines @@
         assertEquals(1, separator.offsetHeight);
 
         // Disable Translate. On platforms that can't change the UI language,
         // this hides all the checkboxes, so the separator isn't needed.
         // Chrome OS and Windows still show a checkbox and thus the separator.
         languageHelper.setPrefValue('translate.enabled', false);
         assertEquals(
             cr.isChromeOS || cr.isWindows ? 1 : 0, separator.offsetHeight);
       });
 
+      test('test enable translation toggle', function() {
+        var toggle = languagesPage.$.offerTranslateOtherLangs;

[michaelpg, 2017/01/31 21:54:10]

this assumes translate is already enabled. we should first set the pref (see the
test below).

[scottchen, 2017/02/01 01:02:39]

The button that this line is grabbing is the toggle to enable/disable
prefs.translate.enabled itself, which should always exist and be visible on the
page. In which case, setting the pref is not necessary, since all the test
should care about is translate.enabled is different from the initial value after
being clicked.

I think you might be thinking of a different button that only exists in the
overflow menu if translate.enabled = true (i.e. the button that is being tested
in the test below). 

[michaelpg, 2017/02/01 01:50:02]

origTranslateEnabled is used to ensure the value gets reset to the default when
we leave this test suite. It's only set once, so relying on it within a test is
fragile. If we were to change or swap some tests, the value might be different
than origTranslateEnabled when we get to this test. That's why I suggest setting
the pref first, or at least querying for the current value of the pref, before
testing the toggle.

[scottchen, 2017/02/01 02:04:31]

The test would be valid regardless of origTranslateEnabled's initial value,
because all it checks is whether or not the value is flipped. (new value != old
value); it doesn't actually check if the value is truthy or falsey, so even if
we query the current value, we'd still be testing for "new value != old value"
anyway - so I'm not sure how it'll make a difference.
(See the assertEquals line below).

So if we query for the current value, we'd be doing:

var curValue = origTranslateEnabled;
... //flip the toggle
assertEquals(!curValue, newTranslateEnabled);

which would be exactly the same as the current code, just with one extra
proxy-variable.

[michaelpg, 2017/02/01 02:57:15]

I was playing with this test to try to show what I mean, but it's behaving
weirdly. MockInteractions.tap(toggle) doesn't appear to be actually changing the
state of the toggle.

Which would explain why we're not seeing the failure I expect here.

[scottchen, 2017/02/01 18:52:35]

Acknowledged. Please see newest patch.

+        assertTrue(!!toggle);
+        MockInteractions.tap(toggle);
+        var newTranslateEnabled = languageHelper.prefs.translate.enabled.value;
+        assertEquals(!origTranslateEnabled, newTranslateEnabled);

[michaelpg, 2017/01/31 21:54:10]

can you also test that disabling the toggle button hides the menu option in a
language's dropdown? (again see test below for set-up)

[scottchen, 2017/02/01 01:02:38]

Do you mean disabling the toggle button as in <settings-toggle-button disabled>,
or do you mean disabling translation (i.e. translate.enabled = false)?

I don't think <settings-toggle-button disabled> should impact whether the menu
option show up either way, and currently there's no condition in which the
toggle would be disabled.

If you mean the latter, I agree we should test for that :) I'll add a new test
though, since it seems like a separate concern than what we're testing for here.

[michaelpg, 2017/02/01 01:50:02]

Sorry, yes, if we "uncheck" the toggle button to turn off translate
(translate.enabled = false). Thanks.

+      });
+
       test('toggle translate', function(done) {

[michaelpg, 2017/01/31 21:54:10]

change title to something like 'toggle translate for a specific language' since
it's ambiguous now

[scottchen, 2017/02/01 01:02:39]

Done.

         // Enable Translate so the menu always shows the Translate checkbox.
         languageHelper.setPrefValue('translate.enabled', true);
         languagesPage.set('languages.translateTarget', 'foo');
         languagesPage.set('languages.enabled.1.supportsTranslate', true);
 
         var languageOptionsDropdownTrigger =
             languagesCollapse.querySelectorAll('paper-icon-button')[1];
         assertTrue(!!languageOptionsDropdownTrigger);
         MockInteractions.tap(languageOptionsDropdownTrigger);
         assertTrue(actionMenu.open);
@@ skipping 99 matching lines @@
         assertTrue(!!languagesPage.$$('settings-edit-dictionary-page'));
       }
     });
   }.bind(this));
 
   // TODO(michaelpg): Test more aspects of the languages UI.
 
   // Run all registered tests.
   mocha.run();
 });