Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

[in_app_purchase] moved android iap unit tests #3732

Merged
merged 4 commits into from
Mar 26, 2021

Conversation

renefloor
Copy link
Contributor

Moved in_app_purchase unit tests.

As they were on the wrong place there was a misconception that they were missing.

Fixes flutter/flutter#78538 (as there were already quite some tests).

TextUtils and Logs had to be mocked as well to make the tests succeed in the new project.

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
  • I signed the CLA.
  • The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
  • I listed at least one issue that this PR fixes in the description above.
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
  • I updated CHANGELOG.md to add a description of the change.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@cyanglaz
Copy link
Contributor

all the log says is running java-test script/tool/lib/src/main.dart: Warning: Interpreting this as package URI, 'package:flutter_plugin_tools/src/main.dart'. All Java tests successful!

Is there a way to make sure the tests did actually run? Maybe try to modify a test to intentionally fail and see if ci fails?

@renefloor
Copy link
Contributor Author

@cyanglaz where is the location of the tests set for the CI? I couldn't really find it

@cyanglaz
Copy link
Contributor

@cyanglaz
Copy link
Contributor

#3742 has landed. we should be able to rebase and run tests in this PR.

@renefloor
Copy link
Contributor Author

Yes I tried to merge this with master yesterday, but this PR makes that close to impossible: #3744
I'll just recreate this today.

@renefloor renefloor force-pushed the feature/move-android-test branch from 72be712 to 377d504 Compare March 26, 2021 13:43
Copy link
Contributor

@mvanbeusekom mvanbeusekom left a comment

Choose a reason for hiding this comment

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

LGTM!

@mvanbeusekom mvanbeusekom added the waiting for tree to go green (Use "autosubmit") This PR is approved and tested, but waiting for the tree to be green to land. label Mar 26, 2021
@fluttergithubbot fluttergithubbot merged commit 5787b35 into flutter:master Mar 26, 2021
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Mar 26, 2021
fotiDim pushed a commit to fotiDim/plugins that referenced this pull request Sep 13, 2021
@mvanbeusekom mvanbeusekom deleted the feature/move-android-test branch September 21, 2021 09:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes p: in_app_purchase platform-android waiting for tree to go green (Use "autosubmit") This PR is approved and tested, but waiting for the tree to be green to land.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[in_app_purchase] Increase test coverage on Android
5 participants