blocks|key|2582502|text|谢谢指点@Arran。切换到Firefox驱动程序解决了这个问题。我想这一定是I驱动程序的错误所在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2582503|[SetUp]
public+void+SetupTest()
{
++++Driver+=+new+FirefoxDriver();
}|code-block|syntax|javascript|2582504|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Thanks for the pointers @Arran. Switching to a Firefox driver fixed the issue. I guess the fault must lie somewhere in the Internet Explorer driver.

<pre><code>[SetUp]
public void SetupTest()
{
 Driver = new FirefoxDriver();
}
</code></pre>

I'm having an issue running Selenium tests in NUnit from Cruise Control .NET. I have a simple test that runs fine when I run from the NUnit GUI on our continuous integration server. However when the NUnit test is run from Cruise Control .NET on the same server, the test always fails. Tests that don't use Selenium run fine from both the NUnit GUI and from Cruise Control.

<pre><code>[SetUp]
 public void SetupTest()
 {
 Driver = new InternetExplorerDriver();
 }



 [TearDown]
 public void TeardownTest()
 {
 Driver.Quit();
 }



 /// &lt;summary&gt;
 /// Test basic Selenium functionality.
 /// &lt;/summary&gt;
 [Test]
 public void SeleniumTest()
 {
 Driver.Navigate().GoToUrl(TestConfig.TestURL);
 IWebElement testEle = WaitForElement(Driver, By.Id, "body", TestConfig.TestWaitMS);
 Assert.IsTrue(true);
 }



 private static IWebElement WaitForElement(IWebDriver driver, ByFunc byFunc, string elementId, int waitMs,
 string waitOutput = null, int pause = 50)
 {
 bool elementFound = false;
 int i = 0;
 IWebElement webElement = null;
 while (!elementFound &amp;&amp; (i * pause) &lt; waitMs)
 {
 try
 {
 webElement = driver.FindElement(byFunc(elementId));
 elementFound = true;
 }
 catch (NoSuchElementException)
 {
 i++;
 Thread.Sleep(pause);
 if (waitOutput != null)
 Console.Write(waitOutput);
 }
 }
 if (elementFound)
 return webElement;
 else
 throw new NoSuchElementException(string.Format("Could not find element {0} after waiting {1}ms.", elementId, waitMs));
 }
</code></pre>

WaitForElement is just a helper function that allows me to assign specific waits for certain elements rather than have a blanket waiting time for the entire test run.

The test fails when the NoSuchElementException is raised from the WaitForElement function.

I've found some links on Google saying that you need to run SeleniumRC as a service to get it to run from Cruise Control. I don't think that applies here as I'm using the WebDriver version. Please correct me if I'm wrong.

<ol>
<li>IE version 8</li>
<li>Cruise Control .NET 1.8.3.0</li>
<li>NUnit 2.6</li>
<li>Selenium 2.0.0</li>
</ol>

Running Selenium via NUnit and Cruise Control .NET

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

我在NUnit中运行Control .NET中的Selenium测试时遇到了问题，在我们的连续集成服务器上从NUnit GUI运行时，有一个简单的测试运行良好。但是，当NUnit测试从同一服务器上的Control .NET运行时，测试总是失败。不使用Selenium的测试可以从NUnit GUI和Control运行。[SetUp]    public void SetupTest()    {  

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐