Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix failing tests #556

Closed
IndrajeetPatil opened this issue Mar 18, 2023 · 4 comments
Closed

Fix failing tests #556

IndrajeetPatil opened this issue Mar 18, 2023 · 4 comments
Assignees

Comments

@IndrajeetPatil
Copy link
Member

══ Failed tests ════════════════════════════════════════════════════════════════
── Failure ('test-cronbachs_alpha.R:14:3'): cronbachs_alpha, principal_components ──
cronbachs_alpha(pca, verbose = FALSE) (`actual`) not equal to c(PC1 = 0.1101384) (`expected`).

  `actual`: 0.09
`expected`: 0.11
── Failure ('test-cronbachs_alpha.R:15:3'): cronbachs_alpha, principal_components ──
`cronbachs_alpha(pca)` did not throw the expected warning.

[ FAIL 2 | WARN 2 | SKIP 10 | PASS 295 ]
@strengejacke
Copy link
Member

These tests should all be fixed after updates were submitted to CRAN (in the order insight -> datawizard -> parameters -> performance). They all work on the dev-versions, but then I removed them from the Remotes field, because of the circular issues in the readme-check. So this should be resolved already.

@IndrajeetPatil
Copy link
Member Author

Ah, okay. Good to know.

@IndrajeetPatil
Copy link
Member Author

These tests are still failing, even with insight 0.19.1.

@strengejacke
Copy link
Member

Yes, they require the latest changes in parameters, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants