Validate Assertions

Example

[Test]
public void CommonActionsWithDesktopControls_Wpf()
{
    var calendar = App.Components.CreateByAutomationId<Calendar>("calendar");

    calendar.ValidateIsNotDisabled();

    var checkBox = App.Components.CreateByName<CheckBox>("BellaCheckBox");

    checkBox.Check();

    checkBox.ValidateIsChecked();

    var comboBox = App.Components.CreateByAutomationId<ComboBox>("select");

    comboBox.SelectByText("Item2");

    Assert.AreEqual("Item2", comboBox.InnerText);

    var label = App.Components.CreateByName<Label>("Result Label");

    label.ValidateIsVisible();

    var radioButton = App.Components.CreateByName<RadioButton>("RadioButton");

    radioButton.Click();

    radioButton.ValidateIsChecked(timeout: 30, sleepInterval: 2);

	Bellatrix.Assertions.Assert.Multiple(
        () => radioButton.ValidateIsChecked(timeout: 30, sleepInterval: 2),
        () => checkBox.ValidateIsChecked(),
        () => Assert.AreEqual("Item2", comboBox.InnerText));
}

Explanations

calendar.ValidateIsNotDisabled();
//Assert.AreEqual(false, calendar.IsDisabled);

We can assert weather the control is disabled. The different BELLATRIX desktop elements classes contain lots of these properties which are a representation of the most important app element attributes. The biggest drawback of using vanilla assertions is that the messages displayed on failure are not meaningful at all. This is so because most unit testing frameworks are created for much simpler and shorter unit tests. In next chapter, there is information how BELLATRIX solves the problems with the introduction of Validate methods. If the bellow assertion fails the following message is displayed: “*Message: Assert.AreEqual failed. Expected:. Actual:.*" You can guess what happened, but you do not have information which element failed and on which page. If we use the Validate extension methods, BELLATRIX waits some time for the condition to pass. After this period if it is not successful, a beatified meaningful exception message is displayed: "*The control should be disabled but it was NOT.*"

 var checkBox = App.Components.CreateByName<CheckBox>("BellaCheckBox");

checkBox.ValidateIsChecked();

Here we assert that the checkbox is checked. On fail the following message is displayed: “Message: Assert.IsTrue failed.” Cannot learn much about what happened. Now if we use the ValidateIsChecked method and the assertion does not succeed the following error message is displayed: “The control should be checked but was NOT.”

var label = App.Components.CreateByName<Label>("Result Label");
label.ValidateIsVisible();

See if the element is present or not using the IsPresent property.

var radioButton = App.Components.CreateByName<RadioButton>("RadioButton");
radioButton.ValidateIsChecked(timeout: 30, sleepInterval: 2);

By default, all Validate methods have 5 seconds timeout. However, you can specify a custom timeout and sleep interval (period for checking again).

Bellatrix.Assertions.Assert.Multiple(
        () => radioButton.ValidateIsChecked(timeout: 30, sleepInterval: 2),
        () => checkBox.ValidateIsChecked(),
        () => Assert.AreEqual("Item2", comboBox.InnerText));

You can execute multiple validate assertions failing only once viewing all results.

BELLATRIX provides you with a full BDD logging support for Validate assertions and gives you a way to hook your logic in multiple places.