platypush/tests/etc/config_test.yaml

include:
    - include/test_procedure.yaml

main.db:
    engine: sqlite:////tmp/platypush-tests.db

backend.http:
    port: 8123
    num_workers: 1
    use_werkzeug_server: True

backend.redis:
    disabled: False
Refactored tests to use pytest with fixtures instead of unittest.TestCase 2021-03-06 16:21:28 +01:00			`include:`
			`- include/test_procedure.yaml`

Fixed and expanded integration tests to deal with HTTP user authentication 2020-12-16 02:10:37 +01:00			`main.db:`
Tests improvements 2021-03-06 16:25:37 +01:00			`engine: sqlite:////tmp/platypush-tests.db`
Fixed and expanded integration tests to deal with HTTP user authentication 2020-12-16 02:10:37 +01:00
Replaced the local fifo test with a test for the HTTP backend 2018-01-04 18:29:03 +01:00			`backend.http:`
			`port: 8123`
Added `use_werkzeug_server` option to `backend.http`. There are situations where you may not want to run the HTTP server in a full blown WSGI-over-Tornado container - unit/integration tests and embedded single-core devices are among those cases. In those scenarios, we should allow the user to be able to run the backend using the built-in Werkzeug server provided by Flask. 2023-05-20 15:26:58 +02:00			`num_workers: 1`
			`use_werkzeug_server: True`
Added config.yaml for tests 2017-12-22 02:20:28 +01:00
Removed timeout from get_plugin lock; Added Redis server to tests configuration 2018-09-20 12:59:18 +02:00			`backend.redis:`
			`disabled: False`