How We Test Our Tools
A completely factual overview of automated tests, unit tests, and runtime verification executed on Khalasna.
Last Updated: October 2026
Trust requires absolute honesty about what is actually tested and what is not.
This page describes ONLY things that are genuinely implemented in our repository: our automated test suite, which categories have unit test coverage, and the exact software runtimes and browser environments used for validation.
11. Automated Test Suite (npm test)
Khalasna includes an automated test runner built with Node.js's native test engine (node:test and node:assert). You can run this test suite in our repository using the command 'npm test'.
Our tests run in milliseconds during development and continuous integration to catch regressions before deployments.
22. Unit Test Coverage for Mathematical Tools
Automated unit tests (located in tests/math-tools.test.js) test calculation logic against verified mathematical cases:
• Loan Amortization: Verifies fixed-rate monthly payments, total paid, and interest for multi-year loans and 0% edge cases. • Percentage Calculations: Tests all three primary calculation modes (P% of N, X is what % of Y, and percentage change). • BMI Calculations: Tests WHO metric and imperial weight/height conversions and category thresholds (underweight, normal, overweight, obese). • Age Calculations: Verifies exact calendar day differences, leap year handling, and multi-year offsets. • Currency Math: Verifies rate multiplier precision without floating-point artifacts. • Base Conversions: Tests UTF-8 text encoding and decoding, including special characters and Arabic strings.
33. Tier A UI Smoke Testing
Automated smoke tests (tests/smoke.test.js) verify our Tier A tool suite:
• Component Integrity: Validates that tools export compliant React components. • Bilingual Content: Checks that English and Arabic names and metadata exist for all Tier A tools. • Pre-rendered Workspaces: Confirms that production builds output complete server-side HTML workspaces containing interactive inputs, dropzones, and buttons without empty loading spinners.
44. Tested Runtimes & Browser Environments
To maintain strict factual accuracy, here are the exact environments used during testing:
• Runtimes: Node.js 20+ and Node.js 24 execution environments on 64-bit systems. • Browsers: Google Chrome and Chromium desktop engines during Next.js development and server pre-rendering.
We do not claim test coverage on physical devices or browsers that were not directly executed in our test pipeline.
55. Memory Stability & Large File Handling Tests
Client-side processing utilities are tested for RAM stability to prevent browser tab crashes during high-resolution image and multi-page PDF processing. We enforce proactive resource deallocation (including immediate URL.revokeObjectURL calls and Garbage Collection hygiene) to safeguard user device responsiveness.