Generate unit tests from a repository, ZIP, or code

• Repository, ZIP, or code: The project materials required to identify the implementation, test framework, file structure, configuration, and existing testing conventions.
• Target code: The file, function, class, module, or component for which unit tests should be generated.
• Expected behavior or known bug: Requirements, expected results, failure conditions, or a bug to cover when available. If none are supplied, the prompt uses the code’s current observable behavior as the test basis.

Generate unit tests for the supplied repository, ZIP, or code.

TASK:
Inspect the supplied materials and create focused unit tests for the specified code.

INSTRUCTIONS:
- Identify the language, test framework, test runner, file structure, and existing testing conventions from the supplied materials.
- Use neighboring tests as the primary reference for naming, setup, fixtures, mocks, helpers, and assertions.
- Use supplied requirements or expected behavior as the test basis. If none are supplied, test the code’s current observable behavior and state that this is the basis.
- Cover the relevant normal, invalid-input, boundary, error, state-change, and side-effect cases.
- Test observable behavior rather than private implementation details.
- Keep tests focused, fast, isolated, deterministic, and runnable in any order.
- Reuse existing project test utilities and isolate external dependencies with the project’s established mechanisms.
- Add the tests in the correct project location and avoid duplicating existing coverage.
- Limit changes to test files. If correct testing requires a production-code, configuration, or dependency change, report it before expanding the scope.
- If a required project detail cannot be determined from the supplied materials, ask one precise question before writing the tests.
- Run the narrowest supported test command when execution is available. Report only the actual result.

OUTPUT:
1. Target test file path
2. Complete test code
3. Test command
4. Execution result: Passed / Test failure / Execution blocked / Not run
5. Exact failure evidence or reason when the result is not Passed

MATERIALS:
"""
Repository, ZIP, or code:
[Attach or paste the materials.]

Target code:
[Identify the file, function, class, module, or component to test.]

Expected behavior or bug to cover:
[Add when available.]

Constraints:
[Add relevant project constraints.]
"""