Just brainstorming…
- Color conversions
- Object position after alignment (on known [emulated] screen size)
- File system (generic functionality; not suggesting it initially test anything platform specific)
- Area mutation
- Asyncs fire
- Linked lists would be an almost perfect first candidate
- Math functionality
- Memory seems like a good candidate, but could open up black-hole of low RoI problematic edge cases or false results
- printf
- Tasks fire
- Text mutation/manipulation/calculation
- Utils
- Fonts might be difficult
- Style copying
- Theme verification
- Objects may be hard.
- Drawing will be difficult only in that it will require verifying results from screen capture, and that isn’t trivial to verify
Again, my initial proposal is just for basic core functionality tests where judiciously determined to be worthwhile to minimize regressions.