Add Jest testing framework with comprehensive regex-focused unit tests for callsign.js

[Copilot]

This PR implements Jest as the testing framework for the callsign.js project and adds comprehensive unit tests with a primary focus on validating the core regex patterns that drive the library's functionality.

Changes Made

Testing Infrastructure

• Added Jest and jest-environment-jsdom as dev dependencies
• Configured Jest for ES6 modules and browser environment compatibility
• Added npm test and npm run lint scripts to package.json
• Created tests/ directory with organized test files

Unit Test Coverage (71 tests total)

Primary Focus: Regex Pattern Validation

SEARCH_REGEX Pattern Tests (tests/searchCallsigns.test.js)

• Comprehensive validation of the /([A-Z,\d]{1,3}\d[A-Z]{1,3}(?:\/\d)?)\s/ pattern
• Tests valid call sign patterns (single/double/triple letter prefixes)
• Tests portable indicators (e.g., W1ABC/3)
• Validates edge cases: whitespace handling, greedy matching, boundary conditions
• Tests invalid patterns that should NOT match
• Real-world call sign examples from multiple countries
• 50+ test cases covering all aspects of call sign detection

PARTS_REGEX Pattern Tests (tests/partsRegex.test.js)

• Comprehensive validation of the /([A-Z,\d]{1,3})(\d)([A-Z]{1,3})(?:\/(\d))?/ pattern
• Tests all capture groups: prefix (1-3 chars), area digit, suffix (1-3 letters), portable indicator
• Validates component extraction from call signs
• Tests greedy matching behavior with long prefixes
• Edge cases and boundary conditions
• 40+ test cases covering all parsing scenarios

Supporting Method Tests

getFlag Method Tests (tests/getFlag.test.js)

• Verifies correct conversion of ISO country codes (extracted via PREFIX_TABLE matching) to Unicode Regional Indicator Symbols
• Tests multiple country codes including US 🇺🇸, Sweden 🇸🇪, Germany 🇩🇪, Japan 🇯🇵, UK 🇬🇧, and Canada 🇨🇦
• Validates the mathematical transformation (character codes + 127397 offset)

getPhonetics Method Tests (tests/getPhonetics.test.js)

• Ensures accurate mapping of characters to phonetic alphabet equivalents for regex-parsed call signs
• Tests individual letters, digits, and complete call signs like W1AW → "Whiskey One Alfa Whiskey"
• Validates all A-Z letters and 0-9 digits according to ITU phonetic alphabet
• Handles edge cases including empty strings and undefined characters

Documentation Updates

• Added comprehensive Testing section to README.md emphasizing regex-focused approach
• Included clear instructions for running tests: npm test
• Documented regex patterns, test coverage, and file organization
• Explained the primary focus on regex validation

Usage

# Install dependencies
npm install

# Run all tests
npm test

# Run linting
npm run lint

Verification

All existing functionality remains intact as demonstrated in the test page:

The screenshot shows:

• Country flags correctly displayed before call signs (🇸🇪 🇺🇸 🇩🇪 🇯🇵 🇬🇧 🇦🇺)
• Phonetic information properly generated for accessibility
• Call signs highlighted with monospace formatting
• No regressions in existing behavior

✅ 71/71 tests pass
✅ ESLint validation passes
✅ Zero breaking changes
✅ Comprehensive regex pattern validation
✅ Complete requirements fulfillment

This implementation maintains the amateur radio community's philosophy of readable, educational code while adding robust regex-focused testing capabilities that validate the core patterns driving call sign detection and parsing functionality.

This pull request was created as a result of the following prompt from Copilot chat.

Set up Jest as a testing framework for the callsign.js project. Write initial unit tests for core functionalities, including:

1. getFlag Method: Verify it correctly converts ISO country codes into Unicode Regional Indicator Symbols.
2. getPhonetics Method: Ensure it accurately maps characters to their phonetic alphabet equivalents.
3. searchCallsigns Method: Test basic functionality for detecting and wrapping untagged call signs in a <call-sign> tag.

Include a package.json file with Jest as a dependency, and create a tests folder to store the test cases. Provide clear instructions for running the tests in the README.

This pull request was created as a result of the following prompt from Copilot chat.

Set up Jest as a testing framework for the callsign.js project. Write initial unit tests for core functionalities, including:

1. getFlag Method: Verify it correctly converts ISO country codes into Unicode Regional Indicator Symbols.
2. getPhonetics Method: Ensure it accurately maps characters to their phonetic alphabet equivalents.
3. searchCallsigns Method: Test basic functionality for detecting and wrapping untagged call signs in a <call-sign> tag.

Include a package.json file with Jest as a dependency, and create a tests folder to store the test cases. Provide clear instructions for running the tests in the README.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[phieri]

@copilot have the tests primarily focus on the regex codes

[Copilot]

@copilot have the tests primarily focus on the regex codes

Refactored the test suite to primarily focus on regex pattern validation. The tests now comprehensively validate:

SEARCH_REGEX (/([A-Z,\d]{1,3}\d[A-Z]{1,3}(?:\/\d)?)\s/) - 50+ test cases covering:

• Valid/invalid call sign patterns
• Prefix length variations (1-3 chars)
• Portable indicators
• Whitespace handling
• Greedy matching behavior

PARTS_REGEX (/([A-Z,\d]{1,3})(\d)([A-Z]{1,3})(?:\/(\d))?/) - New comprehensive test file with 40+ test cases covering:

• Component parsing (prefix, digit, suffix, portable)
• All capture groups
• Edge cases and boundary conditions

All 71 tests pass. Commit: e2d5a59