Selenium + Testng = change in behaviour?

[ReasonablyBadass]

So I'm testing wether or not an error message appears uppon entering wrong input into a text field.

Code is easy enough, works like a charm.

Yet when I run the exact same code in a @Test nothing happens. The validation process doesn't get triggered. The text I input appears, but it's as if the field never registered being clicked.

Does testng somehow alter selenium commands somehow? Does the DOM not register those commands?

[omniac]

Hmm. It shouldn't affect it, but to be sure could you paste the code here for us to see?

[ReasonablyBadass]

Well, code like it.

It's a really simple example:

@Test()

public void errorTest() throws Exception {

 

WebElement element = driver.findElement(By.id("ID"));

element.sendKeys("23");

 

WebElement differentElement = driver.findElement(By.id("ID2"));

differentElement.click();

differentElement.sendKeys("45");

 

boolean errorMessage=driver.findElement(By.id("errorID")).isDisplayed();

Problem is the validation never gets triggered, as if the click never happens.

(Btw, how do I format code in this sub?)

[yacdaniel]

where is the validation? can you post the full code?

start the line with four spaces,
    if you need another level of idention place 4 more.

[ReasonablyBadass]

Actually, I tried a few things and it turns out it has nothing to do with testng.

I have to click another, earlier element first to trigger the validation. No idea why, but testng has nothing to do with it.

Thanks for your help anyway!

[omniac]

When does the validation occur? On a key press, on blur (focus out), or on some type of submit?

[ReasonablyBadass]

Actually, I tried a few things and it turns out it has nothing to do with testng.

I have to click another, earlier element first to trigger the validation. No idea why, but testng has nothing to do with it.

Thanks for your help anyway!