I have been using MbUnit as the driver of parallel webdriver tests for a
while.
To my life simply, I apply parallization at a class level rather than
method level
e.g.
[Parallelizable(TestScope.Self)]
public class SigningUpTests
{
private RemoteWebDriver _driver;
[SetUp]
public void SetUp()
{
_driver = DriverFactory.CreateDriver();
}
[TearDown]
public void TearDown()
{
_driver.Quit();
}
[Test]
pubic void Test1()
{
...
}
[Test]
pubic void Test2()
{
...
}
}
This means that I do not have to worry about different threads sharing the
same webdriver instance. If you were desperate to have paralleization
within a class, then you cannot use SetUp and TearDown without creating
some kind of context container.
--
You received this message because you are subscribed to the Google Groups
"MbUnit.User" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mbunituser/-/Uvl-6mrCUFUJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mbunituser?hl=en.
