posthog/pytest.ini

[pytest]
DJANGO_SETTINGS_MODULE = posthog.settings
addopts = -p no:warnings --reuse-db

markers =
    ee
    clickhouse_only
    skip_on_multitenancy
Run tests via pytest (#3417) * Compile requirements-dev.txt with latest pip-tools * Install pytest * Avoid picking up factories as tests * New runner * Always set TEST env variable running tests Some of our tests rely on it. * Remove repetition * Fix a broken test * Cut down noise from bin/tests * Rename test factory * Fix stickiness filter * Skip a broken test This has been broken since numpy removal PR. Sadly tests were not running for this submodule * Fix import on ee * Run ee tests properly The django_db_setup fixture will be automatically run when running ee/ module tests. * Make tests run on CI * Include REDIS_URL, fix cloud * Set TEST env variable * Hack cloud tests to work * Attempt at workflow fix * Import Person model when running ee tests This module implicitly adds hooks, so this is needed when running tests * Respect reuse-db for clickhouse * Add custom markers to avoid warnings * pytest: use ch test database always Accidentally wiped by ch setup a few times without this. Oops * Remove repetition in tests * Pytest: Always run migrations Testing a state cleanup fix * Use same DB in conftest and main code * Pytest: autoset TEST setting without env variable * fix broken test Co-authored-by: eric <eeoneric@gmail.com> 2021-02-24 08:32:44 +01:00			`[pytest]`
			`DJANGO_SETTINGS_MODULE = posthog.settings`
fix(event-search): make search case insensitive for postgres (#5880) * chore(dev): make sure we reuse the postgres db in tests This can be overridden with `--create-db`, see https://pytest-django.readthedocs.io/en/latest/database.html#example-work-flow-with-reuse-db-and-create-db * refactor(test_event_definition): remove requirement for demo data team The data takes a long time to import and is a little indirect. Removed and replaced with some simple db creates * fix(event-search): make search case insensitive for postgres It already is for clickhouse which is using ILIKE. One thing I'm not sure about is why we'd not use postgres tsv here instead of doing our own tokenising etc. Still may be relevant for data that we wish to keep in postgres. Closes https://github.com/PostHog/posthog/issues/5812 Co-authored-by: Harry Waye <harry@scalexp.com> Co-authored-by: eric <eeoneric@gmail.com> 2021-09-09 19:57:34 +02:00			`addopts = -p no:warnings --reuse-db`

Run tests via pytest (#3417) * Compile requirements-dev.txt with latest pip-tools * Install pytest * Avoid picking up factories as tests * New runner * Always set TEST env variable running tests Some of our tests rely on it. * Remove repetition * Fix a broken test * Cut down noise from bin/tests * Rename test factory * Fix stickiness filter * Skip a broken test This has been broken since numpy removal PR. Sadly tests were not running for this submodule * Fix import on ee * Run ee tests properly The django_db_setup fixture will be automatically run when running ee/ module tests. * Make tests run on CI * Include REDIS_URL, fix cloud * Set TEST env variable * Hack cloud tests to work * Attempt at workflow fix * Import Person model when running ee tests This module implicitly adds hooks, so this is needed when running tests * Respect reuse-db for clickhouse * Add custom markers to avoid warnings * pytest: use ch test database always Accidentally wiped by ch setup a few times without this. Oops * Remove repetition in tests * Pytest: Always run migrations Testing a state cleanup fix * Use same DB in conftest and main code * Pytest: autoset TEST setting without env variable * fix broken test Co-authored-by: eric <eeoneric@gmail.com> 2021-02-24 08:32:44 +01:00			`markers =`
			`ee`
Implementation of diagnose event names (#6235) * chore(diagnose): add a stub endpoint for event diagnosis This adds an insight endpoint that takes a `target_entity` and returns a list of events ordered by significance of a person reaching `target_entity` Followup PRs will add actual calculations but this should act as a conversation piece around the structure of request and response, as well as a stub from which UI development can start. * play around to get mypy typings right * Sort out test reponse structurea * refactor: address CR comments * feat(diagnose): add diagnose stubs for implementation * feat(funnel): add event correlation calculation implementation This adds to the `/api/projects/<team_id>/funnel/correlation` endpoint an implementation that calculates the odds_ratios for each event that a user that has been part of a funnel, successful or otherwise. * chore(correlation): get query working * refactor(correlation): move functions to Query methods 2021-10-06 12:08:16 +02:00			`clickhouse_only`
Run tests via pytest (#3417) * Compile requirements-dev.txt with latest pip-tools * Install pytest * Avoid picking up factories as tests * New runner * Always set TEST env variable running tests Some of our tests rely on it. * Remove repetition * Fix a broken test * Cut down noise from bin/tests * Rename test factory * Fix stickiness filter * Skip a broken test This has been broken since numpy removal PR. Sadly tests were not running for this submodule * Fix import on ee * Run ee tests properly The django_db_setup fixture will be automatically run when running ee/ module tests. * Make tests run on CI * Include REDIS_URL, fix cloud * Set TEST env variable * Hack cloud tests to work * Attempt at workflow fix * Import Person model when running ee tests This module implicitly adds hooks, so this is needed when running tests * Respect reuse-db for clickhouse * Add custom markers to avoid warnings * pytest: use ch test database always Accidentally wiped by ch setup a few times without this. Oops * Remove repetition in tests * Pytest: Always run migrations Testing a state cleanup fix * Use same DB in conftest and main code * Pytest: autoset TEST setting without env variable * fix broken test Co-authored-by: eric <eeoneric@gmail.com> 2021-02-24 08:32:44 +01:00			`skip_on_multitenancy`