pytest | The pytest framework makes it easy to write small tests, yet scales to support complex functional te | Functional Testing library

I used pip install eth-brownie and it worked fine, I didnt need to downgrade. Im new to this maybe I could be wrong but it worked fine with me.

@hoefling and @Arkadiusz Łukasiewicz were right, I just needed to add the corresponding DB within the factories:

You can use the built-in request fixture in your own fixture:

The request fixture is a special fixture providing information of the requesting test function.

Its node attribute is the

Underlying collection node (depends on current request scope).

If you want to test that a "thing" is deleted, make a fixture without teardown, delete it in the test, then assert if it is deleted.

The current structure of myfixture guarantee cleanup() is called between test_1 and test_2, unless prepare_stuff() is raising an unhandled exception. You will probably notice this, so the most likely issue is that cleanup() dosn't "clean" everything prepare_stuff() did, so prepare_stuff() can't setup something again.

As for your question, there is nothing pytest related that can cause the hang between the tests. You can force cleanup() to be called (even if an exception is being raised) by adding finalizer, it will be called after the teardown part

You are using the default traceback logger of pytest, which also logs the arguments passed to a specific function. One way to solve this kind of leak is to use another traceback mode. You can find the general documentation at this link. In that link you can find two interesting traceback modes:

• --tb=short
• --tb=native

Both give you all the information you need during your specific test since:

• They still give you information about the tests failed or succeded
• Since you are using parametrized tests, the logs about failures will look like FAILED test_issue.py::test_connectivity[server_name-server_jdbc_port-server_database-name_env_credentials-name_env_pwd], in this way you can identify the actual failing test

Mind that this solution, while avoiding to log the credentials used at test time, these credentials used during testing must not be the same that will be used outside the test environment. If you are concerned with the fact that in case of failures in production, the logger could leak your credentials, you should setup you logger accordingly and avoid to log the default text of the exception.

This works for me, please try:

Your logic starts a process wrapped within the MyClass object which itself spawns a new process via the os.system call.

When you terminate the MyClass process, you kill the parent process but you leave the 7zip process running as orphan.

Moreover, the process.terminate method sends a SIGTERM signal to the child process. The child process can intercept said signal and perform some cleanup routines before terminating. This is not ideal if you want to simulate a situation where there is no chance to clean up (a power loss). You most likely want to send a SIGKILL signal instead (on Linux).

To kill the parent and child process, you need to address the entire process group.

You're getting the failure before your monkeypatch is able to run. The loading of the environment variable will happen when the runner module is first imported.

If this is a module you own, I'd recommend modifying the code to use a default value if DATA_ENGINEERING_BUCKET isn't set. Then you can modify it's value to whatever you want at runtime by calling module.DATA_ENGINEERING_BUCKET = "my_bucket".