Matheus Nogueira
Matheus Nogueira
Hey @kdhamric, do you have the list of information that would be good to have in the test run? * latest commit * PR number? * PR url?
I'd go with a flag for now. It seems to be too cumbersome to introduce graphql right now.
That's definitely something that we need. I'm thinking about using some kind of syntax: `#{uuid}`, `#{name}`, etc. We can use [gofakeit](https://github.com/brianvoe/gofakeit) to generate those values for us. I don't see...
Yes, currently we only support data generation on the triggering side. I'm planning to start working on adding support to data generation probably on Monday.
About supporting variables, we have the goal of adding support for both variables and expressions: #782
Hey @mrwatson we just released `v0.6.4` and it introduces the concept of generator functions which are functions that generate random data in your test trigger section. You can read more...
It would probably require #824 and #782 (due to variable referencing) to be really useful
Today we have that in tracetest's global configuration: ```yaml pollingConfig: timeout: 10m retryDelay: 5s ``` Maybe it makes sense to have that as the default configuration and allow tests to...
Hey @abangser! I did some research on how we can achieve that, and I came to the conclusion that this will be hard to use Tracetest inside Kubernetes due to...
#1297 was a partial implementation of this. I'll work on another PR to finish the windows installation