-
Notifications
You must be signed in to change notification settings - Fork 886
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
Delete TestCase (is not completely eliminated) #16322
Labels
Comments
@TeddyCr I saw this issue when working on integration tests for data quality. I can look into it. |
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected module
Data Quality
Describe the bug
When a test case is created and executed and you decide to delete it, when the test case is created again with the same name, the last status and the history are displayed.
For example, we have defined a nomenclature OM_TABLENAME_CONSISTENCY, and we create a test case and we realize that it is not correct after executing it, when we delete it and when we recreate it with the same name, it keeps the history and execution statuses as if it had never been deleted.
Keeping the history of the test case created to access the API can be interesting to analyze, deleted test cases and their history but it conflicts with renaming them to the same name.
To Reproduce
1.- I create a test
2.- I check the last executions
3.- I remove it
4.- I create it again with the same name and voila, everything appears again.
Expected behavior
It may not be a good idea to remove it from the database altogether, but to allow a case with the same name to be created over time and to be internally different.
Think for example that today I create a test case called ACCURANCY_TABLE, and I test, and in 1 year I create another test case called ACCURANCY_TABLE, and suddenly the whole history appears, it will be very confusing and surely we will not remember that a test case with the same case was made 1 year ago.
Version:
thanks in advance,
Carlos
The text was updated successfully, but these errors were encountered: