Srikanth

there are a few changes like programatic skipping scenarios and support for async/await in tests. I know we had some issues with async before, so that is a possible suspect....

# Lazy vs Eager Scenario Initialization - Quick Benchmark Comparison ## Summary **Lazy mode is 100-4000x faster and uses 99.9% less memory during scenario creation.** ## Quick Comparison Table ###...

@jensakejohansson - thanks for checking this out. I had missed one path with nested tables. I have pushed another commit - think this should address the issue. If you can...

no, that's my bad - I didn't push it before, now It should be in - apologies

this can be tricky. The steps you've listed are probably in context of your test suite. What would help is if you have a test suite or any other means...

I have a PR here: https://github.com/getgauge/gauge/pull/2791 this should address a few issues highlighted. I would love it if folks could try out the build from the branch and let me...

#2791 is merged, so you can do a `go get` install and check it out. I have raised another PR - https://github.com/getgauge/gauge/pull/2792 - this is an attempt to address the...

No, not really. I had a couple of lean days last week and I could spend some time on this. If you can, please go ahead by all means! Thanks...

This is a hot topic - Gauge maintains and I am still of this opinion that the order of test execution is not guaranteed unless you use the `--sort` flag....

There is another option. `gauge run` honours the order of spec/scenario passed. so if you were to randomize all scenarios and pass it to `gauge run` it will execute in...