importinto: adding more unit tests for import into

[GMHDBJD]

What problem does this PR solve?

Issue Number: ref #42930

Problem Summary:

What is changed and how it works?

• use mockgen for disttask

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from gmhdbjd. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[GMHDBJD]

/hold wip

[tiprow]

Hi @GMHDBJD. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-chi-bot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-chi-bot]

@GMHDBJD: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev	6388532	link	true	/test check-dev
idc-jenkins-ci-tidb/check_dev_2	6388532	link	true	/test check-dev2
pull-mysql-client-test	6388532	link	true	/test pull-mysql-client-test
idc-jenkins-ci-tidb/mysql-test	6388532	link	true	/test mysql-test
idc-jenkins-ci-tidb/build	6388532	link	true	/test build
pull-integration-ddl-test	6388532	link	true	/test pull-integration-ddl-test
idc-jenkins-ci-tidb/unit-test	6388532	link	true	/test unit-test
pull-br-integration-test	6388532	link	true	/test pull-br-integration-test
pull-lightning-integration-test	6388532	link	true	/test pull-lightning-integration-test
pull-integration-e2e-test	6388532	link	true	/test pull-integration-e2e-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.