Either I'm doing this wrong or it's a bug

[DavidThielen]

I am very very new to bUnit so I may be doing this wrong. This code was working up until 2 days ago. No changes but I did do a get updates on NuGet. However, reverting back on bUnit, still a problem. I am on .NET 8 so it might be a .NET 8 update. Anyways (also on Stack Overflow), here's the question/bug:

This is for a pretty simple page. I use DevExpress and emailTextBox is a DxTextBox.

This is successful

var emailTextBox = allTextBoxes.Single(x => x.Instance.InputId == "email");

emailTextBox.TextEditChange("");
button.Click();
var li = renderedComponent.Find("li.validation-message");
Assert.NotNull(li);
Assert.Equal("Your Email is required", li.InnerHtml);
Assert.Equal("", pageModel.Email);

Then this code immediately follows - and fails.

emailTextBox.TextEditChange("bogus");
button.Click();
li = renderedComponent.Find("li.validation-message");
Assert.NotNull(li);
Assert.Equal("The Email field is not a valid e-mail address.", li.InnerHtml);
Assert.Equal("bogus", pageModel.Email);

The problems are:

1. The error message it finds is the message for an empty field.
2. pageModel.Email is "".
3. In the debugger I look at emailTextBox.Text and it is "".

Is TextEditChange() not the right way to set the value in DxTextBox?

Update:

And sometimes randomly the above 2nd test passes, but then the next test, which is similar, fails. These tests assume that not only the value is being set, but that the and have then run.

Update 2:

The following works:

emailTextBox.TextEditChange("bogus");
button.Click();
renderedComponent.Render();
li = renderedComponent.Find("li.validation-message");
Assert.NotNull(li);
Assert.Equal("The Email field is not a valid e-mail address.", li.InnerHtml);
Assert.Equal("bogus", pageModel.Email);
Is it required to call renderedComponent.Render() after the TextEditChange/Click?

[egil]

I dont know DevExpress components, but if things are working sometimes, then you may have changes showing up asynchronously.

Look at renderedComponent.WaitForElement("li.validation-message") instead of Find in these cases. There are also WaitForAssertion, WaitForState and WaitForElements.

[DavidThielen]

In this case, there is no component appearing or disappearing. All that changes is the content of that component. So, do you think the solution for my issue here may be that instead of setting up a page, and then testing 4 different bad emails, one after the other, instead I need 4 tests where each starts with an empty , gets the one bad value, asserts that, then done.

thanks - dave

[linkdotnet]

Well, you can use data-driven tests.
Ideally, one test represents one logical assertion. That makes at least one test for a good case and one for a failing case.

Also to your question: It seems you are using validation - Your model will not be updated, when the validation fails, not?
Therefore in your described case, you will not see bogus in your model class.