Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • snowdrift snowdrift
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 198
    • Issues 198
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Custom issue tracker
    • Custom issue tracker
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Snowdrift.coopSnowdrift.coop
  • snowdriftsnowdrift
  • Issues
  • #27
Closed
Open
Created Jul 09, 2017 by Snowdrift.coop Import@snowdriftimportContributor

Stripe integration tests that actually hit the Stripe API

Using our account's test key will allow us to really communicate with Stripe and get real responses (albeit with imaginary money). We should use this to write tests about our Stripe assumptions.

  • Are we calculating the fee correctly?
  • Do the API commands we use exist and respond as we expect them to?

We don't want to spam the crap out of Stripe's servers, so access to the test key (and the ability to run integration tests) will be limited.

Edited Jul 14, 2021 by Stephen Michel
Assignee
Assign to
Time tracking