Matheus Nogueira
Matheus Nogueira
@mrwatson you can read about transactions [here](https://docs.tracetest.io/concepts/transactions). We use it in our integration tests as well. You can check [this](https://github.com/kubeshop/tracetest/tree/main/tracetesting/features/environment) as an example
@schoren can you add your proposal here?
I like your suggestion, @kdhamric. Maybe we could have `polling profiles`: ```yaml polling: defaultProfile: fastTest profiles: - longRunningTest: name: Long running test strategy: sameSpanCount executions: 3 # if the number...
I'm closing this as this was implemented already.
Closing this, as it seems that #1308 fixed it.
I prefer to move the API to a v3, but if that's out of the cogitation, I think duplicating the methods and providing a `DoSomethingWithContext` variant would be the best...
Two things we have to think about here: 1. How are we gonna propagate the traceID to the frontend request? (query param or headers?) 2. We probably gonna need to...
What tracing backend are you using? Jaeger, Tempo, or sending traces directly to Tracetest?
I have seen that happen before. The problem was that the triggered system was ignoring the trace context propagation headers and this was making the app generate another `Trace-ID` for...
Hello @cb645j. Did you install Tracetest via `helm install tracetest kubeshop/tracetest`? Are you using a production-ready k8s or a testing one like minikube or kind? I tried installing tracetest locally...