BUG: CCIP router address assertion fails on local Hardhat network

[dhruvi-16-me]

Is there an existing issue for this?

• I have searched the existing issues

Issue Description ✍️

📌 Describe the Bug

While running the test suite on a fresh local Hardhat setup, one of the ElectionFactory deployment tests fails due to a CCIP router address mismatch.

The failure seems to occur because the test expects a specific router address, which does not match the router deployed or mocked on a local Hardhat network.

🚨 Actual Behavior

Running npx hardhat test on a local Hardhat network causes the following test to fail:
ElectionFactory → Deployment → "Should set the ccip receiver router"
The assertion compares two different router addresses and fails, even though the contract deployment itself succeeds.

🎯 Expected Behavior

On a local Hardhat network, the test should either:

• use the locally deployed / mocked CCIP router address, or
• be skipped or handled differently if it is intended only for testnet or live environments.

📷 Screenshot

💡 Suggestions

I’m not sure what the preferred approach is here, but possible options could be:

1. conditionally skipping CCIP-related tests on local Hardhat networks, or
2. adjusting the test setup to use the locally deployed / mocked router.

Record

• I have synced all my node versions as mentioned in the project
• I am using the same version of npm as is the project
• My current branch is in sync with the development branch
• I want to work on this issue

[Himanshukumar2211]

I reproduced this issue locally on Hardhat. The deployment test fails because the assertion compares the router address against a fixed testnet value, while Hardhat deploys a mock router dynamically.

This mismatch also explains why the cross-chain voting test later reverts with InvalidRouter, since the contract is validating against a different router than the one actually sending the message.

Between the two possible approaches:
• Skipping CCIP-related tests on Hardhat would hide real logic and reduce local coverage.
• Adjusting the test setup to bind assertions to the locally deployed/mock router keeps the test environment-agnostic and preserves CCIP validation.

The second approach seems preferable, as it fixes the root cause while keeping the tests meaningful across Hardhat, CI, and testnet environments.

If @dhruvi-16-me is already working on this, I’d be happy to collaborate. Otherwise, I’d be glad to take this up if the maintainers feel it’s appropriate to assign it to me.

[dhruvi-16-me]

Hey @Himanshukumar2211 I am already working on this.

[Himanshukumar2211]

Thanks @dhruvi-16-me for the update! Looking forward to the fix 👍

[harshkumarrai]

Hi @dhruvi-16-me , just checking in are you still actively working on this?
If not, I would be happy to take it up or help with a follow up PR. Let me know 👍

[dhruvi-16-me]

@harshkumarrai yeah working