Test if running on simulator

no, :test is only kept when running tests

Okay but you could still use :debug and :release if you only deploy the release version to devices.

And that's what most of us use, but it's not 100% 

It's good for not releasing accidentally some thing not meant for release.

But sometimes you do want (or need to) run release build in the simulator. Although in most of those cases you probably would want to run release (non-emulator) code anyways (i.e DataField on old device with not enough memory or trying to recreate a crash from ERA)

Then you could set a storage value in debug mode. Which in theory only gets set in Simulator.   Then if you subsequently run release in Simulator it can work in same manner.  Like you say depends on needs. You just need a system works for 99% of time, and can be quickly tweaked for those 1% or less of cases.

For now this is good enough and 'simulator' code will never endup with end users. This way I can overrule the onpress functionallity with an extra setting to cycle through test situations.

This seems like a reasonable solution. Obviously it breaks if you change the battery values for some reason, but it doesn't seem like something that you would need to do very often or indeed at all, for the vast majority of applications.

I wouldn't release an app with code that thinks that it runs in a simulator every couple of days, even if only for a couple of minutes

It's pretty unlikely that battery and batteryInDays would line up exactly at 50.0 and exactly at 5.0 particularly often, but I agree it's not perfect; sadly that seems to be the way of things given the absence of any official way of having such an obviously useful bit of functionality. (And anyway it's the kind of thing you would annotate with (:debug), so you wouldn't be at risk of publishing it in production.)

Yeah, I guess that is a solution, but if you're going down that kind of route it seems a rather complicated way of doing it. You may as well just achieve the same thing using a storage variable, which you manually set once in the simulator using Edit Application.Storage Data and otherwise provide no user accessible means of setting it to true. i.e. something like:

var IS_SIMULATOR as Lang.Boolean = false;
        
private function calledAtStartup() as Lang.Void
{
    var isSimulatorNullable = Storage.getValue(activityKey("isSimulator"));
    IS_SIMULATOR = isSimulatorNullable != null ? isSimulatorNullable as Lang.Boolean : false;
    Storage.setValue(activityKey("isSimulator"), IS_SIMULATOR);
}

Wastes 4 bytes of storage space I guess.