Sebastian Choren
Sebastian Choren
> I was hoping to see more calling relationships in the Graph view but I'm only seeing 1 service so I will investigate a bit further. We're having a conversation...
I agree. Let's save everything available and decide what to show later. We'll probably iterate a bit on what to show, so having all info allows max flexibility
@mathnogueira You said we can "hide" fields based on the request. I.E `/api/tests` would not return the results or definitions of each test, `/api/tests/{testID}/runs` would not return trace and results,...
On hold at the moment
I've been thinking about this issue for some time now, and I've come up with a proposal: https://github.com/kubeshop/tracetest/issues/951. This is just my first though, so feel free to comment any...
Totally, but it's not a blocker to start working on it. This just adds on top of tests, so tests can keep evolving without interfering with this feature
I'm not sure about adding the `output:` prefix. I get confused by the fact that an `env` can come from any external source, but `output` can only be internal. I'm...
I think that flow makes the most sense of any options. In that case, your tests can only reference internal variables or env vars. A definition would look like this:...
I think we need to remove the `cli/definition` package and move it to the server, and have the cli import it from the server, so we don't have anything duplicated
Hi @niuzhi. Looks like this is a bug in our installer. We only check for the `docker compose` command, not the `docker-compose` one (space vs dash). I've pushed a fix,...