Page MenuHomePhabricator

Create an initial set of API integration tests using variables (part 1)
Closed, ResolvedPublic

Description

Without support for variables in phester, these tests have to be written "dry", with no way to execute them.

  • watchlist (watch/unwatch/auto-watch)
  • bot edits (interaction of bot permission and bot parameter)
  • rollback
  • patrolling, patrol log
  • listing user contributions
  • page deletion/undeletion (effectiveness)
  • user blocking (effectiveness, various options)
  • user script protection (can only edit own)
  • minor edits
  • remaining core magic words (in particular REVISIONID and friends)
  • Special pages transclusion
  • media file uploads (need to be enabled on the wiki) (needs file upload support in phester)

These tests will be written for our own runner (phester) and some tests for some of the other candidates, like strest, tavern, behat, codeception, or dredd.

Tests to be written in other frameworks:

Acceptance criteria: at least half of the tests have been written using Phester and at least two of them have been written in at least two other frameworks.

Event Timeline

CCicalese_WMF renamed this task from Create a set of API integration tests using variables to Create an initial set of API integration tests using variables.Jul 15 2019, 8:37 PM
CCicalese_WMF renamed this task from Create an initial set of API integration tests using variables to Create an initial set of API integration tests using variables (part 1).Jul 17 2019, 6:25 PM
CCicalese_WMF assigned this task to daniel.

@daniel hey,. thanks for updating… just left this comment for Clara too:

Would you mind also creating a list for each additional framework you intend to test? (At says at least 2 but I'm not sure which ones you are doing and how many you think you will do)

@daniel whoops! you already did that… nm and thanks!

I tried to write a test in strest. It's next to impossible due to the lack of support for session contexts. We'd have to permanently log in and log out in order to write tests that involve multiple users. That's a show stopper.

CCicalese_WMF changed the task status from Invalid to Resolved.Aug 12 2019, 7:34 PM