Skip to content
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

Validation: A fuel was reported for an Emission Category with no reported emissions #2009

Open
3 tasks
dleard opened this issue Oct 12, 2021 · 1 comment
Open
3 tasks
Labels
Backlog Refinement Issues to look at during backlog refinement. User Story A User Story issue type

Comments

@dleard
Copy link
Contributor

dleard commented Oct 12, 2021

Our emission_category_missing_fuel() validation function checks for the opposite scenario where a (carbon taxed) Emission Category has reported emissions but a fuel was not reported for that category.

Question: do we need a validation for the scenario where a fuel is reported in a (carbon taxed) Emission Category but no emissions were reported in that category?

AC:

  • Add a new validation function to check this scenario
  • Add a corresponding entry in data/prod/application_validation_function.sql
  • pgTap test for the new validation function
@dleard dleard added attn: Business Area Blocked issue, Business area Backlog Refinement Issues to look at during backlog refinement. User Story A User Story issue type labels Oct 12, 2021
@hannavovk
Copy link

hannavovk commented Oct 12, 2021

Following up on our conversation: checked with Unit Head - YES, a reverse validation as described in this scenario would be beneficial.
cc: @matthieu-foucault, @dleard, @pbastia

@matthieu-foucault matthieu-foucault removed the attn: Business Area Blocked issue, Business area label Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog Refinement Issues to look at during backlog refinement. User Story A User Story issue type
Projects
None yet
Development

No branches or pull requests

3 participants