我刚刚使用了 NUnit 的参数化测试。
我创建了一个枚举:
/// <summary>
/// Enum that holds references to different browsers used in testing.
/// </summary>
public enum BrowserTypeEnum
{
/// <summary>
/// Google Chrome.
/// </summary>
Chrome,
/// <summary>
/// Mozilla Firefox.
/// </summary>
Firefox,
/// <summary>
/// Internet Explorer.
/// </summary>
InternetExplorer
}
在 TestFixture 中这样调用它:
/// <summary>
/// Tests related to browsing Google
/// </summary>
[TestFixture(BrowserTypeEnum.Chrome)]
[TestFixture(BrowserTypeEnum.Firefox)]
public class GoogleTests : AbstractTestFixture
{
}
在 AbstractTestFixture 中:
/// <summary>
/// Create's the browser used for this test fixture.
/// <para>
/// Must always be called as part of the test fixture set up, not the base test fixtures.
/// </para>
/// <para>
/// It is the actual test fixture's responsibility to launch the browser.
/// </para>
/// </summary>
protected override void CreateBrowser()
{
switch (BrowserType)
{
case BrowserTypeEnum.Chrome:
Browser = new ChromeDriver();
break;
case BrowserTypeEnum.Firefox:
Browser = new FirefoxDriver();
break;
case BrowserTypeEnum.InternetExplorer:
Browser = new IEDriver();
break;
default:
break;
}
}
可能不是最好的解决方案,但我发现它非常易读。另一种方法是使用 Selenium Grid 之类的东西,或者将驱动程序的类型传递给 NUnit 并直接创建它,如下所示:
/// <summary>
/// Tests related to browsing Google
/// </summary>
[TestFixture(typeof(FirefoxDriver))]
public class GoogleTests : AbstractTestFixture
{
}
另一种选择是,如果您使用 CI 服务器解决方案,请创建一个配置设置以指示用于测试的浏览器。让 CI 驱动程序重复测试 3 次,每次都编辑该配置设置。