Reported duration time of scenario is about 0ms on Android

[aslakhellesoy]

From @lsuski on July 5, 2018 18:7

Hi,
I've recently build locally cucumber 4.0.0-SNAPSHOT and tried it on Android and encounter issue with scenario duration time. For most of scenarios it is about 0ms or 25ms or 75ms so generally it is very short but test takes naturally longer. With Cucumber 2.4.0 execution time is normal (average 2s per scenario). I was digging whole day in code base but could not find any reason for that.
Was there any change between 2.4.0 and 4.0.0-SNAPSHOT which could introduce such issue on Android?

Copied from original issue: cucumber/cucumber-jvm#1413

[aslakhellesoy]

From @mpkorstanje on July 5, 2018 18:32

If you can tell me where the time is reported I might be able to help.

[lsuski]

I mean the time shown in Android Studio test execution tab on the right of scenario name

[mpkorstanje]

Sure. But where does that time come from?

[mpkorstanje]

We did stop using XStream in 3.x for our transformations. That might have something to do with it, XStream involved quite a bit of class path scanning/reflection. Both are slow operations on Android I believe.

[mpkorstanje]

Does it add up wit the reported durations in logcat?

[lsuski]

I'll check tomorrow, but execution time is slower than reported, it takes about 2 s per scenario but reported in Android Studio is 0ms. I have no idea where does that time come from. I thought it is reported to Instrumentation but it is not and it wasn't as well in 2.4.0. The only place where duration from Result is taken into account is Stats

[lsuski]

There is cucumber.api.event.TestCaseFinished class which holds cucumber.api.Result with duration. But I can't find a place where this duration is used except Stats and some formatters but it was the same in 2.4.0 and durations were accurate then. So there is some magic from which Intellij/AS is taking those duration but I'm lack of ideas currently.

[lsuski]

fixed by 2ed7777