Add support for creating test cases

[hi-rai]

This fixes https://github.com/Hypersequent/tms-issues/issues/2141

[gemini-code-assist]

Summary of Changes

Hello @hi-rai, 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 test result upload commands (junit-upload and playwright-json-upload) by introducing the capability to automatically create test cases in QA Sphere for results that lack predefined markers. This feature, along with improved project code specification and updated API interactions, streamlines the integration of automated test results, making it easier to manage and map tests within the QA Sphere platform. The changes aim to provide greater flexibility and reduce manual effort in setting up test case tracking.

Highlights

• Automatic Test Case Creation: Introduced a new --create-tcases option for the junit-upload and playwright-json-upload commands. When enabled, this option automatically creates new test cases in QA Sphere for any test results that do not have valid test case markers.
• Test Case Mapping File Generation: Upon creating new test cases via --create-tcases, a mapping file (qasphere-automapping-YYYYMMDD-HHmmss.txt) is generated. This file lists the sequence numbers assigned to each newly created test case, helping users update their test suites for future uploads.
• Explicit Project Code Specification: Added a --project-code option to explicitly specify the project code when creating a new test run. This provides a more reliable alternative to auto-detecting the project code from test case names, which can be unreliable.
• API Enhancements: Implemented new API endpoints and schemas for paginated retrieval of test cases and bulk creation of test cases, supporting the new automatic test case creation functionality.
• Documentation and Examples Update: The README.md has been updated to reflect the new command-line options, clarify the two modes of uploading results (to an existing run or creating a new one), and provide updated examples for various scenarios, including automatic test case creation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 introduces a significant enhancement to the junit-upload and playwright-json-upload commands, allowing users to automatically create new test cases in QA Sphere for results that lack valid markers. The README.md has been updated to clarify the two modes of operation (uploading to an existing run or creating a new one) and details the new --project-code and --create-tcases options, including examples and updated requirements for test case matching. Core API changes include new interfaces for pagination and test case creation (PaginatedResponse, TCase, CreateTCasesRequest, CreateTCasesResponse) in src/api/schemas.ts, and corresponding API methods (getTCasesPaginated, createTCases) in src/api/tcases.ts. A new utility appendSearchParams was added in src/api/utils.ts for building URL query parameters. The command-line interface in src/commands/resultUpload.ts now includes the --project-code and --create-tcases options, with revised examples and epilogue text. New test fixtures were added, and src/tests/result-upload.spec.ts was updated with new test cases and mocked API handlers to validate the test case creation functionality, including cleanup for generated mapping files. The ResultUploadCommandHandler in src/utils/result-upload/ResultUploadCommandHandler.ts was refactored to support the new modes, including a discriminated union for command arguments, logic for detecting project codes, fetching existing test cases, creating new ones, and generating a mapping file for newly created test cases. Review comments highlighted a type safety issue with the runName property in ResultUploadCommandArgs, an unsafe type assertion for runName in processTemplate, and a potential bug in the isValidValue utility function where 0 was incorrectly treated as an invalid value, suggesting a more robust check for null and undefined.

[gemini-code-assist]

The isValidValue function currently filters out the number 0 because 0 is a falsy value. This could lead to unexpected behavior if an API parameter legitimately needs to be 0. A safer and clearer implementation would be to explicitly check for null and undefined.

Suggested change

	const isValidValue = (value: unknown) => {
	return value || value === false || value === ''
	}
	const isValidValue = (value: unknown) => {
	return value !== null && value !== undefined
	}