Dave, I did not  understan what did you mean
# post status for user A

because watirgrid is working with processes, problem is when you have
3 processes and 100 test cases  which are excuting at same time, then
this slows down machine.



On 11 nov., 20:33, Dave McNulla <[email protected]> wrote:
> Wow, that's pretty open-ended type of question. There are so many ways
> to do things with these tools. The easy answer to give is "it depends
> on what you want to do".
>
> Here is an rdoc example of 
> watirgid:https://github.com/90kts/watirgrid/blob/master/EXAMPLES.rdoc
> From that, it looks like the grid needs to be initialized, browsers
> need to be started, etc.
>
> class FACEBOOD_SMOKE_TEST < Test::Unit::TestCase
> def setup
>  #initialize grid, start browsers, log in users A, B, and C
>  # add relationships between user A and user B
> end
>
> def teardown
> # remove relationships
> # close browsers
> end
>
> def test_friends
> # post status for user A
> # validate status is found in the news feed for user B
> end
>
> def test_unknown
> # post status for user A
> # validate status is NOT found in the news feed for user C
> end
>
> end
>
> It seems to me like it is a tool for use cases that require multiple
> actors. Do you have a use case like that?
>
> Thanks,
>
> Dave
>
> On Nov 10, 2:12 am, Danijel <[email protected]> wrote:
>
> > Hi,
>
> > I haved created a lot of unit test case in watir for IE. I would like
> > to use watirgrid to execute parallel test on multiple browser.
>
> > Can you please advise me how to integrate watirgrid into existing test
> > cases.
>
> > class SMOKE_TEST < Test::Unit::TestCase
> > def setup
> >  # start IE
> > end
> > def teardown
> > # close IE
> > end
> > def test_a
> > # clink on browser
> > end
> > def test_b
> > # clink on browser
> > end
> > def test_c
> > # clink on browser
> > end
> > end

-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

[email protected]
http://groups.google.com/group/watir-general
[email protected]

Reply via email to