Pekka Klärck

Thanks for submitting an issue. It seems we have somehow missed PR #15. @jussimalinen is currently on holiday, but I hope he has time to look at this when he's...

This project has been pretty much abandoned and I've personally never used it. If there are users, making it Python 3 compatible is definitely a good idea. Are you interested...

On a quick look it seems to me you haven't specified expected messages in the documentation for the failing tests.

I doubt we can do anything for this. There's no guarantee that the other end of the connection would support running `shopt login_shell` or similar. Is there a reason you...

Are you interested in enhancing the docs and provide a pull request? Notice that docs need to be generic, though, there's no guarantee that the server even has bash. The...

Could you try adding `PASS` into the beginning of the doc to explicitly specify that the test should pass? The reminder of the doc ought to then be used for...

You are right, if there's `FAIL` anywhere the expected status is `FAIL` even if there would be `PASS` as well.

If I've understood this issue correctly, it only manifests itself if the test itself is expected to pass but there are log messages with `FAIL` level. This can happen, for...

There's no log level `PASS` so the problem only occurs if test is expected to pass but to have `FAIL` messages. This obviously needs to be fixed, but because there's...

I'd prefer flags being supported by default. I believe it would be enough to just use newish `re.fullmatch` and omit `^$` altogether.