1.0 / April 25, 2016
(4.7/5) (Learn More</a></div>)
Loading...

Description

This launcher application provides a simple repeatable way oftesting for transient state bugs in your Android app.Visithttps://github.com/idelgado/tstu for the latest sourcecode.Transient state bugs are rarely encountered during developmentbut often appear in production. Transient state loss can occur forseveral reasons:- A configuration change occurs as a result of ascreen orientation change, locale change, etc.- The Activity isdestroyed. This is equivalent to setting Don't keep activities indeveloper options.- The application process is killed due toinactivity.The challenge of testing transient state loss is thatthere are no simple repeatable ways to test it without jumpingthrough a few hoops. The most common recommendation is to invokescreen orientation changes with an emulator or to use Don't keepActivities from the developer options. Both of these options fallshort of providing complete transient state testing coveragebecause they only destroy the Activity and do not destroy theentire Application process which can happen during inactivity.

App Information TSTU

  • App Name
    TSTU
  • Package Name
    org.idelgado.tstu
  • Updated
    April 25, 2016
  • File Size
    1.0M
  • Requires Android
    Android 3.2 and up
  • Version
    1.0
  • Developer
    Iñaqui Delgado
  • Installs
    10+
  • Price
    Free
  • Category
    Tools
  • Developer
  • Google Play Link

Iñaqui Delgado Show More...

TSTU 1.0 APK
This launcher application provides a simple repeatable way oftesting for transient state bugs in your Android app.Visithttps://github.com/idelgado/tstu for the latest sourcecode.Transient state bugs are rarely encountered during developmentbut often appear in production. Transient state loss can occur forseveral reasons:- A configuration change occurs as a result of ascreen orientation change, locale change, etc.- The Activity isdestroyed. This is equivalent to setting Don't keep activities indeveloper options.- The application process is killed due toinactivity.The challenge of testing transient state loss is thatthere are no simple repeatable ways to test it without jumpingthrough a few hoops. The most common recommendation is to invokescreen orientation changes with an emulator or to use Don't keepActivities from the developer options. Both of these options fallshort of providing complete transient state testing coveragebecause they only destroy the Activity and do not destroy theentire Application process which can happen during inactivity.
Loading...