Welcome aboard!
> but I am facing the following issue:
> When I raise exception inside my thread to indicate fail, this
> exception is being reported as "INFO" in the log and not as FAIL,
> resulting my test to report pass and not fail as its expected ?
> my question is how can I do it correctly ? report FAIL from my
> threads.
You should generally communicate with Robot only from the main thread.
Logging messages from threads ought to work, but exceptions should be
risen only from the main thread.
Cheers,
.peke
--
Agile Tester/Developer/Consultant :: http://eliga.fi
Lead Developer of Robot Framework :: http://robotframework.org
I'm not sure how exactly you're using threads in your RF test library, but we do it all the time at TI. In our design the main thread accepts a "run_keyword" call from RF and then distributes the work to each thread. Each thread is driving a different SUT (e.g. a different attached TI-Nspire device). The main thread then gathers the results from each of the worker threads. If ANY of the worker threads returns a "FAIL" then a "FAIL" exception is generated by the main thread. This exception would identify the number, and which, of the device-specific threads that had a failure.
Is this design anything like what you're doing with multiple threads in your RF test library?
Cheers,
Martin
Regards
EK
--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To post to this group, send email to robotframe...@googlegroups.com.
To unsubscribe from this group, send email to robotframework-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/robotframework-users?hl=en.
@Martin: Your setup sounds interesting. Do the SUTs communicate with
each other? What do the tests look like?
One thing that I've been working on is a general network package
testing library[1] and any experience with tests that interact with
multiple communicating SUTs would be helpful.
Main question:
How to model in robot test data in an understandable and clean way the
situations where multiple actors/SUTs communicate with each other?
We have also done an experimental multiprocessing library that also
supports interprocess (between robots that can even run on different
machines) communication[2] .. but it is really very experimental.
[1] http://code.google.com/p/rammbock/
[2] http://code.google.com/p/robotframework/source/browse/proto/parallel
2011/6/20 Taylor, Martin <cmta...@ti.com>:
--
Mikko Korpela
> To unsubscribe from this group, send email to robotframework-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/robotframework-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "robotframework-users" group.
> To post to this group, send email to robotframe...@googlegroups.com.
> To unsubscribe from this group, send email to robotframework-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/robotframework-users?hl=en.
>
>
--
Mikko Korpela