Comments (3)
deparse()
comes with its own headaches (though I do think it's probably the right way to go) -- a minimal-overhead approach is to just use seq_along
to number the tests. At least that way the test failures will have unique names.
from patrick.
I think a good use case to have in mind here is replacing a simple for
loop with a patrick test.
With for
loop:
for (name in names) {
test_that(sprintf("works: %s", name), {
# expectations depending on 'name'
})
}
replaced with
with_parameters_test_that(
"works:",
{
# expectations depending on 'name'
},
name = names
)
A big appeal of the for
loop is that names
can be a literal & we don't need to store any variables in the test env, nor to repeat ourselves by spelling out names
>once.
Whereas the appeal of doing this through patrick
is (1) API consistency within a test suite (2) makes it clearer the purpose is to do a templated series of tests (slightly less clear in for
loop approach, especially with a bigger {...}
body) and (3) obviates the distracting sprintf()
test name construction part.
from patrick.
I think this is the same as a new issue I was about to post:
The more I use patrick()
the more I find myself writing code like:
with_parameters_test_that(
"a test name",
{ some_test_exprs(single_param) },
.test_name = FOO,
single_param = FOO
)
This feels pretty redundant. It seems like using .test_name = params[[1]]
when length(params) == 1
is a reasonable default.
Alternatively, accepting syntax like
single_param = FOO, .test_name = single_param
(or even "single_param"
to avoid NSE headaches)
would generalize to higher-cardinality tests where .test_name
is still drawn directly from one of the test parameters
from patrick.
Related Issues (14)
- .setup= argument to allow re-usable (but hermetic) local variables? HOT 1
- make patrick citable HOT 1
- Do I add patrick to the Remotes field inside DESCRIPTION? HOT 2
- Could not find function "with_parameters_test_that" HOT 2
- Can we only use one expectation inside the `code` argument? HOT 1
- Supply a glue-formatted string to `.test_names=` for building the name from `.cases` HOT 2
- API for handling `skip()` of some cases?
- What happens when a parametrised test fails? HOT 8
- Consider an API change: `test_these()`
- Update for dev testthat
- Make package available via conda HOT 4
- Warning for code outside `test_that()` HOT 4
- Creating factorial tests HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from patrick.