Skip to content

Generate tests to exercise error handling added for METplus-Internal #50 and to increase code coverage #339

@bikegeek

Description

@bikegeek

Replace italics below with details for this issue.

Describe the Task

Modifications to the METdbLoad code for the following METplus-Internal issue:

https://github.com/orgs/dtcenter/projects/75/views/15?sliceBy%5Bvalue%5D=dtcenter%2FMETplus-Internal&pane=issue&itemId=28260964&issue=dtcenter%7CMETplus-Internal%7C50

cannot be verified unless testing can be performed in the met_db_load.py code to trigger specific error conditions.

Time Estimate

Estimate the amount of work required here.
2-3 days

Sub-Issues

Consider breaking the task down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Review default alert labels
  • Select component(s)
  • Select priority
  • Select requestor(s)

Milestone and Projects

  • Select Milestone as a METdataio-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
  • For a METdataio-X.Y.Z version, select the METdataio-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

Task Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Add any new Python packages to the METplus Components Python Requirements table.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issue
    Select: Milestone as the next official version
    Select: METdataio-X.Y.Z Development project for development toward the next official release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

🩺 Needs Triage

Relationships

None yet

Development

No branches or pull requests

Issue actions