Arize does not automatically skip tracing when code is run from testing frameworks like pytest. To ensure that your traces are captured and sent to the Phoenix dashboard, you need to verify a few things:
1. *Tracer Initialization*: Ensure that the tracer is correctly initialized before any code that you want to trace is executed. This includes setting up the tracer provider and span processor as shown in the <https://docs.arize.com/phoenix/tracing/how-to-tracing/setup-tracing-python|Phoenix documentation>.
2. *Environment Variables*: Make sure that the necessary environment variables, such as `PHOENIX_COLLECTOR_ENDPOINT`, are correctly set. This endpoint should point to your Phoenix server, for example, `http://localhost:6006/v1/traces`.
3. *Project Configuration*: Ensure that the project name is correctly set in your tracing setup. Projects in Phoenix are created when traces are sent with a new project name. You can set the project name using the `register` function from the `phoenix.otel` module, as described in the <https://docs.arize.com/phoenix/tracing/how-to-tracing/setup-tracing-python|setup guide>.
Would you like more detail on any specific part of this setup?
Sources:
- <https://docs.arize.com/phoenix/tracing/how-to-tracing/setup-tracing-python|Phoenix documentation>
