Skip to content

Conversation

@swift-kim
Copy link
Member

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.

Copy link

@bbrto21 bbrto21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The removed tests are unit tests written to test each API of the engine.
Are you sure you want to remove them?(including headed version)

@swift-kim
Copy link
Member Author

@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.

@swift-kim swift-kim merged commit eeee17d into flutter-tizen:flutter-2.10.1-tizen Mar 3, 2022
swift-kim added a commit that referenced this pull request May 12, 2022
* Remove mock_engine-based tests

* Use absolute paths

* Install libflutter_engine.so

* Let RunsAOTCompiledDartCode return false
swift-kim added a commit that referenced this pull request Aug 5, 2022
* Remove mock_engine-based tests

* Use absolute paths

* Install libflutter_engine.so

* Let RunsAOTCompiledDartCode return false
swift-kim added a commit that referenced this pull request Sep 1, 2022
* Remove mock_engine-based tests

* Use absolute paths

* Install libflutter_engine.so

* Let RunsAOTCompiledDartCode return false
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants