메뉴
Build or review test-app/ for AppsFlyer Cordova against the tooling test-app contract: .env, [AF_QA] logs, auto-run SDK order, afqa-cordova deep links, iOS af_qa_logs.txt. Use when implementing Phase 3 or reviewing test-app PRs.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/AppsFlyerSDK/appsflyer-cordova-plugin --skill cordova-test-app-contract명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Maps the AppsFlyer Cordova RC pipeline (RC prep, lint-test-build, E2E, npm publish, rc-smoke, promote) to workflow files in this repo. Use when editing rc-release, rc-smoke, promote-release, or lint-test-build; not for day-to-day feature work.
Run or triage AppsFlyer Cordova E2E/smoke via ./scripts/af-scenario-runner.sh, sibling E2E copy, smoke dir, and JSON reports. Use for local reproduction, CI log triage, or report summaries.
Maps AppsFlyer Cordova CI (android/ios E2E workflows, ENV_FILE, sibling copy, smoke scripts) to the tooling smoke/E2E story. Use when editing .github/workflows/*e2e*, rc-smoke (when added), or debugging scenario CI.
| name | cordova-test-app-contract |
| description | Build or review test-app/ for AppsFlyer Cordova against the tooling test-app contract: .env, [AF_QA] logs, auto-run SDK order, afqa-cordova deep links, iOS af_qa_logs.txt. Use when implementing Phase 3 or reviewing test-app PRs. |
| globs | test-app/**,.af-e2e/test-plan.json,.af-smoke/rc-test-plan.json |
test-app/)Use when:
test-app/ (www/, config.xml, native hooks if needed).[AF_QA] lines or iOS file log).Normative: appsflyer-mobile-plugin-tooling/contracts/test-app-contract.md.
| Item | Location |
|---|---|
| Widget / bundle id | com.appsflyer.qa.cordova — test-app/config.xml |
| JS entry | test-app/www/js/index.js (and www/index.html) |
| E2E execution | Sibling copy only — scripts/sync-test-app-e2e-copy.sh + scripts/e2e-cordova-build.sh; do not cordova build from in-repo test-app/ with file:.. (ENAMETOOLONG risk) |
.env (E2E sibling) | ../appsflyer-cordova-plugin-e2e/.env (CI: ENV_FILE secret) |
| Deep link scheme (plan) | afqa-cordova:// — must match deep_link_url entries in .af-e2e / .af-smoke JSON |
DEV_KEY, APP_ID from .env at runtime; never commit .env. Provide test-app/.env.example. On missing key, log [AF_QA][CONFIG] and fail fast per contract.[AF_QA] — e.g. [AF_QA][startSDK] result: SUCCESS, [AF_QA][CALLBACK][onInstallConversionData] ….shouldStartSdk: false / manual start pattern per Cordova plugin API → register onInstallConversionData, onAppOpenAttribution, onDeepLinking → pre-start APIs → log --- Pre-start auto APIs complete --- → startSdk() → post-start APIs → three events (af_demo_launch, af_purchase, af_content_view).[AF_QA] lines to Documents/af_qa_logs.txt (Cordova: small native plugin, hook, or cordova-plugin-file — see workplan §Phase 3). The scenario runner prefers this file on iOS because simctl log show often misses WebView console.log output.Plans poll / grep for lines including:
[AF_QA][startSDK] result: SUCCESS[AF_QA][AUTO_APIS] --- Auto run complete --- (or pre/post complete lines per plan JSON — keep spelling identical to .af-e2e/test-plan.json)Until the test app emits these, phase_1 will fail even when install/launch succeeds.
.af-e2e / .af-smoke config.*.env documentedstartSdk[AF_QA] strings match plan patterns exactlyafqa-cordova URL scheme on Android + iOSaf_qa_logs.txt implemented and flushed[AF_QA] prefix or plan regexes ad hoc.