QAF with 4.0.0-RC3 and selenium 4.25.0 – When using QAF 4.0.0-RC3 with Selenium 4.25.0, the QAFWebComponent web element does not store the updated value; instead, it retains the old value. This issue does not occur with QAF 3.1.0. #462
Description
QAF Version
QAF with 4.0.0-RC3 and selenium 4.25.0
the QAFWebComponent web element does not store the updated value but retains the old value.
Expected behavior
The variable updatedText should store the updated value.
Actual behavior
The variable updatedText retains the old value instead of storing the updated one. This behavior is seen in components only.
Is the issue reproducible on runner?
- QAS
- Maven
- Gradle
- [] Ant
- Eclipse
Test case sample
public class TestComponent extends QAFWebComponent {
public TestComponent(String locator) {
super(locator);
// TODO Auto-generated constructor stub
}
@findby(locator = "someValidLocator")
private QAFWebElement testElement;
public void getextValue () {
String initText = testElement.getText(); // initText get the value say TextValue111
testElement.click(); // This updates the element-testElement and getText value updates to say TextValue222. (Locator is unchanged)
//
String updatedText = testElement.getText(); //updatedText still gets TextValue111 instead of TextValue222
}
}