searxng/tests/unit/test_answerers.py

# SPDX-License-Identifier: AGPL-3.0-or-later
# pylint: disable=missing-module-docstring

from mock import Mock
from parameterized import parameterized

from searx.answerers import answerers
from tests import SearxTestCase


class AnswererTest(SearxTestCase):  # pylint: disable=missing-class-docstring
    @parameterized.expand(answerers)
    def test_unicode_input(self, answerer):
        query = Mock()
        unicode_payload = 'árvíztűrő tükörfúrógép'
        query.query = '{} {}'.format(answerer.keywords[0], unicode_payload)
        self.assertIsInstance(answerer.answer(query), list)
[mod] pylint all files with one profile / drop PYLINT_SEARXNG_DISABLE_OPTION In the past, some files were tested with the standard profile, others with a profile in which most of the messages were switched off ... some files were not checked at all. - ``PYLINT_SEARXNG_DISABLE_OPTION`` has been abolished - the distinction ``# lint: pylint`` is no longer necessary - the pylint tasks have been reduced from three to two 1. ./searx/engines -> lint engines with additional builtins 2. ./searx ./searxng_extra ./tests -> lint all other python files Signed-off-by: Markus Heiser <markus.heiser@darmarit.de> 2024-03-11 14:06:26 +01:00			`# SPDX-License-Identifier: AGPL-3.0-or-later`
			`# pylint: disable=missing-module-docstring`
[enh] add quick answer functionality with an example answerer 2016-11-19 20:53:51 +01:00
			`from mock import Mock`
[refactor] unit tests to utilize paramaterized and break down monolithic tests - for tests which perform the same arrange/act/assert pattern but with different data, the data portion has been moved to the ``paramaterized.expand`` fields - for monolithic tests which performed multiple arrange/act/asserts, they have been broken up into different unit tests. - when possible, change generic assert statements to more concise asserts (i.e. ``assertIsNone``) This work ultimately is focused on creating smaller and more concise tests. While paramaterized may make adding new configurations for existing tests easier, that is just a beneficial side effect. The main benefit is that smaller tests are easier to reason about, meaning they are easier to debug when they start failing. This improves the developer experience in debugging what went wrong when refactoring the project. Total number of tests went from 192 -> 259; or, broke apart larger tests into 69 more concise ones. 2024-09-24 05:37:30 +02:00			`from parameterized import parameterized`
[enh] add quick answer functionality with an example answerer 2016-11-19 20:53:51 +01:00
			`from searx.answerers import answerers`
[mod] move searx/testing.py to the tests directory move robot tests to tests.robot manage calls "python -m tests.robot" 2021-09-02 16:01:34 +02:00			`from tests import SearxTestCase`
[enh] add quick answer functionality with an example answerer 2016-11-19 20:53:51 +01:00

[mod] pylint all files with one profile / drop PYLINT_SEARXNG_DISABLE_OPTION In the past, some files were tested with the standard profile, others with a profile in which most of the messages were switched off ... some files were not checked at all. - ``PYLINT_SEARXNG_DISABLE_OPTION`` has been abolished - the distinction ``# lint: pylint`` is no longer necessary - the pylint tasks have been reduced from three to two 1. ./searx/engines -> lint engines with additional builtins 2. ./searx ./searxng_extra ./tests -> lint all other python files Signed-off-by: Markus Heiser <markus.heiser@darmarit.de> 2024-03-11 14:06:26 +01:00			`class AnswererTest(SearxTestCase): # pylint: disable=missing-class-docstring`
[refactor] unit tests to utilize paramaterized and break down monolithic tests - for tests which perform the same arrange/act/assert pattern but with different data, the data portion has been moved to the ``paramaterized.expand`` fields - for monolithic tests which performed multiple arrange/act/asserts, they have been broken up into different unit tests. - when possible, change generic assert statements to more concise asserts (i.e. ``assertIsNone``) This work ultimately is focused on creating smaller and more concise tests. While paramaterized may make adding new configurations for existing tests easier, that is just a beneficial side effect. The main benefit is that smaller tests are easier to reason about, meaning they are easier to debug when they start failing. This improves the developer experience in debugging what went wrong when refactoring the project. Total number of tests went from 192 -> 259; or, broke apart larger tests into 69 more concise ones. 2024-09-24 05:37:30 +02:00			`@parameterized.expand(answerers)`
			`def test_unicode_input(self, answerer):`
[enh] add quick answer functionality with an example answerer 2016-11-19 20:53:51 +01:00			`query = Mock()`
Drop Python 2 (1/n): remove unicode string and url_utils 2020-08-06 17:42:46 +02:00			`unicode_payload = 'árvíztűrő tükörfúrógép'`
[refactor] unit tests to utilize paramaterized and break down monolithic tests - for tests which perform the same arrange/act/assert pattern but with different data, the data portion has been moved to the ``paramaterized.expand`` fields - for monolithic tests which performed multiple arrange/act/asserts, they have been broken up into different unit tests. - when possible, change generic assert statements to more concise asserts (i.e. ``assertIsNone``) This work ultimately is focused on creating smaller and more concise tests. While paramaterized may make adding new configurations for existing tests easier, that is just a beneficial side effect. The main benefit is that smaller tests are easier to reason about, meaning they are easier to debug when they start failing. This improves the developer experience in debugging what went wrong when refactoring the project. Total number of tests went from 192 -> 259; or, broke apart larger tests into 69 more concise ones. 2024-09-24 05:37:30 +02:00			`query.query = '{} {}'.format(answerer.keywords[0], unicode_payload)`
			`self.assertIsInstance(answerer.answer(query), list)`