Closed sh16011993 closed 1 week ago
Please have look at the comments @sh16011993
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Totals | |
---|---|
Statements: | 20.1% ( 2980 / 14829 ) |
Methods: | 10.3% ( 194 / 1884 ) |
Lines: | 23% ( 2574 / 11192 ) |
Branches: | 12.09% ( 212 / 1753 ) |
Totals | |
---|---|
Statements: | 54.25% ( 453 / 835 ) |
Methods: | 49.02% ( 50 / 102 ) |
Lines: | 58.68% ( 372 / 634 ) |
Branches: | 31.31% ( 31 / 99 ) |
Totals | |
---|---|
Statements: | 82.18% ( 775 / 943 ) |
Methods: | 80% ( 84 / 105 ) |
Lines: | 83.44% ( 670 / 803 ) |
Branches: | 60% ( 21 / 35 ) |
Totals | |
---|---|
Statements: | 61.62% ( 4944 / 8023 ) |
Methods: | 58.47% ( 604 / 1033 ) |
Lines: | 66% ( 3932 / 5958 ) |
Branches: | 39.53% ( 408 / 1032 ) |
As a part of this PR, the following was completed:
workflow-wrap-up
worker was updated to populate the new columnprevious_date_changed_reported_assessment_id
for an application inCompleted
state. The following were considered when updating the worker:Scenario 1 Checked if there is a previously reported assessment for the application (ordered by assessment_date desc, limit 1), immediately before the assessment being processed right now.
Scenario 2 If no assessment was ever reported, checked if an e-Cert was generated for this application.
If Scenario 1 or Scenario 2 produced an assessment: Checked if the offering dates changed, If yes, saved the assessment in the
previous_date_changed_reported_assessment_id
. If no, then left the column as is.Generated Queries for reference:
Next PR: e2e tests