apache/incubator-seata

Test: increase rm-datasource module test coverage

Open

#1,714 opened on Sep 26, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (25,960 stars) (8,878 forks)batch import
good first issuetype: enhancement

Description

Why you need it?

Is your feature request related to a problem? Please describe in details increase rm-datasource module test coverage

How it could be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

Other related information

Add any other context or screenshots about the feature request here.

Contributor guide

Tech stack
javasql
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaUnit testingSeata framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the rm datasource module under the seata rm datasource directory. Look at existing test files in src/test/ to understand the testing patterns used (likely JUnit). Check the code coverage report to identify untested classes and methods. Focus on writing unit tests for uncovered functionality, especially core data source operations. Consider using mocking frameworks like Mockito if needed. Review any existing test resources or configuration files.