Tips and Tricks

How do I maintain so many failing UI tests?

Just click the "Save Results" button.

In other frameworks, UI tests break often and require a lot of tedious code changes. But IcuBlazor UI tests are interactive & largely decoupled from the UI-under-test. So maintaining a failing test only requires a button click!

Handle subtle image differences

Captured test images can vary slightly depending on the browser, user, or monitor settings. How can we create reliable tests under such subtleties?

  1. One answer is to crush all diversity! Just ensure your tests always run in the same environment (i.e. on the same browser, user, or monitor settings). This may seem draconian but it is very effective.

  2. Another solution is to embrace differences. Save test images in different folders for each environment. For example, to handle browser differences you can save images in a "Chrome\" or "Firefox\" folder. Just format CompareDiv()'s testName; e.g. set testName=Env.Browser+"\\"+testName.

Test images must be located under wwwroot/ so your browser can load them. But you may want to store them elsewhere. To do so, you can create a symbolic link (e.g. mklink /D link target) and set IcuConfig.TestDir=link. Now your images can be anywhere and accessible from wwwroot. (Note: creating a symbolic link will require admin privileges.)

Create Images for Documentation

It's handy to use your test images for documentation purposes. Usually, you will want to format your images in a consistent way and place them in a certain directory. Here's an example that uses CSS styles to add a border around document images and saves them in a docs folder.

<IcuTestDiv Suite="@this" Width="510">
    <div id="holder" style="border:5px solid #eee;">
        <MyAwesomeThing Args="setup1"/>
    </div>
</IcuTestDiv>

@code {
    public async Task Make_doc_image_setup1(Checker cx) {
        :
        await CompareDiv(cx, @"docs\awesome_setup1", "#holder");
    }

}

Running IcuBlazor from Commandline

Under samples see start_server.bat & run_tests.bat.

Support

If you have any questions or discover a bug or have a feature request feel free to open an issue.