Grant Lanham 44a06190bb [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-10-03 13:20:32 +02:00
..
robot	[mod] pylint all files with one profile / drop PYLINT_SEARXNG_DISABLE_OPTION	2024-03-11 14:55:38 +01:00
unit	[refactor] unit tests to utilize paramaterized and break down monolithic tests	2024-10-03 13:20:32 +02:00
__init__.py	[mod] pylint all files with one profile / drop PYLINT_SEARXNG_DISABLE_OPTION	2024-03-11 14:55:38 +01:00