hdflextest

This is a test harness for the HDflex API, a dental staffing/scheduling platform. It automates integration testing by creating test dental offices, professionals (hygienists), messages, and verifying CRUD operations across all endpoints. The tool authenticates via OAuth2, creates realistic test data using real Minneapolis dental office addresses, runs a comprehensive test suite (~45 tests), and automatically cleans up all created resources. It's designed for QA engineers and developers working on the HDflex platform to validate API functionality and catch regressions.

Built to automate manual API testing for the HDflex dental staffing platform during development. The extensive documentation (beginner's guides, quick reference, flow diagrams) suggests this was created to be shared with non-technical team members or clients who needed to validate API functionality without deep technical knowledge. The tool encodes knowledge about several API quirks (inconsistent response wrapping, undocumented required fields, real address validation), indicating it was built after encountering these issues in production integration work.

TypeScript with strict typing, Node.js CLI, Axios for HTTP requests, dotenv for configuration. Includes ESLint and Prettier for code quality. Custom test framework with typed assertions, result types, and detailed console reporting. No external test framework (Jest/Mocha) used—implements custom test orchestration and reporting.

Last active Nov 3, 2025 — 2 commits across 1 active day (spanning 0 days).

Developed in a single focused session on November 3, 2025. Only 2 commits across 1 day, but the codebase is substantial and polished with extensive documentation, suggesting most work was done locally before committing or this represents a snapshot of work from a larger context.

This is a complete, production-ready testing tool with extensive beginner-friendly documentation, comprehensive error handling, and real-world API quirk handling. The detailed guides and polished output formatting indicate it was built for actual use by a team. While there's minimal commit history, the sophistication of the implementation (custom test framework, detailed reporting, dependency-aware cleanup) and the focus on usability demonstrate this is a shipped internal tool rather than an experiment.