4b8a612df4
Document some of our current testing practices in hopes of helping reduce friction in PRs and communication in general. In theory, nothing in the text should be a surprise because these are things we have been discussing over many months (some things for almost 1.5 years) and are already present in the code. |
||
---|---|---|
.. | ||
decisions | ||
files | ||
images | ||
sign_in | ||
tests | ||
README.md | ||
codebase-structure-and-guidelines.md | ||
debugging.md | ||
dependencies.md | ||
export-icons.md | ||
fdroid.md | ||
how-to-catch-crash-on-ios.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 | ||
react_tree.png | ||
release-checklist.md | ||
release-guide.md | ||
starting-guide.md | ||
status-go-changes.md | ||
troubleshooting.md | ||
ui-guidelines.md |
README.md
Getting Started
Development Process
- Coding guidelines
- UI components coding guidelines
- Release Checklist
- Release Guide
- Merging PR process
- PR Review Policy
- Working on PR together with QA team
- Debugging
- Patching
- Creating a pixel perfect UI
- Contributing to status-go
- Malli schemas (recorded demo) (slides)
Testing
Project details
- status-go introduction (recorded meeting)
- re-frame usage (recorded meeting)
- status app functionality demo
Misc
- Importing icons from Figma into project
- Updating Status APK builds for the F-Droid Android application catalogue
- Troubleshooting for known errors