🔧 test: improve user messages in DdevUtils validation tests

[Morgy93]

This pull request makes improvements to the unit tests for the DdevUtils class, focusing on making test assertions more precise and explicit. The main changes involve updating how user-facing error messages are validated and clarifying error types in assertions.

Test assertion improvements:

• Changed assertions in validateDdevTool tests to compare the returned userMessage directly to the expected full message, rather than just checking for substrings. This ensures that the error messages are exactly as intended. [1] [2]
• Updated the error type in the execDdev test's thrown error assertion to use a more specific type annotation ({ status: number; stderr: string }), improving type safety and clarity.

[Copilot]

Pull request overview

This pull request improves test assertions for the DdevUtils validation methods by making them more precise and explicit. The changes replace substring checks with exact string comparisons for user-facing error messages and improve type annotations for error handling tests.

Changes:

• Replaced substring assertions with exact string equality checks in validateDdevTool tests for better validation precision
• Added a more specific type annotation for error objects in execDdev test

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.