-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jmm/resolve cog baseline bug #2483
Conversation
Terraform plan for dev No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #349 |
Terraform plan for meta No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #349 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against eead0c6 |
@JeanMarie-TTS can we catch this up with main so @tadhg-ohiggins's PR is more reviewable? |
@danswick Merfed with |
PR checklist: submitters
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)PR checklist: reviewers
make docker-clean; make docker-first-run && docker compose up
; then rundocker compose exec web /bin/bash -c "python manage.py test"
The larger the PR, the stricter we should be about these points.
What does the PR fix
When running
run_2022
locally, noticed that a new entry was being created in CognizantBaseline for every assugnment of a cognizant_agency. We should not beadding a new entry if there is already a valid entry in this table.The test cases to test this scenario were not doing the right thing and hence tests were passing.
Updated the tst case to test this consition. Re-ran
run_2022
and it creates fewer entries now as it should be.Made minor tweaks to admin.py to be able to see the data better on the admin screen. This change is not required to fix he bug, but was useful in resolving it.