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
Prior to #1110, it was possible to run the tests from a test's local directory. E.g.
cd autogen/test/agentchat/contrib
python test_compressible_agent.py
or
cd autogen/test/agentchat/contrib
pytest test_compressible_agent.py
But now, doing so raises the error:
ModuleNotFoundError: No module named 'conftest'
Now, tests need to be run from the test root folder:
cd autogen/test
pytest agentchat/contrib/test_compressible_agent.py
This isn't a real problem, but it is a change in prior behavior, and it took me a minute to understand what was going on despite considerable prior experience with the tests.
Steps to reproduce
No response
Expected Behavior
No response
Screenshots and logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
I just logged the same issue as #1137 without realizing it was a dup. But I would give this bug a higher priority, because we have blog posts directing users to run some of these tests, and running pytest within the test folder (as described above) is a pain, and makes debugging into these tests harder. I propose a different solution in #1137.
Describe the bug
Prior to #1110, it was possible to run the tests from a test's local directory. E.g.
cd autogen/test/agentchat/contrib python test_compressible_agent.py
or
cd autogen/test/agentchat/contrib pytest test_compressible_agent.py
But now, doing so raises the error:
Now, tests need to be run from the test root folder:
cd autogen/test pytest agentchat/contrib/test_compressible_agent.py
This isn't a real problem, but it is a change in prior behavior, and it took me a minute to understand what was going on despite considerable prior experience with the tests.
Steps to reproduce
No response
Expected Behavior
No response
Screenshots and logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: