oceanbase / oceanbase/seekdb

Add mysqltest-case for 442bp2_xml_feature branch

Open
#786 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dima type: task
Dominant language
C++
Stars
2.9k
Forks
342
Avg merge
1d 19h
Merged PRs (30d)
52

Description

Description

This is a request to add a mysqltest case for the feature branch 442bp2_xml_feature. The target branch for this work is master.

Environment

  • Target Branch: master < 442bp2_xml_feature
  • Is this an RD-provided temporary version? No
  • Reproducibility: Not specified
  • Test Changes: Not specified
  • Other environmental anomalies or changes: Not specified
  • Environment Information: Not specified
  • Log Information: Not provided

Steps to Reproduce / Scenario Description

Not provided. Please describe the workload run on the environment, actions taken before the issue occurred, and any test changes.

Note: Strongly discouraged to only post ERROR logs or stack traces without context.

Other Information

For issues reported from external business operations, please correctly select the "Work Item Type" based on the actual situation:

  • Customer Service Feedback: Specifically refers to issues before production deployment or during POC, where a product bug is confirmed and requires a fix and release.
  • Online Issue: An issue that has occurred in a production environment, confirmed as a product bug, but not classified as a fault.
  • Online Fault: An issue that has occurred in a production environment, confirmed as a product bug, causing business errors or public impact on the customer side (the authority to define a fault belongs to the delivery service team).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating existing mysqltest cases covering XML features and compare how they are organized for the master branch. Determine the expected behavior for the 442bp2_xml_feature branch, then add a test that exercises that workload and passes with the feature integrated into master.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql
Domain
databases, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.