Skip to content

Add E2E tests for credential batch mint endpoint #637

Closed

Description

@DeFiVC

What

The credential batch mint endpoint has no E2E test coverage.

Why

Batch minting is an efficiency feature. The full request/response cycle should be tested.

Scope

In scope:

  • E2E tests for batch mint endpoint
  • Tests for partial failures
  • Tests for rate limiting

Out of scope:

  • Unit tests

Acceptance Criteria

  • E2E test file at tests/e2e/credential-batch-mint.test.ts
  • Tests cover batch mint
  • Tests cover partial failures
  • All tests pass

Technical Context

Source: src/modules/credentials/credential.routes.ts — /batch-mint endpoint

Activity

  1. MoscowDev commented on Oct 21, 2026

    @MoscowDev

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

    Dear Hiring Manager,

    I am writing to express my interest in any suitable opportunity available at Drips Issues. I am a dedicated and adaptable professional with experience in software development, problem-solving, and technology. I am eager to contribute my skills, learn from your team, and support the company's goals.

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

  2. Gentle842 commented on Oct 21, 2026

    @Gentle842

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

    Hi maintenaner, I can work on this,
    Pls kindly assign it to me

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

  3. Divine639700 commented on Oct 21, 2026

    @Divine639700

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

    Hi maintainer, I’d like to add E2E tests for the credential batch mint endpoint, covering successful batches, partial failures, and rate limiting. I’ll create tests/e2e/credential-batch-mint.test.ts and verify the full request and response flow.

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

  4. moon-code12 commented on Oct 21, 2026

    @moon-code12

    @moon-code12 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainers, I would like to express my interest in working on this issue. I have reviewed the issue description and understand the problem that needs to be addressed. My approach will be to investigate the existing codebase, identify the root cause, and implement a solution that follows the project's existing architecture and coding standards.

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

  5. emwulrd commented on Oct 21, 2026

    @emwulrd

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

    Hiii maintainer i will like to work on this issue

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

  6. Temibell commented on Oct 21, 2026

    @Temibell

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

    Hi Maintainer, I can fix this pls assign. ETA 5hrs

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

  7. drips-wave commented on Oct 21, 2026

    @drips-wave

    Congratulations, @emwulrd! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @emwulrd: 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 🌊

  8. added a commit that references this issue on Oct 22, 2026
    59ba8a5
  9. grantfox-oss commented on Oct 22, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @emwulrd's PR #753 was approved and merged by @DeFiVC.

    🏆 @emwulrd: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (710 total points). Track your full progress on GrantFox.

    👏 Great work, @emwulrd! Keep contributing to ChainLearnOfficial.

  10. drips-wave commented on Oct 22, 2026

    @drips-wave

    This issue has been completed by @emwulrd as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @emwulrd: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programenhancementNew feature or requestlow

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions