Flow: logged_in browser test assumes block user right
Open, LowPublic
Actions

Assigned To

None

Authored By

	• Spage
	Feb 22 2014, 8:59 AM

Description

Scenario: Block looks for a "Block User link", but by default only sysops have that.

We could

Add that right to the qa_automation config as we did for bug 58375 in gerrit I7523c867b12
Disable the test on test2wiki and other wikis with the @symbols annotation
Remove the test altogether (gerrit 114172)

Version: master
Severity: normal

• bzimport raised the priority of this task from to Low.Nov 22 2014, 3:04 AM

• bzimport set Reference to bz61799.

• bzimport added a subscriber: Unknown Object (MLST).

Change 114172 had a related patch set uploaded by Spage:
Don't check for 'Block', only very privileged users will have this

Change 114172 merged by jenkins-bot:
Don't check for 'Block', only very privileged users will have this

gerrit Icd3fec2341f26a5a reintroduced a Block check when it changed a Scenario to

Scenario: Add new Flow topic and show author and block links

, so flow_logged_in.feature is again failing on test2.wikipedia.org.

We could skip that scenario on test2wiki, or add

'block' => true

to the 'qa_automation' group on test2wiki, similar to gerrit I7523c867b12.