functional-testing

Please answer these questions before submitting a bug report.

What version of godog are you using?

> godog -version
Godog version is: v0.11.0

What version of Go are you using?

> go version
go version go1.15.6 darwin/amd64

What did you do?

• Add a step to a feature file including a DocString which has no registered step definition.
• Execute: `godog ru

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

❯ flame 0.0.0.0 -p 9953 -Q 10   
flaming target "0.0.0.0" (0.0.0.0) on port 9953 with 10 concurrent generators, each sending 10 queries every 1ms on protocol udp

"10 concurrent generators, each sending 10 queries every 1ms on protocol udp" is not accurate if flamethrower is only sending 10 queries per second, 10 generators * 10 queries/ms is 100,000 QPS. Unless I'm missing something

The current mock mechanism is "strict" regarding trailing slashes:

mockiavelli.mockGET('/example', {status: 200})
// GET /example/ => 404

This behaviour should be at least configurable to allow ignoring trailing slashes:

const mockiavelli = await Mockiavelli.setup(page, {ignoreTrailingSlashes: true});
mockiavelli.mockGET('/example', {status: 200})
// GET /example/ => 200

many methods are missing, any eta on the implementation?

I was interested in addnode for example

thanks