Test on multiple device profile emulators

[HakkyuKim]

I've tested locally on my machine, I'll mark it as "ready for review" when I've tested on the internal server.

Test passed on internal server: https://github.com/flutter-tizen/plugins/pull/228/checks?check_run_id=3834753312.

[swift-kim]

Tizen devices (including real devices) are basically all ephemeral. Why don't you use the term "emulator" instead of "ephemeral device"?

[HakkyuKim]

@swift-kim
In the context of the tool, I defined the term "ephemeral" as targets(real devices and emulators) that are created and deleted by to tool, I admit it doesn't make sense for real devices so I could have used the term ephemeral-emulators. If I use the term "emulator", it could mean choosing between a connected real device and a running emulator process. Does ephemeral-emulators sound better?

Tizen devices (including real devices) are basically all ephemeral.

I did not understand this part. Could you explain in detail?

[swift-kim]

The Flutter SDK (flutter_tools) defines an ephemeral device as a device that can be connected and disconnect to the host. For example, Android devices are ephemeral because the host needs to connect to the devices before operating on them, and a Windows device is non-ephemeral because the device itself is the host and can never disconnect. Thus, in terms of this definition, all Tizen devices are ephemeral. Do you really need to distinguish between emulator instances that are created by the tester tool on the fly and not created by it?

[HakkyuKim]

Thanks for the info. In that definition, I see that the current use of the term doesn't make sense. I do need an option that tests on emulators which are created and deleted by the tool on the fly instead of testing on any running emulator instances. I could simply use the phrase --generate-emulators for the option.

[swift-kim]

@HakkyuKim That sounds good. I just wanted to make it clear. Thanks.

[bwikbs]

It's pretty cool! 👍