You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are creating resources and making sure they are destroyed as part of multiple tests (for example we create users, roles, databases, datasources, virtual graphs, and others)
if a test fails, then the resource can be left dangling. one way to approach this (which is currently what we are doing) is to run a test, and depending on the result, clean the resources.
This would be much easier, readable, and make the code smaller, if we would be using pytest fixtures for it.
We already added virtual graph and datasources for some tests in here: #103 , but we are are still missing some other fixtures.
The text was updated successfully, but these errors were encountered:
We are creating resources and making sure they are destroyed as part of multiple tests (for example we create users, roles, databases, datasources, virtual graphs, and others)
if a test fails, then the resource can be left dangling. one way to approach this (which is currently what we are doing) is to run a test, and depending on the result, clean the resources.
This would be much easier, readable, and make the code smaller, if we would be using pytest fixtures for it.
We already added virtual graph and datasources for some tests in here: #103 , but we are are still missing some other fixtures.
The text was updated successfully, but these errors were encountered: