MetOffice / MetOffice/CDDS

Detecting import problems

Open
#533 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

migrated
Dominant language
Python
Stars
8
Forks
7
Avg merge
1d 15h
Merged PRs (30d)
23

Description

Migrated Jira Issue CDDSO-168
Jira creation date 06/07/2022 15:29
-------
If there are any import issues, the tests (even the nightly tests) will not find them all. The best approach is to run each script in the ``bin`` folders with ``--help`` parameter.

It would be neady to have such a little test. That will be run when kick off the unit tests.
-------

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the scripts in the repository's bin folders and the existing unit-test entry point. Run each script with --help to understand the expected checks, then add a test that performs this for all applicable scripts and fails on import problems when the unit tests start.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.