Merge package:mockito

[mosuem]

• Move and fix workflow files, labeler.yaml, and badges in the README.md
• Rev the version of the package, so that pub.dev points to the correct site
• Add a line to the changelog:

* Move to `dart-lang/test` monorepo.

• Add the package to the top-level readme of the monorepo:

| [mockito](pkgs/mockito/) | A mock framework inspired by Mockito with APIs for Fakes, Mocks, behavior verification, and stubbing. | [![pub package](https://img.shields.io/pub/v/mockito.svg)](https://pub.dev/packages/mockito) |

• Important! Merge the PR with 'Create a merge commit' (enabling then disabling the Allow merge commits admin setting)
• Update the auto-publishing settings on https://pub.dev/packages/mockito/admin
• Add the following text to https://github.com/dart-lang/mockito/:'

> [!IMPORTANT]  
> This repo has moved to https://github.com/dart-lang/test/tree/master/pkgs/mockito

• Publish using the autopublish workflow
• Push tags to GitHub using git tag --list 'mockito*' | xargs git push origin
• Close open PRs in dart-lang/mockito with the following message:

Closing as the [dart-lang/mockito](https://github.com/dart-lang/mockito) repository is merged into the [dart-lang/test](https://github.com/dart-lang/test) monorepo. Please re-open this PR there!

• Transfer issues by running dart run pkgs/repo_manage/bin/report.dart transfer-issues --source-repo dart-lang/mockito --target-repo dart-lang/test --add-label package:mockito --apply-changes
• Archive https://github.com/dart-lang/mockito/
• Import to g3 - see internal cl/705463525

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[mosuem]

I don't see the pubspec, but I imagine the deps just need to be bumped. Or mockito in google3 might be using unpublished elements from analyzer.

It seems like stable Dart does not yet support some features. I would advise to move this package with the failing CI, and fix the issue in a follow up. IIUC, fixing would require depending on a dev version of Dart, or removing the use of these features.

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:mockito	5.4.5-dev.0	ready to publish	mockito-v5.4.5-dev.0
package:checks	0.3.1-wip	WIP (no publish necessary)
package:fake_async	1.3.2	already published at pub.dev
package:matcher	0.12.18-wip	WIP (no publish necessary)
package:test	1.25.12	already published at pub.dev
package:test_api	0.7.4	already published at pub.dev
package:test_core	0.6.8	already published at pub.dev

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[jakemac53]

I looked a bit at the issue tracker for this package and I am pretty concerned about merging it into the test repo.

This package is active enough I think it should stay in its own repo. I am not able or willing to take ownership of it and don't want to be on the hook for fielding the issues, but would feel obligated to if it was in this repo.

[mosuem]

Hm. In my personal opinion, merging mockito into this repo should really not imply that you are in any way an owner, but I can definitely see why it would feel that way.

@devoncarew @srawlins any ideas?

[srawlins]

I don't have any feelings about where it lives. I have not been a good owner, but I won't ask anyone else to.

[devoncarew]

mockito is pretty up in the air currently (should we own it? do we have the time to maintain and move it forward?). Let's hold off on moving this to a monorepo until we have more clarity on the medium term / long term plans.