Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Hello all! I’m hitting an interesting problem that isn’t making much sense to me. I’ve got a unit test setup using <https://github.com/eugeniy/pytest-tornado|pytest-tornado> following the directions in their README.md and all works perfectly fine running through pipenv. When I put pants on it though, anything written synchronously works and tests with `async` in front claim they can’t find fixtures. I’ve got a much larger project already using tornado so re-writing without async is not currently feasible, hoping this simplified example sparks something in someone. I’ve got a <https://github.com/nikwotton/Broken-Pants-Demo|sample project here> with instructions on how to reproduce the issue

I would suspect you need to ensure that the `pytest-tornado` plugin gets pulled into your test env when using Pants…

For anyone else that comes across this post, the solution is to add this to pants.toml and regenerate the lockfiles:
```[pytest]
extra_requirements=['pytest-tornado==0.8.1']
lockfile="3rdparty/python/pytest"```

Happy it was helpful :slightly_smiling_face: