Files
mediawiki-extensions-Univer…/tests/browser/features/textarea_font.feature
Antoine Musso 9fa4b32c08 browsertests: profile for default settings
Some scenarii are meant to be tested on specific wiki instances such as
commmons.beta.wmflabs.org or sandbox.translatewiki.net. For the Gerrit
integration, we are using a fresh wiki having the default ULS settings,
hence the specific tests will definitely fail.

This patch introduces a new cucumber tag `@needs-custom-setup`, it is
meant to flag tests which require further configuration tweaking, for
example tests explicitly targetting an already existing wiki such as
beta or translatewiki

I am introducing a new cucumber profile 'ciwmf' which exclude any test
tagged '@needs-custom-setup' or '@phantomjs-bug'.  That profile is going
to be used by the Jenkins/Gerrit install using something like:

  cucumber -p ciwmf

equivalent to:

  cucumber -t '~@phantomjs-bug' -t '~@needs-custom-setup'

Marked some tests as being bugged on phantomjs:
* autonym ones because of bug 57101 "browser tests must normalize
  font-family".
* accept_language since we dont have yet a way to pass the accept
  language header via phantomjs.
* Commented out an 'input method is visible' test with Vector + Hebrew
  since it does not pass.
* Malayalam link is looked by title which is translated by default.

This patch is passing on my local wiki, albeit skipping a lot of steps.

Change-Id: Ib055f5470886e1b818d4c53cb4c61a751d81e154
2013-12-05 11:35:35 +01:00

50 lines
2.5 KiB
Gherkin

@login
Feature: Font preferences respected in different languages
If a user has an edit font preferences respect that preference.
If a user has no edit font preference, but the UI language has a monospace defined,
the edit area has monospace font, given there is no ULS webfont preference for the user.
If a user has no edit font preference, but the UI language has no monospace defined,
the edit area has the font according to the ULS webfont preferences.
Background:
Given I am logged in
And I have reset my preferences
@commons.wikimedia.beta.wmflabs.org
Scenario: Edit area fonts should not change on UI language change if the user preferences for edit area font are set
When I set the editing fonts to "monospace"
And I set "Hindi" as the interface language
And I start editing a page
Then I should see the edit area text being displayed using "monospace" font
# Needs OpenDyslexic font to have been configured on the target wiki
@needs-custom-setup @commons.wikimedia.beta.wmflabs.org
Scenario: Edit area should use the fonts selected by the user from ULS for a language
When I select OpenDyslexic font for the content language
And I start editing a page
Then I should see the edit area text being displayed using "OpenDyslexic" font
Scenario: Edit area should use the ULS selected fonts when content language has a ULS font selection
When I open "Language" panel of language settings
And I click the button with the ellipsis
And I use the panel to change my interface language to "German"
And I open "Fonts" panel of language settings
And I select "OpenDyslexic" font for the content language for the live preview
And I apply the changes
And I start editing a page
Then I should see the edit area text being displayed using "OpenDyslexic" font
Scenario: Edit area should use the system default fonts when content language does not have any ULS font selection
When I open "Language" panel of language settings
And I click the button with the ellipsis
And I use the panel to change my interface language to "German"
And I apply the changes
And I start editing a page
Then I should see the edit area text being displayed using "monospace" font
@phantomjs-bug
Scenario: Edit area should use browser's default Monospace font for languages that have a default monospace font (Latin, Cyrillic, Hebrew etc.)
When I start editing a page
Then I should see the edit area text being displayed using "monospace" font