test: scenario 2 - long tests (16 min) before sonar scanner - #42
test: scenario 2 - long tests (16 min) before sonar scanner#42CristianAmbrosini wants to merge 1 commit into
Conversation
SummaryThis PR adds a 16-minute delay step to the SonarCloud workflow to test an external bot's behavior around check-run status watching. The new "Run long tests" step adds a 960-second sleep before the SonarQube Scan step, simulating a long-running test suite. The test validates that the bot correctly monitors check-run status while in_progress and doesn't abandon early, then proceeds to collect SonarQube analysis results after the tests complete. What reviewers should knowWhat changed: A single step was added to Why this matters: This is an integration test scenario designed to verify that bot automation (external to this repo) correctly handles long-running GitHub check-runs. The sleep ensures the workflow stays in progress for 16 minutes, allowing the bot to demonstrate it won't time out or abandon the check-run prematurely. What to check: The workflow change is minimal and intentional—the goal is to observe the bot's behavior during execution, not to review the workflow logic itself. The SonarQube Scan step remains unchanged and will run after the tests complete, at which point the bot should collect the analysis results.
|
SonarQube reviewer guide
|
![sonar-review-dev18[bot]](https://avatars.githubusercontent.com/in/3054993?s=60&v=4){kind=small}
1 participant
Testing check-run watching: tests take 16 min before sonar scanner step. Bot should wait for the check run to complete (status: in_progress), NOT abandon early. After tests pass and scanner runs, bot should get SQC analysis.