Originally I wrote this as my comment in #27 but, I think, here is a better place for discussions.

Wouldn't it be easier to use testthat edition 3, which automatically sets the language to English:

In https://www.tidyverse.org/blog/2020/10/testthat-3-0-0/:

test_that() now sets a number of options and env vars to make output as reproducible as possible. Many of these options were previously set in various places (including devtools::test(), test_dir(), test_file(), and verify_output()) but they have now been centralised in to local_test_context().

In the Details section of local_test_context() documentation:

In the third edition, local_test_context() also calls local_reproducible_output() which temporary sets the following options:

...

And modifies the following env vars:

Unsets RSTUDIO, which ensures that RStudio is never detected as running.

Sets LANGUAGE = "en", which ensures that no message translation occurs.

Finally, it sets the collation locale to "C", which ensures that character sorting the same regardless of system locale.

So I suggest trying testthat edition 3. If it fails, then considering merging this PR.

Is it OK with you, @cbeleites?

unit tests failing with LANGUAGE different than English #26

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions