spotify-box
github-action
Our great sponsors
spotify-box | github-action | |
---|---|---|
17 | 4 | |
119 | 1,296 | |
- | 2.2% | |
4.1 | 9.0 | |
6 months ago | 8 days ago | |
JavaScript | JavaScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
spotify-box
- I made a spotify-box: Update GitHub pinned-gist to show your Spotify top tracks
- spotify-box: Update a pinned-gist to contain your top tracks on Spotify.
- spotify-box: Update GitHub pinned-gist to show your Spotify top tracks.
- spotify-box: Update a pinned-gist to show your Spotify top tracks
- I made a spotify-box: Update a pinned-gist to show your Spotify top tracks
- spotify-box: Update a pinned-gist to contain your top tracks on Spotify
github-action
-
Effective Test Strategies for Deployed NodeJS Services using LaunchDarkly Feature Flags and Cypress. Part2: testing
# .github/workflows/main.yml name: cypress-crud-api-test on: push: workflow_dispatch: # if this branch is pushed back to back, cancel the older branch's workflow concurrency: group: ${{ github.ref }} && ${{ github.workflow }} cancel-in-progress: true jobs: test: strategy: # uses 1 CI machine matrix: machines: [1] runs-on: ubuntu-20.04 steps: - name: Checkout 🛎 uses: actions/checkout@v2 # https://github.com/cypress-io/github-action - name: Run api tests 🧪 uses: cypress-io/[email protected] with: browser: chrome record: true group: crud api test env: CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }} LAUNCH_DARKLY_PROJECT_KEY: ${{ secrets.LAUNCH_DARKLY_PROJECT_KEY }} LAUNCH_DARKLY_AUTH_TOKEN: ${{ secrets.LAUNCH_DARKLY_AUTH_TOKEN }} LAUNCHDARKLY_SDK_KEY: ${{ secrets.LAUNCHDARKLY_SDK_KEY }} #{{ # Here we are running the unit tests after the e2e # taking advantage of npm install in Cypress GHA. # Ideally we install first, and carry over the cache # to unit and e2e jobs. # Check this link for the better way: # https://github.com/muratkeremozcan/react-hooks-in-action-with-cypress/blob/main/.github/workflows/main.yml - name: run unit tests run: npm run test
-
Run your Cypress Tests in a Github Workflow
For much more info regarding the Cypress Github Action, check out their detailed documentation. I'm just barely scratching the surface of its capabilities here.
- Teste automático para front-end
-
The 32+ ways of selective testing with Cypress: a unified, concise approach to selective testing in CI and local machines
Cypress maintains a very neat GitHub Action that makes CI usage convenient with custom parameters.
What are some alternatives?
lovelace-paper-buttons-row - Adds highly configurable buttons that use actions and per-state styling.
mongodb-github-action - Use MongoDB in GitHub Actions
youtube-to-anchorfm - An automation process to convert YouTube video into audio file and uploading it to Anchor.fm podcast
amazon-ecs-run-task - Runs an Amazon ECS task on ECS cluster
create-release - An Action to create releases via the GitHub Release API
cypress-and-jest - Cypress and Jest both with code coverage running unit tests
playstation-box - Update a pinned gist to contain your PlayStation stats
cypress-grep - Filter tests using substring
setup-ruby - An action to download a prebuilt Ruby and add it to the PATH in 5 seconds
floatly - An extension that adds a floating button for browser quick actions
cypress-skip-test - Simple commands to skip a test based on platform, browser or a url
git-cliff-action - GitHub action to generate a changelog based on the Git history