BUnit tests work locally but not on build agent

[saalocin]

Locally I have unit tests using BUnit to test my pages and components.

Locally it works perfectly but on the build server it fails to find the component with FindComponent method.

Am I missing a install on the build agent to be able to run this type of test on the agent?

[linkdotnet]

Hey,

without a specific test case it is hard to tell. But often times this observed behavior is explained due to asynchronous code, that isn't awaited property.
The reason is that your local machine, most often, is far more performant than any CI Runner.

For more information, check out: https://bunit.dev/docs/interaction/awaiting-async-state.html

[saalocin]

specifically its this line:
var activeCampaignsGrid = renderedComponent.FindComponent<TelerikGrid<ReferralCampaign>>();

Locally it can find this component, but on the server it fails with error:

  Error Message:
   Bunit.Rendering.ComponentNotFoundException : A component of type TelerikGrid`1 was not found in the render tree.

More context - currently the tests are in a .cs file, when I move it to .razor file the tests are ignored by the build agent, but locally its NOT ignored and works perfectly.

[linkdotnet]

It is hard to debug your issue without any code. And the second issue seems independent from your first.

Regarding ComponentNotFoundException. When and how does your component come into play?
Is it populated after some data is loaded inside OnInitializedAsync or similar life-cycle methods? If so, I would recommend to check out the link provided above.

Also Telerik provides their own TestContext implementation: https://github.com/telerik/blazor-ui/blob/master/testing/bUnit-justmock/Telerik.Blazor.BUnit.JustMock/Common/TelerikTestContext.cs

You might want to lean towards that to debug your issue.

[saalocin]

All data are mocked and no I/O operation is performed to get data.

I use the OnParametersSetAsync method to set data.
I also added a public bool OnParametersSetExecuted = false; which I wait on like renderedComponent.WaitForState(() => renderedComponent.Instance.OnParametersSetExecuted);. But still it fails on the CI server.

[linkdotnet]

Without the component under test (simplified) and the test, it is really hard to help.
Could you provide an example? Also it could be that Telerik components are using asynchronous operations.

[saalocin]

I removed the async life cycle event for the test and doing a FindComponent<PageTitle>(); and this is also failing.
its not something with telerik nor the data.
I am running out of ideas

[saalocin]

after some modifications from recommendations from above the current test is:

 public class Tests: TelerikTestContextWithActualRoot
 {
     [Fact]
     public void Testss()
     {


         //Act
         var renderedComponent = RenderComponent<Component>(
             );

         var selector = "tbody";
         renderedComponent.WaitForElement(selector);

Locally it works, on the agent it fails with:

Error Message:
   Bunit.Extensions.WaitForHelpers.WaitForFailedException : The CSS selector and/or predicate did not result in a matching element before the timeout period passed. Check count: 1. Component render count: 1. Total render count: 4.
---- Bunit.ElementNotFoundException : No elements were found that matches the selector 'tbody'

[saalocin]

Been playing with .Markup
The result is a bit strange on the build server.
Markup is empty:

            var renderedComponent = RenderComponent<TestPage>(
                );

            var markup = renderedComponent.Markup;

Markup is not empty: (the only change is TelerikButton)

            //Act
            var renderedComponent = RenderComponent<TelerikButton>(
                );

            var markup = renderedComponent.Markup;

Am I missing something on my TestPage to make it compatible somehow?

[saalocin]

I have found the issue.
In the pipeline we use sonaqube (SonarQubePrepare@4), if I remove this step everything works as expected.

I have no idea what is the root cause yet, but at least I can confirm its not bunit, telerik or the my tests :)

[linkdotnet]

Nice! Maybe pinging @andrei-epure-sonarsource might shed some light. He is one of the devs of SonarSource, that develop SonarQube.

Hey @andrei-epure-sonarsource - can you point to a direction where @saalocin could file a report?

[andrei-epure-sonarsource]

@saalocin please open a topic on https://community.sonarsource.com/c/sq/10

If you can provide a minimal reproducer we'll be able to jump on the topic faster.

Please also share, if possible, the YML commands you use, SQ version, OS version, Scanner for .NET version, MSBuild / dotnet version etc.

If you can provide a binlog for the build or diagnostics logs, it will help us (please make sure to redact and private info from the logs before, as it's a public forum).

And also the verbose logs of the SonarQubePrepare@4 step - add

 extraProperties: |
        sonar.verbose=true

to the yaml.

Thanks!

[saalocin]

Thanks @andrei-epure-sonarsource I will try to get a reproducer going

My current work around is to do a - task: DotNetCoreCLI@2 build before - task: SonarQubePrepare@4, somehow this allows the tests (the test build again) to run and execute normally. If I move this build step after - task: SonarQubePrepare@4 it fails.

I am running into - task: SonarQubeAnalyze@4 issues now. This worked before I started creating tests with bunit.

All this is strange to me, and days like this it feels like I have no idea what I am doing :)

[saalocin]

Even though its a old issue, I want to share the fix.

After we upgraded sonarqube to latest version, after that everything worked as expected.