Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

task: Improve the test case coverage of [integration-tx-api] module to 70% #6507

Open
lightClouds917 opened this issue Apr 27, 2024 · 3 comments · May be fixed by #6533
Open

task: Improve the test case coverage of [integration-tx-api] module to 70% #6507

lightClouds917 opened this issue Apr 27, 2024 · 3 comments · May be fixed by #6533
Assignees
Labels
good first issue Good for newcomers

Comments

@lightClouds917
Copy link
Contributor

Why you need it?

Is your feature request related to a problem? Please describe in details

The test case coverage of [integration-tx-api] module is 18.33%, We need to go up to 70% to improve the robustness and stability of our code.
[integration-tx-api]模块的测试用例覆盖率为18.33%,我们需要提高到70%,以提高代码的健壮性和稳定性。

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.
You can get some help from:
https://seata.apache.org/docs/developers/contributor-guide/test-coverage-guide_dev
https://seata.apache.org/blog/how-to-write-unit-tests

@funky-eyes funky-eyes added the good first issue Good for newcomers label Apr 28, 2024
@azatyamanaev
Copy link

azatyamanaev commented May 10, 2024

Hello. Can you assign this issue to me?

@azatyamanaev
Copy link

I made a pull request for this issue. Can you review it?

@xingfudeshi
Copy link
Member

Hello. Can you assign this issue to me?

Hi.This issue has assigned to you.Thanks for your work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants