NRLMMD-GEOIPS / NRLMMD-GEOIPS/template_basic_plugin

Add test to "test_all.sh" to run all pytests

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

Nobody has claimed this yet.

testing
Dominant language
Python
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Requested Update

Description
  • Add a call to test_all.sh to run all pytests
Background and Motivation
  • Formalize the process of calling units tests in all repos.
  • May want to wait until we formalize the testing process (ie, potentially not having to clone geoips repo locally in order to run any tests - now since "check_code.sh" is called from $GEOIPS_PACKAGES_DIR, geoips must be cloned to run any plugin repo tests.
  • Something like "if -e tests/test_pytest; then pytest tests/test_pytest
Alternative Solutions
  • [ OPTIONAL: If appropriate, list alternative fixes that could be considered]
Environment
  • [ IF APPROPRIATE: Corresponding repository versions ]
Code to demonstrate issue
  • [ IF APPROPRIATE: Can include steps here to identify/demonstrate bug fix or desired feature ]
Checklist for Completion
  • <!--- Include a list of steps that must be complete in order to close this Issue --->

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

Open test_all.sh and inspect how existing checks are invoked, then review the proposed tests/test_pytest path and the role of check_code.sh from GEOIPS_PACKAGES_DIR. Done means test_all.sh invokes the repository's pytest tests in the agreed testing workflow; the issue notes that this process may still change.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.