563f1c588d
Problem: failed equality checks as in "(is (= expected actual))" will give a single, long line of output that for anything but the simplest data structures is unreadable by humans, and the output doesn't give a useful diff. Solution: use library https://github.com/nubank/matcher-combinators and its test directive "match?" which will pinpoint where two data structures differ. Then, instead of "(is (= ...", use "(is (match? expected actual)". It works beautifully. The library offers other nice matchers, but the majority of the time match? is sufficient. Can we use another test runner like Kaocha? kaocha-cljs2 (https://github.com/lambdaisland/kaocha-cljs2) would be able to print better test errors out of the box, among other features, but I have no clue if it would work well or at all in our stack (in theory yes, but it's a larger piece of work). |
||
|---|---|---|
| .. | ||
| decisions | ||
| images | ||
| sign_in | ||
| README.md | ||
| codebase-structure-and-guidelines.md | ||
| component-tests-overview.md | ||
| debugging.md | ||
| dependencies.md | ||
| export-icons.md | ||
| fdroid.md | ||
| how-to-catch-crash-on-ios.md | ||
| how-to-launch-e2e.md | ||
| ide-setup.md | ||
| merging-pr-process.md | ||
| new-guidelines.md | ||
| patching.md | ||
| pipeline_process.md | ||
| pixel-perfection.md | ||
| post-mortem.md | ||
| pr-review-policy.md | ||
| release-checklist.md | ||
| release-guide.md | ||
| starting-guide.md | ||
| status-go-changes.md | ||
| testing.md | ||
| troubleshooting.md | ||
README.md
Getting Started
Development Process
Working on PR together with QA team
Testing
End-to-end tests (e2e) overview
Component tests (jest) overview
Project details
status-go introduction (recorded meeting)
re-frame usage (recorded meeting)
Misc
Importing icons from Figma into project
Updating Status APK builds for the F-Droid Android application catalogue
Troubleshooting for known errors