Sanity testing for Daily build release process is to achieve the “stable daily trunk build” goal on all applicable MeeGo platforms. Daily build validation (both core and UX) is to provide comparable results for TT (Trunk:Testing) and Trunk. With that, release engineer can compare and see that changes introduced to TT are not breaking something which we have working in Trunk.
|System||Startup||system bootup and shutdown||pass||pass|
|no obvious regression on boot time||pass||pass|
|Overall||no process eats unusual CPU||pass||pass|
|no process eats unusual memory||pass||pass|
|usb storage can be recognized||pass||pass|
|connman||3G data connection||n/a||n/a|
|Guest WiFi nework||n/a(19659)||pass|
|oFono||accept an incoming call||n/a||n/a|
|make a call successfully||n/a||n/a|
|Telepathy (IM)||Send gtalk IM||n/a(19659)||pass|
|Receive gtalk IM||n/a(19659)||pass|
Core sanity test check points is to check the key functionality of the core components. Make sure the new changes won’t introduce the regression on general health of the distribution (through comparable result between TT and Trunk).
|SW management||Package Management|