test-timeclock

Automate end-to-end timeclock attendance testing with PASS/FAIL reports.

Updated Mar 30, 2025
One-click install
npx skills add https://github.com/j4xie/my-prototype-logistics --skill test-timeclock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-timeclock
Source: https://github.com/j4xie/my-prototype-logistics/tree/main/.claude/skills/test-timeclock
Command: npx skills add https://github.com/j4xie/my-prototype-logistics --skill test-timeclock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates testing of the timeclock/attendance features, including status checks, today’s records, clock-in/clock-out actions, and weekly/monthly stats.

Core Features & Use Cases

  • Attendance Flows: Validate clock-in, clock-out, and daily history retrieval.
  • Work Hours & Stats: Verify weekly and monthly time statistics aggregation.
  • Use Case: Ensure a new office location’s attendance flows correctly without manual steps.

Quick Start

Run the timeclock test suite: bash tests/api/test-timeclock.sh

Frequently Asked Questions about test-timeclock

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate testing for clock-in and clock-out workflows?

Automated attendance testing validates clock-in, clock-out, and daily history retrieval through end-to-end API testing against a local timeclock module. This Skill runs a test suite that covers login, token retrieval, endpoint interactions, and generates PASS/FAIL reports for your attendance flows.

Can I test attendance and work-hours tracking without manual verification?

Yes. This Skill automates functional testing of timeclock features including status checks, today's records, clock-in/clock-out actions, and weekly/monthly statistics aggregation, eliminating manual test steps for attendance modules.

What's included in timeclock testing for a new office location?

Testing covers login, status retrieval, daily records, clock-in, clock-out, duplicate clock-in prevention, and weekly/monthly time statistics. The Skill validates JSON payloads, API responses, and token handling to ensure attendance flows work correctly.

How does automated attendance testing handle duplicate clock-ins?

The test suite includes validation for duplicate clock-in scenarios, ensuring the timeclock module rejects or handles repeated clock-in attempts correctly and generates appropriate responses as part of functional requirement verification.

What environment setup is needed to run timeclock tests?

Tests run against a local timeclock module on localhost:10010 for factory F001. The test suite requires a local environment with API endpoint access and handles token retrieval, payload construction, and response parsing automatically.

Do I need to write custom test logic for attendance verification?

No. This Skill provides an automated test suite that validates attendance module functionality end-to-end, including API interactions, response validation, and report generation—no custom test code required.