Fix wrong expected panic string in token_tests.rs test_transfer_from_expired_allowance

[DeFiVC]

What

The test test_transfer_from_expired_allowance in tests/unit/token_tests.rs expects #[should_panic(expected = "allowance expired")] but the actual panic message is different.

Why

When an expired allowance is used, the contract emits an allowance_expired event and continues execution. The actual panic comes from get_allowance returning 0, followed by the "insufficient allowance" panic. The expected string will never match, so the test doesn't verify what it intends.

Scope

• Update the #[should_panic(expected = "...")] attribute to match the actual panic string
• Verify the test now correctly catches the intended behavior

Technical Context

• File: tests/unit/token_tests.rs (line ~205)
• The transfer_from function flow: check expiry → emit event → get allowance (returns 0) → panic with "insufficient allowance"

Acceptance Criteria

• #[should_panic(expected = "...")] matches the actual panic string
• Test passes with cargo test
• Test still verifies the intended behavior (expired allowance rejection)

[EstherIkechukwu]

I have gone through the description expect a pr in less than 12hrs

[EstherIkechukwu]

I have gone through the description expect a pr in less than 12hrs

[Waffiyyi]

@Waffiyyi has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to work on this issue. Please assign this to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Waffiyyi to this issue.

[Mayorlay]

@Mayorlay has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello please This issue aligns well with my experience. I can work on it and submit a polished PR for review

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mayorlay to this issue.

[SHEROSE0]

@SHEROSE0 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi dear maintainer, I'm ready to work on this has I've read through the description please kindly assign it to me and I'll deliver it promptly. Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SHEROSE0 to this issue.

[Gabugo-tech]

@Gabugo-tech has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Can I get this please, I will be submitting pr soon

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Gabugo-tech to this issue.

[TechBroAfrica]

@TechBroAfrica has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, i would love to work on this issue, kindly assign to me, Thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TechBroAfrica to this issue.

[OmniZlatoon]

@OmniZlatoon has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

My field of work. Please assign me the issue maintainer sir.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OmniZlatoon to this issue.

[drips-wave]

Congratulations, @SHEROSE0! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @SHEROSE0: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊