tidy up uncatalog cases (12.02)

[DuanKuanJun]

Description

Please briefly describe the code changes in this pull request.

Jira: https://jira.taosdata.com:18080/browse/TD-

Checklist

Please check the items in the checklist if applicable.

• Is the user manual updated?
• Are the test cases passed and automated?
• Is there no significant decrease in test coverage?

[gemini-code-assist]

Summary of Changes

Hello @DuanKuanJun, 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 undertakes a significant cleanup and restructuring of the test suite. The primary goal is to improve the organization and clarity of existing test cases by moving them into logical categories and updating their descriptions. This also includes consolidating related tests and refactoring some for better maintainability and readability, ensuring that the test suite is more robust and easier to navigate for future development and debugging efforts.

Highlights

• Test File Reorganization: Numerous test files have been moved from the uncatalog/system-test/0-others directory to more appropriate, categorized directories (e.g., 02-Databases/08-Keep, 06-DataIngestion/03-SML, 21-MetaData, 25-Privileges, 80-Components/01-Taosd, 80-Components/02-Taosc, 81-Tools/01-Check, 81-Tools/02-Taos).
• Test Case Renaming and Docstring Updates: Many test methods within the moved files have been renamed to follow a more consistent naming convention (e.g., test_sml_restart to test_write_sml_restart, test_taos_shell to test_tool_taos_shell). Corresponding docstrings have been updated to provide clearer and more detailed descriptions of the test steps and purpose.
• Consolidation of Scan Tests: The functionality from test_scan.py and test_scan_vgroups.py has been consolidated into a new file, test_check_scan.py, which now comprehensively covers SCAN DATABASE, SCAN VGROUPS, SHOW SCANS, SHOW SCAN <scan_id>, and KILL SCAN <scan_id> commands, including various error and success scenarios.
• Refactoring of test_time_range_wise.py: The test_time_range_wise.py file has been significantly refactored. It now focuses on basic TSMA functionality by comparing query results between databases with and without SMA, simplifying its previous complex SMA schema definition and related helper methods.
• Enhanced information_schema Tests: The test_meta_sysdb.py file, renamed to test_meta_information_schema.py, has been expanded with new methods and checks for various information_schema tables, including ins_columns, ins_stables, ins_dnodes, ins_grants, and ins_encryptions, providing more thorough metadata testing.

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 primarily involves refactoring and tidying up test cases by moving them from an 'uncatalog' directory to a more organized structure. The docstrings have been significantly improved, which is a great enhancement for maintainability. I've identified a few areas for improvement in the refactored code, including a potentially unsafe system call, some dead code, a flawed performance check, and a minor naming issue. My detailed feedback is provided in the comments below.