Fixed the non-deterministic behavior of tests in TkMapperServiceTest

[Wang-Benjamin]

Problem

When the test execution order is changed, all five tests in file TkMapperServiceTest.java would show a non-deterministic behavior and output the following errors of two kinds:

• IllegalArgumentException: wrong number of arguments
• IllegalMonitorStateException: current thread is not owner

The root cause of these errors is that Salon generates a subclass proxy for the test class. When the test methods are non-final, the proxy would override them and route calls through Solon's AOP chain. With NonDex randomizing the iteration order, this proxy path intermittently mis-invokes methods and the above errors would be generated.

Commands to reproduce the errors:

mvn -pl solon-plugin -Dcheckstyle.skip=true -Drat.skip=true \
    edu.illinois:nondex-maven-plugin:2.1.7:nondex \
    -Dtest=tk.mybatis.solon.test.service.TkMapperServiceTest#testName \ -- replace with the actual test name
    -DnondexRuns=10 |& tee nondex-$(date +%s).log

Proposed Fix

The code changes are local and minimum. By changing the test method to final, we can avoid Solon overriding or intercepting them.

Involved Tests

• TkMapperServiceTest.all
• TkMapperServiceTest.byId
• TkMapperServiceTest.exampleQuery
• TkMapperServiceTest.rawMybatisQuery
• TkMapperServiceTest.logicDelInsert

[Copilot]

Pull Request Overview

This PR addresses non-deterministic test behavior in TkMapperServiceTest by making all test methods final to prevent Solon's AOP proxy from overriding them and causing intermittent execution issues.

• Added final modifier to five test methods to prevent proxy interference
• Resolves IllegalArgumentException and IllegalMonitorStateException errors that occur when test execution order changes
• Maintains existing test functionality while ensuring deterministic behavior

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}