Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[tests]: Set modules in all plot_* calls within test functions

Open Beginner friendly
#416 5 comments 1 reaction 2 assignees View on GitHub

Maintainers usually reply within 1 day

@Schiano-NOAA is already working on this.

Since Oct 13, 2026.

  • #417 by @copilot-swe-agent — closed without merging
  • #425 by @JZahner1 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
r
Domain
testing

Research direction

The payload does not name the test files, so start by running the test suite locally and noting where the interactive module prompt appears, then find the plot_* calls in the test functions that omit the module argument. Add a valid module value to each of those calls; the issue leaves the choice of value open, so check how the plotting functions use it. Done means the suite runs without any prompt, and an optional filter_data test covers the user-selection path.

Written by the indexing model from the issue text.

Description

Presently, all tests of the plotting function omit the module parameter, which eventually prompts the user to select a module via the R terminal. This makes running the tests suite locally not automatic (the user has to continuously interact with the tests by selecting modules). It would probably be more efficient to set the module parameter in each call to a plot_* function within the testing suite, rather than leaving it to wait for a user prompt.

An additional test could be created specifically for filter_data that tests that the user selection works, if there are concerns about that functionality breaking.

Dominant language
R
Stars
20
Forks
9
Avg merge
1d 5h
Merged PRs (30d)
12

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from nmfs-ost/stockplotr

All issues in nmfs-ost/stockplotr

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.