If you set up a scenario where the executors runs less than one iteration per second, the value is floored to zero while in progress. However, it reports the correct amount in the end-of-test summary.

Environment

• MacOS Big Sur
• k6 v0.29.0

Expected Behavior

checkEveryFiveSeconds   [=========>----------------------------] 0/1 VUs  0m17.1s/1m0s  0.20 iters/s

or

What RedrawInterval is being constant is a problem. Support the --redraw-interval option to make it configurable.

I think for very quickly looking at the output of your load test it would be cool if oha used some colors with sane defaults for how long something takes (maybe green 0s - 0.3s, orange, 0.3-0.8, red, >=0.8?).

I suggest using colors in the TUI view and in the final output. Of course, make it into an option but I think it should be "auto" by default so that if the terminal is detected to be capab

We need to add more integration tests (living in the src/it folder) to cover various usage scenarios.

Right now we only have a single test that just checks that the plugin can run a basic test with no additional configuration (This can be used as an example on how to configure other integration tests). We should be testing various configuration options as well.

Requirements:

• The .jmx files

Is your feature request related to a problem? Please describe.
Currently when the server is not up, Tests tab don't show any network error popup. Because of this the user may go ahead and try creating tests

Describe the solution you'd like
Show Network Error popup in the same way it's done for Last scheduled runs Tab