[Feature] More Functional Test Scenarios

Open
#2,653 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
databases, testing

Research direction

Start by locating the existing hstore functional-test entry points and determining how scenarios are currently executed. Define separate coverage for leader transfer, region split/merge, data operations, backup/restore, restarts, and scaling, with completion measured by recoverability, consistency, accuracy, and expected operation results.

Written by the indexing model from the issue text.

Description

feature tests
Feature Description (功能描述)

Do we have specific plans for various functional tests?

I think here are several scenarios in which we can add test cases for hstore:

  • 1. Transfer leader
  • 2. Split, merge region
  • 3. Read, write, delete data
  • 4. Backup, restore
  • 5. Stop all nodes and restart all nodes
  • 6. Restart all or part of the components repeatedly
  • 7. Constantly scaling up and down the number of nodes.

For these scenarios, we need to check the following items:

  1. There is no service that is irrecoverable
  2. Data consistency
  3. Data accuracy
  4. Whether the result of each operation meets expectations
Dominant language
Java
Stars
3.2k
Forks
637
Avg merge
3d 18h
Merged PRs (30d)
23

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.

More from apache/hugegraph

All issues in apache/hugegraph

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.