'object' does not contain a definition for 'ElementExists'

Question

I'm trying to do an explicit wait to go around using Thread.Sleep(), but I'm always getting this issue with the ElementExists. I'm not sure if I'm missing a directive or I need to declare something.

TestProjectDemo

WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(10));
driver.Navigate().GoToUrl("https://bi7-azure.test.com/");
wait.Until(ExpectedConditions.ElementExists(By.Id("appList")));
driver.Navigate().GoToUrl("https://bi8.test.com/azure/");
Thread.Sleep(10000);
driver.Navigate().GoToUrl("https://insightsmp.test.com/");
Thread.Sleep(10000);

BaseClass(this is where I'm declaring the objects)

using NUnit.Framework;
using OpenQA.Selenium;
using OpenQA.Selenium.IE;
using OpenQA.Selenium.Support.UI;
using System;

namespace TestProject.BaseClass
{
    public class BaseClassTrigger
    {  
        public IWebDriver driver;
        public object wait;
        public object ExpectedConditions;

Also please look at this question: https://stackoverflow.com/a/49867605/2501279 — Guru Stron, Apr 30 '20 at 23:38
And read [tagging help](https://stackoverflow.com/help/tagging) which states _"The only time you should use tags in your title is when they are organic to the conversational tone of the title."_. Ergo, you should not prefix every question with "Selenium C#" because you have already tagged your question as such. — ProgrammingLlama, Apr 30 '20 at 23:47
The property name is clashing with the class name. Rename the property or refer the the class using a fully qualified class name. — Greg Burghardt, May 01 '20 at 00:15

score 1 · Answer 1 · answered May 01 '20 at 00:21

You have a property on BaseClass named ExpectedConditions. The property name conflicts with the ExpectedConditions class name in the OpenQA.Selenium.Support.UI namespace. Either:

Rename the ExpectedConditions property in BaseClass or
Use the fully qualified class name: OpenQA.Selenium.Support.UI.ExpectedConditions

Most likely the ExpectedConditions property in BaseClass was a mistake introduced by choosing the wrong option in the "Quick actions and refactorings" menu in Visual Studio when trying to resolve the OpenQA.Selenium.Support.UI namespace. I would just remove the ExpectedConditions property in BaseClass.

It's not accepting the fully qualified class name though, and the red underline is on ExpectedConditions saying "The name ExpectedConditions" does not exist in the current context". — Kent Abrio, May 01 '20 at 00:26

Kent Abrio · Answer 2 · 2020-05-02T01:18:18.653

0

I fixed it by installing Selenium.Support; however, it says that it is already deprecated, the recommended way around this is to make your own function from scratch and call that function whenever you need the wait condition.

edited May 02 '20 at 01:18

answered May 01 '20 at 00:33

Kent Abrio

445
2
9
27

The ExpectedConditions and PageFactory classes have been moved to another GitHub repository, which currently has no owner. Things like WebDriverWait are still supported. – Greg Burghardt May 01 '20 at 10:59

'object' does not contain a definition for 'ElementExists'

2 Answers2