@theseion @fzipi Any hints on how to force a test to output a string with new lines?

Use encoded_request and pass the payload as base64 encoded string. That ensures that you carriage returns don't get lost as well.

Use encoded_request and pass the payload as base64 encoded string. That ensures that you carriage returns don't get lost as well.

This is for creating a request but i need to create a response.

We don't yet have a facility to mock responses. However, because responses are reflected we can use the request to inject at least part of the response. I quickly tested the test you wrote and the response does contain the newlines you sent in the request (pass --trace to go-ftw to see the response).

But test haven't pass, so something is wrong. Maybe it outputed \r\n instead of \n, which regex expects?

There are two problems:

1. the expected response is embedded, so the response body will never match ^....
2. line breaks are returned as literal \n sequences

We need to have a built-in facility in go-ftw for this, unfortunately.

So, is it currently possible to write a test for that rule?

No, it currently isn't possible. I would still like to keep your test. Just set enabled: false and add to the description that we cannot currently run this test with the setup we have.

@theseion Thank you!

Glad this made the cut.