Remove stale test code - Githubissues

flutter-tizen / engine

The Flutter engine

https://flutter.dev

BSD 3-Clause "New" or "Revised" License

6 stars 19 forks source link

Remove stale test code #252

Closed swift-kim closed 2 years ago

swift-kim commented 2 years ago

The current test code for FlutterTizenEngine is confusing because two different test patterns (mock_engine.cc-based and MOCK_ENGINE_PROC-based) are being used simultaneously. We should only use a single consistent pattern.

swift-kim commented 2 years ago

@bbrto21

Run, Stop, GetPluginRegistrar, and GetTextureRegistrar are tested by RunDoesExpectedInitialization so we don't have to test them again.
Invoking RunEngine or StopEngine twice is an undefined behavior and I don't think we need to test them.
The headed version of GetTextureRegistrar is already disabled and we don't have plan to support headed testing in the near future.