PassesWithinAnnotation for Processes about chorus

[nickebbutt]

Hi, you can come close to this already if you set the property readTimeoutSeconds for the processes handler
https://github.com/Chorus-bdd/Chorus/wiki/ProcessesHandlerProperties

When you wait for process output, the step will timeout after this many seconds if the output is not detected.
This property will take effect at the feature level so it is not quite as specific as setting an individual timeout for each step, but it may be enough.

Something else we could easily add are extra steps in the process handler which include 'within' such as:

.read the line '(.)' from (?:the )?([a-zA-Z0-9-_]*) process within (\d+) seconds

We may look to add those in a release soon if it would be helpful

[yamaduc]

.read the line '(.)' from (?:the )?([a-zA-Z0-9-_]*) process within (\d+) seconds would be a great addition.

I realized what I meant to say in the bug is I need a way to:

When I write the line 'execute some command' to the console process
Read the line xxxx
Then I write the line 'execute some command' to the console process

I need this group of steps in some PassesWithinAnnontation

I suppose I could call this in a step macro and call it multiple times, but the feature file will get ugly..

[yamaduc]

Right now we have some output, which prints some value sort of like executing a ping, where it continues to print forever until we hit the enter or return key.

The problem with step

Then I read the line 'created=1772' from the console process

it never exits, because this value it printed to the stdout overt and over, eventually the test will time out.

[nickebbutt]

Closing this for now, since I think there is a new feature request raised for reading output within a given time limit. I think a more detailed example would be needed if there is another case to address