MediaWiki REL1_32
ApiTokensTest.php
Go to the documentation of this file.
1<?php
2
10class ApiTokensTest extends ApiTestCase {
11
12 public function testGettingToken() {
13 foreach ( self::$users as $user ) {
14 $this->runTokenTest( $user );
15 }
16 }
17
18 protected function runTokenTest( TestUser $user ) {
19 $tokens = $this->getTokenList( $user );
20
21 $rights = $user->getUser()->getRights();
22
23 $this->assertArrayHasKey( 'edittoken', $tokens );
24 $this->assertArrayHasKey( 'movetoken', $tokens );
25
26 if ( isset( $rights['delete'] ) ) {
27 $this->assertArrayHasKey( 'deletetoken', $tokens );
28 }
29
30 if ( isset( $rights['block'] ) ) {
31 $this->assertArrayHasKey( 'blocktoken', $tokens );
32 $this->assertArrayHasKey( 'unblocktoken', $tokens );
33 }
34
35 if ( isset( $rights['protect'] ) ) {
36 $this->assertArrayHasKey( 'protecttoken', $tokens );
37 }
38 }
39
40}
ApiTestCase\getTokenList
getTokenList(TestUser $user, $session=null)
Definition ApiTestCase.php:164
ApiTokensTest
API Database medium.
Definition ApiTokensTest.php:10
ApiTokensTest\runTokenTest
runTokenTest(TestUser $user)
Definition ApiTokensTest.php:18
TestUser
Wraps the user object, so we can also retain full access to properties like password if we log in via...
Definition TestUser.php:9
as
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such as
Definition distributors.txt:22
$user
please add to it if you re going to add events to the MediaWiki code where normally authentication against an external auth plugin would be creating a local account $user
Definition hooks.txt:247
php
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
Definition injection.txt:37
$tokens
$tokens
Definition mwdoc-filter.php:47