Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Enhancement: Cross-Engine Compatibility and Cross-Platform Conformance Tests

Open
#83 2 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@agentvivekkumar is already working on this.

Since Oct 10, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement Require Customer
Problem / motivation

As Don't Be Michael expands beyond Claude Code to support Codex, Gemini, and additional operating systems, differences in CLI behavior, authentication, streaming output, cancellation, and error handling could cause inconsistent behavior across engine and OS combinations.

Proposed solution

Introduce a shared engine conformance test suite that validates the expected execution lifecycle for every supported AI engine and operating system.

The suite would cover:

-- Engine startup and successful task execution.

-- Streaming output and completion reporting.

-- Missing credentials, authentication failures, and quota limits.

-- Cancellation, process termination, and cleanup.

-- Recovery from interrupted tasks where supported.

-- Consistent error reporting and capability detection across platforms.

Use mocked engine processes for deterministic unit tests, with optional integration tests for installed CLIs. Run the appropriate test matrix through CI on Windows, macOS, and Linux as platform support becomes available.

Screenshot, mockup or recording

No response

Alternatives considered

A provider-specific test suite for each AI engine was considered, but it would duplicate test logic and make it harder to maintain consistent behavior as new engines are added.

Relying only on manual testing was also considered, but it could miss regressions across different engine and operating system combinations.

A shared, provider-neutral conformance suite with mocked process responses and optional integration tests would provide repeatable validation without requiring paid API calls for every test.

Area

Other

Pre-flight
  • I attached a screenshot, mockup or recording above.
  • I searched existing issues and discussions, and this isn't a duplicate.
Dominant language
TypeScript
Stars
273
Forks
211
Avg merge
13h
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from agentvivekkumar/dontbemichael

All issues in agentvivekkumar/dontbemichael

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.