Core Platform Team/Initiative/Add API integration tests/Description/stories

API use cases ("user stories") that should have end-to-end tests.

Permission Enforcement

 * A blocked user tries to edit -> should fail with appropriate message
 * A blocked user tries to their own talk page -> should not fail, unless explicitly forbidden
 * A blocked user tries to log out and then edit -> should fail with appropriate message.
 * Note: The resulting auto-block needs to be cleaned up so that subsequent tests can edit.
 * A blocked user tried to log out and create a new account -> should fail unless explicitly allowed.
 * A (non blocked) user tries to edit from a blocked IP -> should fail or be allowed, depending on the block.
 * A user without sufficient rights tries to edit a protected page
 * A user without sufficient rights tries to edit a page in a protected namespace
 * A user without sufficient rights tries to grant user permissions
 * A user without sufficient rights tries to delete a page
 * A user without sufficient rights tries to move a page
 * A user without sufficient rights tries to create a page
 * A user without sufficient rights tries to access suppressed page content
 * A user with sufficient rights edits a protected page
 * A user with sufficient rights edits a page in a protected namespace
 * A user with sufficient rights accesses suppressed page content

Revision Tags

 * A bot edit gets flagged as such if the user is in the bot group and requests the flag to be set, not otherwise
 * A revert gets flagged as such
 * New revisions get flagged as autopatrolled if the user has the necessary permissions.