🟡 KANGAROO HEALTH
Technical Test
Tracking pengerjaan tes teknis dan technical assignment dari KangarooHealth.
💻 Technical Test
Status Tracker
Technical Test Status
Update section ini SETELAH kamu receive technical assignment dari KangarooHealth. typical timeline: 3-7 days untuk completion.
📥 Received Technical Assignment
| Field | Value |
|---|---|
| Date Received | [TANGGAL] |
| Deadline | [TANGGAL] |
| Duration | [X] days given |
| Format | [Take-home / Live coding / Both] |
| Language | [TypeScript / Python / Both] |
Assignment Details
┌─────────────────────────────────────────────────────────────┐
│ TECHNICAL ASSIGNMENT │
├─────────────────────────────────────────────────────────────┤
│ │
│ [Paste assignment details here] │
│ │
│ Requirements: │
│ 1. ... │
│ 2. ... │
│ 3. ... │
│ │
│ Deliverables: │
│ • ... │
│ • ... │
│ │
│ Evaluation Criteria: │
│ • ... │
│ • ... │
│ │
└─────────────────────────────────────────────────────────────┘Submission Tracker
| Requirement | Status | Notes |
|---|---|---|
| Code | ⬜ Not Started | |
| Tests | ⬜ Not Started | |
| Documentation | ⬜ Not Started | |
| README | ⬜ Not Started | |
| GitHub Repo | ⬜ Not Created |
Approach Framework
If Take-Home Assignment
Expected Format
Typical KangarooHealth technical assignment for QA:
- Build a small test framework demonstrating your approach
- Write tests for a sample application (they provide)
- Design test strategy for a hypothetical scenario
- Automate API testing with provided endpoints
Recommended Structure
kangaroohealth-technical-test/
├── README.md # Clear setup instructions
├── playwright.config.ts # Well-configured
├── tests/
│ ├── e2e/
│ │ └── example.spec.ts
│ └── api/
│ └── example.api.spec.ts
├── src/
│ └── [any helper code]
├── package.json
├── .gitignore
└── CI/
└── github-actions.yml # Bonus: working CI pipelineEvaluation Checklist
| Criteria | Weight | Your Score |
|---|---|---|
| Code Quality | 25% | /25 |
| Test Coverage | 25% | /25 |
| Framework Design | 20% | /20 |
| Documentation | 15% | /15 |
| CI/CD Integration | 15% | /15 |
| TOTAL | 100% | /100 |
Common Technical Test Formats
Format A: Build a Test Framework
Task: Build a small Playwright test framework for testing
a todo application.
Requirements:
• Page Object pattern implementation
• At least 3 E2E tests covering CRUD operations
• API tests for the same endpoints
• Working CI configuration
• README with setup instructions
Evaluation:
• Code organization
• Test maintainability
• Use of best practicesFormat B: Test an Existing App
Task: Write automated tests for [provided web application]
Requirements:
• Cover happy path and edge cases
• Include assertions for validation
• Handle async operations properly
• Add test data management
• Generate a test report
Evaluation:
• Test coverage
• Edge case handling
• Code clarityFormat C: Design Test Strategy
Task: Design a comprehensive test strategy for a
device-agnostic healthcare monitoring platform
Deliverables:
• Test pyramid diagram
• Test automation approach per layer
• Tools selection with justification
• CI/CD integration strategy
• Risk-based testing priorities
Evaluation:
• Strategic thinking
• Healthcare context awareness
• Practical implementationTips for Success
✅ DO
- Read all instructions carefully before starting
- Set up proper project structure (don't just hack something)
- Include README with clear setup/run instructions
- Add comments explaining your decisions
- Use Page Object pattern for E2E tests
- Make tests independent and parallelizable
- Include both positive and negative test cases
- Add a working CI pipeline (bonus points)
- Test your code before submitting
- Submit before deadline (not at the last minute)
❌ DON'T
- Rush without reading requirements
- Submit code that doesn't run
- Skip the README
- Hard-code test data (use fixtures)
- Forget to handle cleanup/teardown
- Ignore edge cases
- Leave commented-out code
- Use deprecated APIs
- Submit without running tests yourself
Submission Template
Subject: Technical Test Submission — Senior QA Automation Engineer
Hi [Name],
Please find my technical test submission below.
Repository: [GitHub Link]
Live Demo: [If applicable]
Time spent: Approximately [X] hours
Key decisions made:
1. [Why you chose certain approach]
2. [Trade-offs you considered]
3. [What you would improve with more time]
Looking forward to discussing my approach!
Best regards,
Faisal AffanPost-Submission
- Wait for feedback (typically 3-5 business days)
- Prepare to discuss your code choices in follow-up interview
- Note any improvements you thought of after submission
- If no response after 7 days, follow up politely
Action Items
- Receive technical assignment
- Clarify any questions before starting
- Set up project structure
- Implement solution
- Add documentation
- Test everything works
- Submit before deadline
- Send confirmation email
- Wait for feedback
Edit on GitHub
Last updated on