blocks|key|4348524|text|您的变量表示您想要对web元素执行的操作(在本例中，单击它)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4348525|合适的类型不是String。改为使用Consumer<WebElement>+(或driver.findElement()返回的任何类型)：|offset|length|style|CODE|4348526|Consumer<WebElement>+command+=+e+->+e.click();

//+...

command.accept(driver.findElement(By.id("id1")));|code-block|syntax|javascript|4348527|这是类型安全的、高效的、可重构的，而且比反射灵活得多(因为您的使用者可以对元素做任何它想做的事情，而不限于没有任何参数的单个方法调用。例如，在文本字段中输入一些文本)|4348528|entityMap^0|0|7|6|I|K|15|K|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

Your variable represents something you want to do with a web element (in this case, click on it). 

The appropriate type for that is not <code>String</code>. Use a <code>Consumer&lt;WebElement&gt;</code> instead (or whatever the type of what <code>driver.findElement()</code> returns is):

<pre><code>Consumer&lt;WebElement&gt; command = e -&gt; e.click();

// ...

command.accept(driver.findElement(By.id("id1")));
</code></pre>

This is type-safe, efficient, refactorable, and much more flexible than reflection (since your consumer can do whatever it wants with the element, not limited to a single method call without any argument. Like for example, enter some text in a text field)

blocks|key|4348595|text|最简单的方法是使用反射：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4348596|String+command+=+"click";
WebElement+element+=+driver.findElement(By.id("id1"));

Method+method+=+WebElement.class.getMethod(command);
method.invoke(element);|code-block|syntax|javascript|4348597|如果您还想使用反射调用By.id，那么您可以这样做：|offset|length|style|CODE|4348598|String+command+=+"click";
String+id+=+"id";

Method+byMethod+=+By.class.getMethod(id,+String.class);
WebElement+element+=+driver.findElement((By)+byMethod.invoke(null,+"id1"));

Method+method+=+WebElement.class.getMethod(command);
method.invoke(element);|4348599|entityMap^0|0|0|B|5|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

The simplest way to do this is to use reflection:

<pre><code>String command = "click";
WebElement element = driver.findElement(By.id("id1"));

Method method = WebElement.class.getMethod(command);
method.invoke(element);
</code></pre>

If you also want to call <code>By.id</code> with reflection, then you can do this:

<pre><code>String command = "click";
String id = "id";

Method byMethod = By.class.getMethod(id, String.class);
WebElement element = driver.findElement((By) byMethod.invoke(null, "id1"));

Method method = WebElement.class.getMethod(command);
method.invoke(element);
</code></pre>

blocks|key|4348910|text|在设计方面(也许可以肯定地进一步优化和抽象)，您可以定义一个Enum，让我们将其命名为Action：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4348911|public+enum+Action+{
+CLICK,
+SENDKEY,
+etc
}|code-block|syntax|javascript|4348912|然后在你的代码中这样做：|4348913|Action+action+=+<input>;
//+find+the+element
WebElement+element+=+driver.findElement(By.id("id1"));
switch(action)+{
++++case+CLICK:
++++++++element.click();
++++++++break;
++++case+SENDKEY:
++++++++element.sendKey();
++++++++break;
++++...
++++default:
++++++++System.out.println("Undefined+action");
++++++++break;
}|4348914|entityMap^0|U|4|17|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

In terms of design(and probably this can be further optimized and abstracted for sure), you can probably define an <code>Enum</code>, let us name it <code>Action</code> as:

<pre><code>public enum Action {
 CLICK,
 SENDKEY,
 etc
}
</code></pre>

In your code then do:

<pre><code>Action action = &lt;input&gt;;
// find the element
WebElement element = driver.findElement(By.id("id1"));
switch(action) {
 case CLICK:
 element.click();
 break;
 case SENDKEY:
 element.sendKey();
 break;
 ...
 default:
 System.out.println("Undefined action");
 break;
}
</code></pre>

blocks|key|4348954|text|看起来你正在尝试构建一个关键字驱动的框架。老实说，如果听到任何成功的故事，我都会非常惊讶。总是想知道这种框架的真正目的是什么？谁会用它呢？管理者、手动QAs还是利益相关者？对我来说，让非技术人员参与测试自动化活动是没有意义的。任何自动化都需要良好的技术技能(包括编程和devops)。否则，失败的概率会很高。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4348955|无论如何，你的问题更多的是关于strings与functional+interfaces映射，或者非常智能的反射用法。但主要的问题是，您为此选择了错误的API输入。下面这行代码：|offset|length|style|CODE|4348956|driver.findElement(locator).doSmth();|code-block|syntax|javascript|4348957|是一种正确的失败方式，因为findElement使用隐式等待。当你面对NoSuchElementException+/+StaleElementReferenceException时，我100%25地肯定你会开始全局重构/修改实现的方法。|4348958|常识建议在ExpectedConditions中使用流畅的等待。但这将使您的任务更加复杂，因为除了定位器和操作之外，您还必须考虑条件，这些条件应该由用户提供。|4348959|从技术角度来看，我会先创建通用的包装器来封装低级的WebDriver调用。与原始调用相比，映射或反映这样的函数会容易得多。例如，预期的条件可以在枚举级别上隐藏：|4348960|@Getter
@RequiredArgsConstructor
public+enum+WaitCondition+{

++++visible(ExpectedConditions::visibilityOfElementLocated),
++++enabled(ExpectedConditions::elementToBeClickable);

++++private+final+Function<By,+ExpectedCondition<WebElement>>+type;
}|4348961|通过调用WaitCondition.valueOf("visible")可以很容易地检索到所需的常量，其中输入的字符串可以从外部传递。|4348962|常见的API包装器可能如下所示：|4348963|protected+void+click(By+locator)+{
++++click(locator,+enabled);
}

protected+void+click(By+locator,+WaitCondition+condition)+{
++++waitFor(locator,+condition).click();
}

private+WebElement+waitFor(By+locator,+WaitCondition+condition)+{
++++return+wait.until(condition.getType().apply(locator));
}|4348964|这个线程中的其他人已经提供了映射/反射示例。只需注意:如果您更喜欢反射，我建议您查看jOOR库，它简化了这个过程。|4348965|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jOOQ/jOOR^0|0|F|7|N|L|0|0|D|B|Z|M|1O|U|0|5|I|0|0|0|4|W|0|0|0|16|4|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1G|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1H|8|@$D|1I|E|1J|F|G]|$D|1K|E|1L|F|G]|$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1O|8|@$D|1P|E|1Q|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1R|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1S|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1T|8|@$D|1U|E|1V|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1W|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|J|7|1X|8|@]|9|@]|A|$K|L]]|$1|10|3|11|5|6|7|1Y|8|@]|9|@$D|1Z|E|20|1|21]]|A|$]]|$1|12|3|-4|5|6|7|22|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

Seems like you're trying to build a keyword-driven framework. To be honest, I'd be very surprised to hear any successfull story on that. Was always wondering what's the real purpose of such kind of frameworks? Who gonna use it? Managers, manual QAs or stakeholders? For me it makes no sense to involve non-tech persons in test automation activities. Any automation requires good tech skills (including programming and devops). Otherwise, failure probability is quite high.

Anyway, your question is more about <code>strings</code> vs <code>functional interfaces</code> mapping, or very smart reflection usage. But the main problem is that you've chosen wrong API [inputs] for that. The following line:

<pre><code>driver.findElement(locator).doSmth();
</code></pre>

is a right way to fail, as <code>findElement</code> uses implicit waits. And I'm 100% sure that you'll start global refactoring / revising implemented approach, when you face with <code>NoSuchElementException</code> / <code>StaleElementReferenceException</code>.

Common sense suggests using fluent waits with <code>ExpectedConditions</code>. But it'll make your task even more complicated, as besides locators and actions you have to think about conditions, which should be supplied by the users.

From technical point, I'd create common wrappers first to encapsulate low-level WebDriver API calls. It'd be much easier to map or reflect such functions in comparison with raw calls. E.g. expected conditions could be hidden on enum level:

<pre><code>@Getter
@RequiredArgsConstructor
public enum WaitCondition {

 visible(ExpectedConditions::visibilityOfElementLocated),
 enabled(ExpectedConditions::elementToBeClickable);

 private final Function&lt;By, ExpectedCondition&lt;WebElement&gt;&gt; type;
}
</code></pre>

It'll be easy to retrieve required constant by calling e.g. <code>WaitCondition.valueOf("visible")</code>, where input string could be passed from outside.

Common API wrapper may look like the following then:

<pre><code>protected void click(By locator) {
 click(locator, enabled);
}

protected void click(By locator, WaitCondition condition) {
 waitFor(locator, condition).click();
}

private WebElement waitFor(By locator, WaitCondition condition) {
 return wait.until(condition.getType().apply(locator));
}
</code></pre>

Mapping / reflection examples were already provided by others in this thread. Just a note: if you prefer reflection, I'd recommend you to look at <a href="https://github.com/jOOQ/jOOR" rel="nofollow noreferrer">jOOR</a> library, which simplifies this process.

I have a requirement such that:

<pre><code>String command = "click"; // this can have value such as clear, getLocation, getSize, getTagName etc. 
WebDriver driver = new ChromeDriver(options); //creating a webdriver object
driver.findElement(By.id("id1")).click(); //Here I want "click" method should be called dynamically as per what I have stored in variable `command`.
</code></pre>

So, is there something possible like:

<pre><code>driver.findElement(By.id("id1")).&lt;something to call click()&gt;
</code></pre>

I have already looked at Reflection in Java, but that looked to me complex as per my requirement. Any pointers will be helpful!

Java: call a method with name stored in variable

Java

我有一个要求：String command = "click";   // this can have value such as clear, getLocation, getSize, getTagName etc. WebDriver driver = new ChromeDriver(options); //c...

问Java:使用存储在变量中的名称调用方法
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java:使用存储在变量中的名称调用方法EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java:使用存储在变量中的名称调用方法
EN