strict testing

[pawelru]

• added options for strict testing
• add pre-commit.yaml
• solve all lintr issues
• solve all spelling issues

[github-actions]

Unit Tests Summary

  1 files  2 suites   54s ⏱️
 24 tests 0 ✅  24 💤 0 ❌
296 runs  0 ✅ 296 💤 0 ❌

Results for commit a650019.

♻️ This comment has been updated with latest results.

[github-actions]

Unit Test Performance Difference

Test Suite	$Status$	Time on main	$±Time$	$±Tests$	$±Skipped$	$±Failures$	$±Errors$
graph-snaps	💔	$3.92$	$+1.11$	$0$	$0$	$0$	$0$
markdown-snaps	💚	$50.59$	$-1.05$	$+1$	$+1$	$0$	$0$

Additional test case details

Test Suite	$Status$	Time on main	$±Time$	Test Case
graph-snaps	💔	$3.02$	$+1.30$	plot_v1

Results for commit 7085af0

♻️ This comment has been updated with latest results.

[shajoezhu]

hi @pawelru , do you know why rbmi table changed? i don't think any dependencies was updated for this?

[pawelru]

hi @pawelru , do you know why rbmi table changed? i don't think any dependencies was updated for this?

I have no idea. I will revert it and see what happens

[Melkiades]

Lgtm! Thanks Pawel! Fantastic work ;) skip_test_strict logic you highlighted is fine for me and for now, it seems quite clean and close to the original code. Doing some exception while testing, as you wrote, would be too complicated imo