Last modified 3 years ago
How to test window manager and libraries.
All
- valgrind:
- fix invalid access!
- fix memory leaks
- brief look at still reachable memory (stringshares and other globals!)
- use eina_stringshare_dump() to see strings that are being stored, try to identify leaks as valgrind will not help you there!
- be aware of false positives (document them?)
- llvm/clangs reports:
- fix null dereference and other major warnings
- remove dead assignments and fix other minor warnings
- gcc -Wall -Wextra
- fix unused parameters, variables, conversions.
Evas
- run expedite and test performance, compare with older releases and find out regressions.
E Window Manager
- start from scratch, without previous ~/.e
- test every shipped profile (let's expand this into more details)
- test every shipped module (let's expand this into more details)
- test every dialog from every module (let's expand this into more details)
