phuse-org / valtools

Validation framework for R packages used in clinical research and drug development.

https://phuse-org.github.io/valtools/

phuse-org/valtools Issues

README: links to cheat sheet are not working as expected
Closed 8 months ago
Working directory friction
Closed 9 months ago4
Maintaining valtools
Closed 9 months ago1
Traceability matrix generates errors when requirements are not numbers.
Updated 2 years ago1
File space design choices
Updated 3 years ago5
Answer to "Add user to config file?" in vt_use_report is disregarded
Updated 3 years ago1
Requirements bulk upload!
Updated 3 years ago
Difference between Requirement Name and Requirement ID
Updated 3 years ago1
Maintaining @editDate
Updated 3 years ago1
Function to address changing which report is run & output name
Updated 3 years ago
release for workshop
Closed 3 years ago1
add maya to contributors
Closed 3 years ago1
Update prompt to reference either packet or package
Updated 3 years ago
Check test code writer and requirement/test case writer
Updated 3 years ago
requirement report can't be generated from template in validate separate from pkg
Updated 3 years ago3
creating requirement as Rmd
Closed 3 years ago2
cheatsheet p2
Closed 3 years ago
dynamic referencing and NA values
Closed 3 years ago
Vignettes for different modes of Validation
Updated 3 years ago
vt_use_* can overwrite files in some cases
Closed 3 years ago1
Identifying validation lead
Closed 3 years ago1
Pulling the 'validation lead' title from the config yaml.
Updated 3 years ago
helpers to evaluate coverage matrix
Updated 3 years ago
Sorting strings
Updated 3 years ago
add documentation re: where to put {valtools} in DESCRIPTION
Closed 3 years ago5
treat source data for risk table and coverage matrix as a single data set
Updated 3 years ago
add test case for bibtex reference
Updated 3 years ago
open as opposed to overwrite
Closed 3 years ago1
add handler for test code headers
Updated 3 years ago1
Dynamic Referencing with Coverage
Updated 3 years ago
vt_scrape_tags_from assumes all files within the validation/* folder to be viable to be scraped from.
Updated 3 years ago
suppress dialog box
Closed 3 years ago1
External or 3rd party validation vignette
Updated 3 years ago2
Install from cran and validate
Updated 3 years ago
investigate compatibility with pkgdown
Updated 3 years ago
create version 0.3.0 for cascadia R workshop
Closed 3 years ago
add clarification that vt_validate_* functions need to be run from the project
Closed 3 years ago3
codcov badge
Closed 3 years ago1
vt_validate_* for validate separate from package
Closed 3 years ago4
can external location for validation report be designated via .yml?
Updated 3 years ago1
why does test code result table use inconsistent numbering ?
Closed 3 years ago1
does function coverage of requirements require a tracability matrix?
Updated 3 years ago1
vt_kable_* assumptions regarding ids
Closed 3 years ago2
automatically add valtools to packages that use config
Closed 3 years ago1
remove lingering .log files in folder
Updated 3 years ago
coverage matrix if no coverage info is included
Closed 4 years ago4
internal function `scrape_roxygen` expects Last Updated By: to have no trailing spaces
Closed 4 years ago1
adding simple asis code via validation_files field?
Updated 4 years ago
vt_scrape_function_editors does not play nicely w/ @include roxy block
Updated 4 years ago2
creating an extension for {riskmetric}
Updated 4 years ago2