ropensci/qualtRics

Regenerate all test fixtures

Open

#294 opened on Nov 15, 2022

View on GitHub
 (14 comments) (0 reactions) (0 assignees)R (71 forks)github user discovery
discussionhelp wanted

Repository metrics

Stars
 (229 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

In ropensci/vcr#255 @sckott suggested it is good practice to regenerate all the test fixtures on occasion. We definitely have not done that, mostly because I (the maintainer) don't have access to many of the features we have tested. These fixtures were created by the individuals who did the original PRs (so involve their surveys).

What is the best way forward from here?

Contributor guide

Research direction
Investigate how to run the existing test suite and regenerate fixtures by examining the test setup and any configuration for API access.
Tech stack
r
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
RGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50