schul_cloud_search_tests
These are the tests for the Schul-Cloud search API. You can read motivation blog post about
common tests for all search engines
testing during live deployment
Installation
You can install the tests by installing Python version 3 and pip. Then, you run the installation from the command line:
pip install --user schul-cloud-search-testsInstallation for Development
If you would like to contribute code to this repository, you can clone it first.
git clone https://github.com/schul-cloud/schul_cloud_search_tests.git
cd schul_cloud_search_testsInstall the required packages for Python:
pip3 install --user -r requirements.txt pip-tools==1.6.5Note that if you would like to change the requirements, please edit the requirements.in file and run this command to update the dependencies:
pip-compile --output-file requirements.txt requirements.inSpecification
The idea is that these tests run in between your search client and your search engine or search adapter. You use the test interface instead of your search engine interface to run checks on every request the client makes:
Is the client request formulated correctly?
Is the server response folmulated correctly?
These cases can be defined and are defined:
When the client issues a successful request and the server responds correctly, the request is forwarded, optionally including a note that the tests passed.
When the client issues a malformed request, HTTP error 400 is returned including the information which tests did not pass. The request is forwarded to the server and the response is expected to be 400, too.
When the client issues a correct request, and the server response is malformed, then HTTP error 409 is returned including a list of error descriptions of the mistakes made by the server.
To make the decisions transparent, the client request and the server response are included in the error reponses.
Usage as Proxy
Suppose you have a server running on http://localhost:1234/v1/search/. You can tun the search engine tests as a proxy on port 8080 like this:
python3 -m schul_cloud_search_tests.proxy http://localhost:1234/v1/search 8080 /endpoint/Now, all your requests to http://localhost:8080/endpoint/ will be forwarded to http://localhost:1234/v1/search.
When you are done, you can visit http://localhost:8080/stop to stop the server or run this command:
python3 -m schul_cloud_search_tests.stop 8080The return code is zero (success) if all tests of all requests passed. If one test fails, it is a number greater than zero.
Note that the defaults are as follows. The command in each line is the same.
python3 -m schul_cloud_search_tests.proxy http://localhost:8080/v1/search 8081 /v1/search
python3 -m schul_cloud_search_tests.proxy http://localhost:8080/v1/search 8081
python3 -m schul_cloud_search_tests.proxy http://localhost:8080/v1/search
python3 -m schul_cloud_search_tests.proxyUsage as Tests
In case you have a search engine which should be tested at the URL, you can run tests against it with the following command
python3 -m schul_cloud_search_tests.search http://localhost:8080/v1/search \
--query "Q=einstein" --query "Q=test&page[offset]=20"The tests test the following:
There is a search engine running at http://localhost:8080/v1/search
These queries Q=einstein and Q=test&page[offset]=20 are handled correctly.
Additional tests are run wich test correct and malformed queries, see Issue 6.
The return status of the tests is zero if all tests passed, otherwise a positive number.
Development Process
The idea is stated in the motivation blog post. We can use the tests to test the search engines. However, the tests can become complex and must be tested themselves. Therefore, the following development process is proposed.
Have a look at the specification:
The Search API describes how to request a search.
The Response Schema describes what to expect as a response.
The Error Schema describes what an error should look like.
The specification is the most important document. It determines what needs to be tested.
Implement tests according to examples of the specification. These tests are located in the schul_cloud_search_tests/tests folder. They test how you would like to have the search proxy respond to the different valid and invalid requests.
Make the tests run.
If it is a new condition under which a proxy request succeeds or fails, you should implement these as tests in the schul_cloud_search_tests/search_tests folder. These tests are executed when a search request goes through the proxy.
If this is a communication feature of the proxy, it must be described in the Specification section. The code in the schul_cloud_search_tests/proxy.py should be touched.
Further Reading
You can edit this document on Github and check it with this editor.
2 maintainers
Release files for schul-cloud-search-tests 1.0.96
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| schul_cloud_search_tests-1.0.96.tar.gz | 24.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| schul_cloud_search_tests-1.0.96-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 61.2 kB
Release files / schul_cloud_search_tests-1.0.96.tar.gz
| Download URL | schul_cloud_search_tests-1.0.96.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ca136e6b90a43a37d921b129bc2c8fa0cd1da446fa25a47fde1bbd27d658ce3
|
|
BLAKE2b-256 checksum How to use checksums |
f7adbef60ab335b7e3f9c1481c507d92ac204bd45e3de045f13d46886cdffff3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / schul_cloud_search_tests-1.0.96-py3-none-any.whl
| Download URL | schul_cloud_search_tests-1.0.96-py3-none-any.whl |
|---|---|
| Size | 36.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d008445d216074478b0121436ae51a31d602be8c43cbf89de13e54f9fd4d1f95
|
|
BLAKE2b-256 checksum How to use checksums |
9ec0e2a475bf109c25cb69cc32765216023e39804183cffb7afc43211478102c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
