Add listEC2Runners verification to maximum runners test

[Copilot]

The test 'calls publishRetryMessage even when maximum runners is reached' was missing verification that listEC2Runners is called when checking runner limits.

Changes

• Added assertion to verify listEC2Runners is called with correct parameters when RUNNERS_MAXIMUM_COUNT='0'
• Used toHaveBeenCalledWith matcher for consistency with modern Vitest practices

According to the scale-up logic (scale-up.ts:370-371), when maximumRunners is not -1, listEC2Runners must be called to get the current runner count. The test now verifies this behavior occurs as expected:

expect(listEC2Runners).toHaveBeenCalledWith({
  environment: 'unit-test-environment',
  runnerType: 'Org',
  runnerOwner: TEST_DATA_SINGLE.repositoryOwner,
});

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None