Toolverse
All skills
Testing

apollo-ci-integration

by jeremylongshore

Configure Apollo.io CI/CD integration.\nUse when setting up automated testing, continuous integration,\nor deployment pipelines for Apollo integrations.\nTrigger with phrases like \

Installation

Pick a client and clone the repository into its skills directory.

Installation

Quick info

Author
jeremylongshore
Category
Testing
Views
1
GitHub repo

About this skill

Configure Apollo.io CI/CD integration.\nUse when setting up automated testing, continuous integration,\nor deployment pipelines for Apollo integrations.\nTrigger with phrases like \

How to use

  1. Przygotuj wymagane elementy: repozytorium GitHub z włączonymi Actions, klucz główny API Apollo oraz token sandbox, Node.js w wersji 18 lub wyższej.

  2. Dodaj sekrety do GitHub Actions, uruchamiając polecenia: najpierw ustaw APOLLO_API_KEY dla testów integracyjnych na gałęzi main, następnie APOLLO_SANDBOX_KEY dla bezpiecznych testów na staging. Oba sekrety przechowywane są w ustawieniach repozytorium.

  3. Utwórz plik workflow Apollo CI w katalogu .github/workflows/apollo-ci.yml. Workflow powinien uruchamiać się na push do main i pull request. Skonfiguruj go do uruchomienia na ubuntu-latest z Node.js 20.

  4. Dodaj kroki do workflow: checkout kodu, setup Node.js z cache npm, instalacja zależności (npm ci), linting, typecheck oraz uruchomienie testów (npm test). Testy jednostkowe będą używać MSW mocki, co oznacza zero rzeczywistych wywołań API.

  5. Dla testów integracyjnych na gałęzi main użyj APOLLO_API_KEY. Dla testów na pull request i staging użyj APOLLO_SANDBOX_KEY, który zwraca dane testowe bez konsumowania kredytów.

  6. Wdróż workflow i obserwuj wyniki w zakładce Actions repozytorium. Każdy push i pull request będzie automatycznie testowany zgodnie z konfiguracją.

Related skills

playwright-browser-automation

by lackeyjb

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test

Testing
13130

test-cases

by cexll

This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering

Testing
2862

go-dev-guidelines

by jumppad-labs

This skill should be used when writing, refactoring, or testing Go code. It provides idiomatic Go development patterns, TDD-based workflows, project structure conventions, and testing best practices using testify/require and mockery. Activate this skill when creating new Go

Testing
1190

ad-creative

by alirezarezvani

When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or

Testing
2863

powershell-windows

by davila7

PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.

Testing
1074

pair-trade-screener

by tradermonty

Statistical arbitrage tool for identifying and analyzing pair trading opportunities. Detects cointegrated stock pairs within sectors, analyzes spread behavior, calculates z-scores, and provides entry/exit recommendations for market-neutral strategies. Use when user requests pair

Testing
994