Description of problem:
We've observed some changes in the effort counts for our analysis tests:
1. Source Analysis
- Source + dependencies analysis for the tackletest app, the effort count dropped from 30 to 4
"source+dep_analysis_on_tackletestapp":
{ "source": "Source code + dependencies", "target": ["Jakarta EE 9", "Containerization"], "effort": 30, },
- For Source analysis on daytrader app, it decreased from 402 to 91.
"source+dep_analysis_on_daytrader-app": {
"source": "Source code ",
"target": ["Jakarta EE 9", "Containerization", "Quarkus"],
"effort": 402,
"analysis_on_example-1-app":
{ "source": "Source code", "target": ["Containerization"], "effort": 2 }
"tackle-testapp-public-4-targets":
{ "appName": "tackle-testapp-public", "source": "Source code", "target": ["Application server migration to", "OpenJDK", "Containerization", "Linux"], "effort": 20 }
Binary Analysis:
- "binary_analysis_on_tackletestapp": { "source": "Binary", "target": ["Containerization"], "appName": "customers-tomcat-0.0.1-SNAPSHOT.war", }
- The effort used to be 1 now it's 0
File system - Java IO : local-storage-00001 rule is not triggered
- The effort used to be 1 now it's 0
Version-Release number of selected component (if applicable):
7.2.0-16
Actual results:
Difference in Effort count
Expected results:
Effort count should not differ