aboutsummaryrefslogtreecommitdiffstats
path: root/tests/phpunit/unit/includes/ListToggleTest.php
Commit message (Collapse)AuthorAgeFilesLines
* tests: Move test cases from /includes/ into sub folderUmherirrender2023-09-131-55/+0
| | | | | | | Follow move of the tested class Most moves are part of T321882 Change-Id: I74ab45d6a5331dcb2ff0b65dc2cc7c6315146646
* Reorg: Move three output related classes to includes/Output/Amir Sarabadani2023-09-051-0/+1
| | | | | | | | | | And namesapce them: - StreamFile - OutputHandler - OutputPage Bug: T321882 Change-Id: Iedf8d88c595e580f2d8f0734c92aa5c45618ba33
* phpunit: Update `@covers` annotations for namespaced classesFunc2023-05-271-3/+3
| | | | | | | | | | | | We renamed many classes to be namespaced, but the `@covers` and `@coversDefaultClass` annotations weren't updated properly. PHPUnit didn't support short cover annotations with `use` statements, these didn't trigger any errors yet, because they are class alias. This patch is populated by a modified version of PhpunitAnnotationsSniff. Change-Id: I6c602290a30099239b17d2dc0d67b1488b4eaeeb
* A fake MessageLocalizer for use in unit testsMichael Große2023-03-151-22/+2
| | | | | | | | | | | | The existing MockMessageLocalizer can't be used in unit tests because it uses real Message objects that make a number of database calls via services. Codewise, this is based on \ListToggleTest::testGetHTML and \EntitySchema\MediaWiki\SpecificLanguageMessageLocalizer. It came out from the conversation on I4122bc8b2 Change-Id: I5297e4c43495b7e959798a21929f6d24d0b4b466
* Reorg: Move HTML-related classes out of includes/ to Html/Amir Sarabadani2023-02-161-0/+2
| | | | | Bug: T321882 Change-Id: I5dc1f7e9c303cd3f5b9dd7010d6bb470d8400a18
* Tests: Cleanup some unnecessary nested function callsReedy2022-06-061-2/+2
| | | | | | Replace ->will( ->return with ->willReturn( Change-Id: Ia2dfafa03cac8169d86d6fa5a30b73bfad1fe9fa
* Only apply transformations for &uselang=qqx when actually using itBartosz Dziewoński2022-03-081-0/+11
| | | | | | | | Depends-On: I4f3b01eccf571475f1248db838a8aa6cba18b93e Depends-On: I0a0681b332abb623fc6871ab78da9e64a79fad84 Bug: T300069 Bug: T302469 Change-Id: I45f58034117e9041fe5403dbfcf83ba25f20518d
* Remove meaningless ->expects( $this->any() ) from all testsThiemo Kreuz2021-04-231-2/+1
| | | | | | | | | | | | | | | It is not entirely meaningless. It might be an indicator that the number of calls to a method is intentionally unlimited. This is similar to e.g. an @inheritDoc PHPDoc comment that marks a method as being "intentionally undocumented". However, what's the meaning of being "intentionally unconstrained"? Let's just not have any constraint then. I feel all these ->expects( $this->any() ) bloat the test code so much that it's never worth it. Change-Id: I9925e7706bd03e1666f6eb0b284cb42b0dd3be23
* Make ListToggleTest a pure unit testDannyS7122021-03-121-0/+62
| | | | | | | Use mocks to avoid dealing with the Message object handling Change-Id: I458cfe6ebffcc80b0b07ff1f032dced69d500993
* Revert "Separate MediaWiki unit and integration tests"Legoktm2019-06-131-49/+0
| | | | | | | | This reverts commit 0a2b996278e57a8b8c5377cd3a3eaa54f993d4a9. Reason for revert: Broke postgres tests. Change-Id: I27d8e0c807ad5f0748b9611a4f3df84cc213fbe1
* Separate MediaWiki unit and integration testsMáté Szabó2019-06-131-0/+49
This changeset implements T89432 and related tickets and is based on exploration done at the Prague Hackathon. The goal is to identify tests in MediaWiki core that can be run without having to install & configure MediaWiki and its dependencies, and provide a way to execute these tests via the standard phpunit entry point, allowing for faster development and integration with existing tooling like IDEs. The initial set of tests that met these criteria were identified using the work Amir did in I88822667693d9e00ac3d4639c87bc24e5083e5e8. These tests were then moved into a new subdirectory under phpunit/ and organized into a separate test suite. The environment for this suite is set up via a PHPUnit bootstrap file without a custom entry point. You can execute these tests by running: $ vendor/bin/phpunit -d memory_limit=512M -c tests/phpunit/unit-tests.xml Bug: T89432 Bug: T87781 Bug: T84948 Change-Id: Iad01033a0548afd4d2a6f2c1ef6fcc9debf72c0d