Add --no-fail-fast to keep executing tests even if there are error

[jcamiel]

When a Hurl file is in error, we stop the tests run as soon as we can (the default is "fail fast")

For instance:

$ hurl --jobs 1 --test a.hurl b.hurl c.hurl d.hurl

Given b.hurl is in error, executed tests will only be a.hurl and b.hurl.

We have an option called --continue-on-error that, if one Hurl file is in error, will try to execute this file until the end.

As the doc tells:

Note that this option does not affect the behavior with multiple input Hurl files.

All the input files are executed independently. The result of one file does not affect the execution of the other Hurl files.

So we need another option to run all Hurl files, regardless of there are error or not => --no-fail-fast.

[krakenbite]

Hi,

I would like to work on this issue. Can I take this on?

[jcamiel]

Hi @krakenbite

You can of course but be warned that this one can be more difficult that it seems.

For a starter, you can also work on issues labeled "good first issues" good first issue Good for newcomers

[krakenbite]

@jcamiel Thanks for your response!

I already had a look at the code and I think I already found the right places which need modification.

As we currently bail-out on errors, question is how we want to handle errors in the future. How do we want to display them to the user if one or several files have issues?

Also, I think I can have a look at this issue as I like to challenge myself with difficult problems and don't need an issue labeled good first issue Good for newcomers .