mediawiki-extensions-Echo/tests/phpunit/Api/Push/ApiEchoPushSubscriptionsTest.php

<?php

use MediaWiki\Tests\Api\ApiTestCase;

/**
 * @group medium
 * @group API
 * @covers \MediaWiki\Extension\Notifications\Push\Api\ApiEchoPushSubscriptions
 */
class ApiEchoPushSubscriptionsTest extends ApiTestCase {

	public function testRequiresToken(): void {
		$this->setMwGlobals( 'wgEchoEnablePush', true );
		$params = [
			'action' => 'echopushsubscriptions',
			'command' => 'create',
			'platform' => 'apns',
			'platformtoken' => 'ABC123',
		];
		$this->expectException( ApiUsageException::class );
		$this->doApiRequest( $params );
	}

}
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62 2020-05-15 17:19:03 +00:00			`<?php`

Use namespaced classes Changes to the use statements done automatically via script Addition of missing use statement done manually Change-Id: I3d7a1ffe167b69d3f4ce51d0c248c758e1cdd70c 2024-06-12 18:31:47 +00:00			`use MediaWiki\Tests\Api\ApiTestCase;`

Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62 2020-05-15 17:19:03 +00:00			`/**`
			`* @group medium`
			`* @group API`
Move EchoPush\Api namespace to MediaWiki\Extension\Notifications\Push\Api Bug: T305667 Change-Id: I6168b386f532c83333cdc6700ba7e2917385a39c 2022-04-08 00:47:34 +00:00			`* @covers \MediaWiki\Extension\Notifications\Push\Api\ApiEchoPushSubscriptions`
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62 2020-05-15 17:19:03 +00:00			`*/`
			`class ApiEchoPushSubscriptionsTest extends ApiTestCase {`

			`public function testRequiresToken(): void {`
			`$this->setMwGlobals( 'wgEchoEnablePush', true );`
			`$params = [`
			`'action' => 'echopushsubscriptions',`
			`'command' => 'create',`
			`'platform' => 'apns',`
			`'platformtoken' => 'ABC123',`
			`];`
			`$this->expectException( ApiUsageException::class );`
			`$this->doApiRequest( $params );`
			`}`

			`}`