It would be cool to have an easy way to map an event message to an event. For example, I see "Step has timed out". What event is that?
Step Issues would be a good place to show that.
It is buried in the console output, but that's not too handy.
We are working towards enhancing the ability for our users to see the events and analysis rule actions as they happened in a test report in a future release of iTest. If anyone has any suggestions in this area, please feel free to add to this thread.
The report viewer now shows you, by name, the event that was triggered (e.g. OnStepTimeout), which is useful if you need to override it. A nice addition to the events pages (local and global) would be the ability to search for that event name! Kind of like how you can search for test reports--that's a really cool search mechanism.
This one is already in our feature request database. Expect to see it in a future release.
From the Global Events, I have set message at Events OnStepTimeout "Error:Step has timed out at $myServer cmd failed".
Is there a way that I can extract this message, write it in an email and then send it.
Maybe I'm missing something, but can't you just add a CallProcedure to the event, and have that send an email? CallProcedure can call any arbitrary test case, so you basically have the full power of iTest at your disposal.
What Dclaar has suggested will definitely work and I believe that you can pass arguments to the email procedure.
Is it that you want the error message text? Or just that you want to fail the test and send an email out to let you/test owner know that it has failed?
I just want to extract the message text "Error:Step has timed out at $myServer cmd password" and store it in a var $loginMsg and then using the writeLine action in the email as followed:
Action Session Description
writeLine EMAIL $loginMsg
I know that it is possible to call proc inside the analysis but what Dclaar suggested is puzzling me how can I add CallProcedure to the event? If I have my proc Pass_GlobaEvent (gb as argument), is this that I have to add in the rule action:
CallProcedure Pass_GlobaEvent -gb $OnStepTimeout
Events don't give you nice help like other parts of iTest, but yeah, you'd do something like:
CallProcedure project://lib/send_email.fftc#send_message -gb "Error:Step has timed out at $myServer cmd password"
You mention "extracting" a message; I'm wondering if that's your question?
Well Dclaar stole my thunder :), but what you can do is something like this:
I think that this is an excellent feature request. It would be very handy for people to trace back to the event that caused a message or an action.
