GitHub Actions - STRIPE_DEVICE_NAME
I'm trying to setup my e2e testing and CI/CD stuff on GitHub.
It's asking me for the enviroment variable "STRIPE_DEVICE_NAME" which according to this documentation "the device name for the CLI, visible in the Dashboard." - only I can't find it anywhere in the Stripe UI.
@kapa.ai
5 Replies
Hi @Gareth_Simpson. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources provided do not contain any information about the STRIPE_DEVICE_NAME environment variable or how to set it up for GitHub Actions, e2e testing, or CI/CD with Wasp or Open SaaS. The sources discuss Stripe integration, environment variables in Wasp, and some Stripe CLI usage, but do not mention STRIPE_DEVICE_NAME specifically or its configuration in the Stripe Dashboard.
If you need to set this variable, you may need to refer directly to the official Stripe CLI documentation or Stripe support, as the Wasp documentation and community discussions do not cover this detail.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Gareth_Simpson, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@kapa.ai - re GitHub Actions and e2e tests - can you help me with an overview?
Let me check the knowledge base for you again. One moment! :books:
----------------------
Certainly! Here’s an overview of how GitHub Actions and end-to-end (e2e) tests relate to Wasp, based on the available knowledge sources:
GitHub Actions & Wasp
- There is ongoing work and community interest in implementing a GitHub CI Action for Wasp apps, which would automate building and testing your Wasp project as part of your CI/CD pipeline. There is a related project at wasp-lang/deploy-action that you might find useful for deployment automation, though it may not cover e2e testing out of the box Implement a Wasp Github CI Action.
e2e Testing in Wasp
- Wasp itself does not yet have built-in support for backend or full-stack e2e testing, but the community has set up e2e tests using Playwright. These are used to test new releases of Wasp by running them on prepared Wasp apps to ensure everything works as expected. You can find examples and setup in the waspc/headless-test directory of the Wasp repository. If you need help setting this up, the Wasp team is open to assisting Discord support thread: experiences with testing the backend or e2e?.
- There is also discussion about the importance of e2e and blackbox testing for the Wasp CLI itself, to ensure reliability and prevent regressions. This includes running commands, modifying files, and validating outputs as part of CI/CD End-to-end blackbox testing of Wasp CLI commands.
Summary
- Frontend testing is officially supported in Wasp via Vitest.
- e2e testing (e.g., with Playwright) is possible and used by the Wasp team, but requires custom setup.
- GitHub Actions can be used to automate these tests, and there are community resources and actions in development to help with this.
If you need specific help setting up Playwright or integrating it with GitHub Actions for your Wasp app, the Wasp team and community are available to assist further.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Gareth_Simpson, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@Carlos @Vinny (@Wasp) - can I get a bit of direction here? I'm using OpenSaaS / vibing / n00bie - and I'm looking to get GitHub actions working, because the LLM has taken me in a direction to get playwright running on GitHub actions. What are you thoughts?
haven't done stripe, but i think that this is confusingly written on their part. my understanding is that the
STRIPE_DEVICE_NAME is a name you decide and set, what you want to name this device, and then it will show up in the stripe dashboard in the logs.
so if you're doing it for CI, you just make up a name and set it (e.g. STRIPE_DEVICE_NAME: github-actions-my-repo)
when you're checking the logs on stripe, some actions will be tagged as github-actions-my-repo so that you know the CI made them
does that make sense?