Future Feature Enhancement Plan

[SongXueZhi]

In terms of functionality:

1. We need the ability to analyze the project's root directory and its module structure. This will enable us to handle multi-module projects and generate test commands for such projects. @zhj-lu
2. From a testing perspective, it seems that we haven't found tests for many of the BFCs. We may need to separately search for tests submitted before and after a bfc or attempt to run tests for the entire project. The latter may require analyzing the overall test time for a specific project and determining it as one of the strategies. @DoughIt

In terms of performance:

Our current testing process is somewhat resource-intensive. I believe we should analyze the possibility of testing by class when certain conditions are met (e.g., when there are a large number of test cases under a test file or a large number of test files). Alternatively, we could consider testing multiple classes at once and retrieve the results of each test case from the test report, rather than individually testing each test case. @DoughIt

Regarding compilation failures after migration：

I think our first step should be to re-implement the rules from RegMiner that were used before [https://sites.google.com/view/regminer/ast-rewiring-rules]. In this context, we can abandon rules 1 and 2, as we no longer support bugs prior to JDK 1.7. Additionally, we can iteratively attempt to migrate changes like 1）refactoring and 2）inserting modified class members (method declarations, imports, class declarations) to bfc-1. @DoughIt

[SongXueZhi]

I would like RegMiner to have the ability to resume the recording process, save results, and support task checkpoint and resumption. @zhj-lu

[SongXueZhi]

sort BFCs

[SongXueZhi]

I think the so-called test search is actually the process of BFC Evaluation. If test cases of pBFC cannot be found, we can confirm this pBFC is not real BFC.
I suggest putting the test search process in BFC Evaluation.
@DoughIt