MerginMaps / MerginMaps/mobile
Benchmark tests
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
It would be good to set up some tests for benchmarking the app performance. Currently, there are many sources which can introduce regression. I suggest to set up some basic tests to:
- App loading with no projects
- App loading with default projects
- Map rendering (we need different scenarios for that, e.g. online/offline, with/without OTF projection (+/- custom grid shifts)
- Forms and relations
- Downloading/syncing project
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the app's existing test and benchmarking infrastructure, then define coverage for app loading, map rendering, forms and relations, and project downloading or syncing across the listed scenarios. Done means repeatable benchmark tests cover those cases and can detect performance regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile-dev, performance, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100