Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple tests of same type on one entity #90

Open
JanPeterDatakind opened this issue May 17, 2023 · 2 comments
Open

Allow multiple tests of same type on one entity #90

JanPeterDatakind opened this issue May 17, 2023 · 2 comments

Comments

@JanPeterDatakind
Copy link
Contributor

Describe your maintenance task
Currently, the test result views are created with a prefix of "tr_dot_model", followed by the names of the entity and the testtype.
Hence, setting up the same testtype twice (e.g. expression is true) on the same entity leads to two views with the same name, which breaks the execution of DOT. This could maybe be prevented by implementing all conditions or specifications for multiple scenarios into one test, but this would complicate the test definition and interpretation of test results.

@bkowshik
Copy link

bkowshik commented Jan 4, 2025

Example

Below are the steps I tried, not sure if this is the error and I am replicating the scenario in this issue right.

  1. There is an existing test checking if price > 0 in all_flight_data entity.
image
  1. I created another similar test, checking if price > 50 a sample threshold.
image
  1. I get the error below when I try to save the test.

Error while adding test! ERROR: syntax error at or near "non" Position: 595

image

@bkowshik
Copy link

The previous error was from an issue with syntax in the Add_Test query. Post fixing that, I get the actual error detailed in this Github Issue which is below:

Error while adding test! ERROR: duplicate key value violates unique constraint "configured_tests_pkey" Detail: Key (test_id)=(c3a73e06-5c42-3fe0-8eb1-cd7e618171fd) already exists.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants