René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Analyze test classes optionally if the user wants to","articleBody":"**Is your feature request related to a problem? Please describe.**\n\nCurrently, the `codeanalyzer-java` does not account for test classes (`src/test/java/`) when analyzing a Maven project. This leads to missing information from unit tests, which can be essential for understanding dependencies, call graphs, and other structural insights in a codebase.\n\n**Describe the solution you’d like**\n\nThe tool should recognize and process test classes located in src/test/java/, ensuring they are included in relevant analyses. Specifically, it should:\n\n* Detect test classes and compile them if necessary.\n* Include test-related call sites and dependencies in the analysis.\n* Maintain a distinction between main source files (target/classes/) and test files (target/test-classes/).\n\nAdd a new flag `--include-test-classes` that optionally enable `mvn test-compile` instead of `mvn compile` (or the gradle alternative)\n\n**Describe alternatives you’ve considered**\n\n* Manually copying test classes to the main source directory before running the tool (not ideal).\n* Running a separate analysis phase for test files.\n* Using custom workarounds to merge test and main class data post-analysis.\n\n**Additional context**\n\nHandling test classes is crucial for tools that analyze code structure, call graphs, and dependencies since test cases often contain critical references to core logic. Support for this feature would improve the completeness of the analysis.","author":{"url":"https://github.com/rahlk","@type":"Person","name":"rahlk"},"datePublished":"2025-02-19T19:53:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/125/codeanalyzer-java/issues/125"}