Add preconditions

[sirkostya009]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @sirkostya009, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the handling of test case preconditions by moving from a simple string comment to a more robust precondition object. This change allows for greater flexibility, enabling users to define preconditions as standalone text or link to shared preconditions. Concurrently, the tool registration mechanism has been refactored to streamline how tool descriptions and input schemas are defined, ensuring better organization and maintainability of the codebase.

Highlights

• Enhanced Precondition Support: Introduced a dedicated precondition field for test cases, replacing the previous comment field. This new field allows for more structured precondition data, supporting both standalone text and references to shared preconditions.
• Tool Registration API Refactor: The server.tool calls have been updated to server.registerTool, and the arguments for tool descriptions and input schemas are now encapsulated within a single object, improving API consistency and readability.
• Updated Type Definitions: New TypeScript interfaces (TestPrecondition, TestPreconditionRequest) and updated existing ones (TestCase, CreateTestCaseRequest, UpdateTestCaseRequest) have been added to fully support the new structured precondition data model.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully introduces a more structured and flexible way to handle test case preconditions. The comment field has been deprecated in favor of a new precondition field, which can either reference an existing shared precondition by ID or provide standalone text. This is a significant improvement for managing test case metadata. The changes correctly update the tool registration methods from server.tool to server.registerTool and adjust the zod schemas and TypeScript interfaces (TestPrecondition, TestPreconditionRequest) to reflect these new capabilities. The deprecation of the old comment field and its replacement with precondition in the create_test_case and update_test_case tools, along with the corresponding type updates, are well-implemented. The JSONStringify utility usage has also been appropriately adjusted to align with these changes. Overall, the code is clean, well-structured, and effectively implements the new precondition functionality.

[satvik007]

It will be useful to implement https://github.com/Hypersequent/tms-issues/issues/2095 before merging this. But this PR looks good.

[sirkostya009]

@sirkostya009 so should i implement the rest in this pr or another one? they'd kinda conflict