MerginMaps / MerginMaps/mobile
write consistent set of attribute forms tests
Open
Nobody has claimed this yet.
enhancement
forms
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
see https://docs.google.com/spreadsheets/d/1Eyv0YnxgPjxb-emlorBNAnFhDW2rxdumBYW9qHIwzsg/edit
- TC01 layouts
- TC02 derived
- TC03 widgets
- TC04 workflow
notes:
- tests should be written so they match the spreadsheet (e.g. TC01-A_ for ...)
- test have docs in their headers. we may want some overall markdown in the docs/ folder too
- for description of the tests ping @jozef-budac
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
Start with the linked spreadsheet and compare its TC01 layouts, TC02 derived, TC03 widgets, and TC04 workflow cases with the existing test structure. Check the test headers and the docs/ folder, and ask @jozef-budac for test descriptions. Done means the spreadsheet cases are covered with matching names and documented headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100