Test failing in build agents.

[ibierut]

Hello.
According to this message, I have prepared a test sample and component that are having problems passing tests in build agents.

bUnit sample.zip

[egil]

Thanks, @ibierut. Can you provide a quick explanation of the sample you have submitted? There are quite a few files in there, so would like to know what to look for and what is what.

[ibierut]

Thank @egil for your quick response.

In zip file from the first post, we have two components: DataSchema and DataSchemaFromSourcePanel. Additionally, there are two files required to run these components: Toolbar folder and the file fix.cs.
These components are almost identical, but DataSchemaFromSourcePanel has two more buttons. You can see how they look in the images below:
DataSchema:

DataSchemaFromSourcePanel:

Both components use the same tests from file DataSchemaBaseTests.cs. I wrote this test using the page object design pattern, so I have several folders. I put all the steps/bUnit actions in the file DataSchemaComponent, so you can also check this file.

To make it easier, I ran my tests again with self-hosted agent.

You can see that tests passed five times, but then test: DataSchemaFromSourcePanelTests.DataSchema_AddAndUpdateButtons_AddDataInLastRow failed.
The error message was:
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'index')

I made a short GIF that demonstrates how these components and tests work.

This behavior is random and in another run, a different test could fail.

[egil]

I will take a look as soon as possible. Very busy at work right now, so no promises.

[egil]

Hi @ibierut, appreciate your patience.

Unfortunately, I cannot run the code locally, I do not have a Syncfusion license. But a few general observations:

1. In DataSchemaComponent.ClickAddButton and others you call the Click method followed by a call to the Render method. That is redundant. After an event handler has been invoked, your component should automatically re-render. Calling Render again causes another unnecessary render.
2. Your test is very tied to SfGrid and how that works. You could consider substituting that component out during testing and instead test that your usage of it is as expected (passing in the right parameters, etc.)
3. The test in your screenshot that does fail, fail because the rowCellsInLastRow does not contain the expected number of rows. Perhaps you need to change line 210 in ChangeValueInCell to var rowCellsInLastRow = _cut.WaitForElements(Selectors.LastRowCells); instead.

Hope this helps.

[ibierut]

I found a way for my tests to pass in the pipeline. I created a template with separate task for each component.
Thank @egil for Your help.