Skill בדיקות ל-Automations ל-Claude

מתי להשתמש

"Testing", "QA", "Sample data", "Edge cases", "Workflow לא עובד", "Staging environment".

הוראות עבודה

1. Why Testing

Production failure = lost data, lost trust. Test before, not after.

2. Test Levels

א. Unit Test — Single Module

• Each step works in isolation.
• Sample input → expected output.

ב. Integration Test — End-to-End

• Full workflow runs successfully.
• Real (or simulated) data.

ג. Edge Case Test

• Empty data.
• Maximum sizes.
• Special characters.
• Unicode (Hebrew, Arabic).
• Null values.

ד. Regression Test

• After changes, old workflows still work.
• Critical workflows = automated regression.

3. Tool-Specific Testing

Zapier

• "Test trigger" — sample data from source.
• "Test action" — runs each step.
• Preview without committing.
• Replay from Zap History.

Make.com

• "Run once" — execute scenario manually.
• Inspect each module's input/output.
• History — full execution logs.

n8n

• "Execute workflow" — manual run.
• Step-through debugging.
• Mock data in nodes.

4. Sample Data Strategy

Real Data

• Pull from actual source (1-5 records).
• Pros: realistic.
• Cons: sensitive data risk.

Synthetic Data

• Generate fake records.
• Pros: safe, controlled.
• Cons: may miss real-world quirks.

Hybrid

• Real structure, fake values.
• Best of both.

5. Edge Cases — Always Test

• ✅ Empty array/string.
• ✅ Null / Missing field.
• ✅ Maximum size (long text, large numbers).
• ✅ Special characters ('", &, <, >).
• ✅ Unicode (Hebrew, Arabic, Emoji).
• ✅ Wrong data type (number where text expected).
• ✅ API timeout simulation.
• ✅ Rate limit response.

6. Staging Environment

Why

• Test in production-like environment.
• Don't affect real customers.

How

• Separate Zapier/Make accounts for staging.
• Tools' "sandbox modes" (Salesforce, HubSpot, Stripe).
• Test customer/data that's clearly marked.

7. Test Documentation

Per Workflow

Workflow: Lead Routing
Tests:
1. Standard lead → SDR pool ✅
2. Enterprise lead → AE direct ✅
3. Empty fields → graceful handling ✅
4. Hebrew name → no encoding issues ✅
5. Duplicate lead → idempotency ✅
6. Rate limit hit → retry works ✅

8. Pre-Production Checklist

• All happy paths tested.
• Edge cases covered.
• Error paths tested.
• Rate limit handling verified.
• Idempotency confirmed.
• Authentication refresh works.
• Alerts trigger on failure.
• Documentation updated.
• Team trained on monitoring.

9. Post-Production Monitoring

First 24 hours

• Watch error rate live.
• Sample some successful runs manually.
• Be ready to disable + rollback.

First week

• Daily review.
• Compare to expected volume.
• Check alerts firing correctly.

Long-term

• Weekly health check.
• Monthly audit.
• Quarterly regression test.

10. Common Bugs

❌ Field mapping wrong — first_name → last_name. ❌ Date format mismatch — MM/DD vs DD/MM. ❌ Timezone issues — UTC vs Israel. ❌ Encoding — Hebrew shows as ?????. ❌ Number format — 1,000.50 vs 1.000,50. ❌ Off-by-one — index 0 vs 1.

11. Israel Specifics

Test Hebrew Data

• Names: דנה כהן, חיים זוהר.
• Addresses: רחוב הרצל 5, תל אביב.
• Phone: 054-555-1234, +972-50-555-1234.

Test Hebrew + English Mix

• Common in Israeli data.

12. Automation of Tests

Concept

• Test workflow that runs other workflows with sample data.
• Validates output.
• Alerts on failure.

Tools

• Postman Collections for API workflows.
• n8n test workflows.
• Bash scripts for cron testing.

13. אסיים בהמלצה.

קלט נדרש

פלט צפוי

דגלים אדומים

• 🚨 No testing before production — Russian roulette.
• 🚨 Test on real customers — affects them.
• 🚨 No monitoring after deploy — unknown issues.
• ⚠️ Test only happy path — edge cases will hit.

הערות חשובות

• Zapier "Test" doesn't commit — safe.
• Make "Run once" = full execution — careful with destructive actions.
• Use staging accounts for risky workflows.

פרומפט לדוגמה

Critical workflow ב-Make. Test plan?

Workflow עובד ב-staging, נופל ב-prod. למה?

איך לבדוק Hebrew encoding ב-Zapier?

© 2026 Automation Expert Pro | גרסה 1.0.0