Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Messenger] Move MiddlewareTestCase in Test ns#28985

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 1 commit intosymfony:masterfromogizanagi:messenger/middleware_test_case
Oct 27, 2018
Merged

[Messenger] Move MiddlewareTestCase in Test ns#28985

fabpot merged 1 commit intosymfony:masterfromogizanagi:messenger/middleware_test_case
Oct 27, 2018

Conversation

@ogizanagi
Copy link
Contributor

@ogizanagiogizanagi commentedOct 25, 2018
edited
Loading

QA
Branch?master
Bug fix?no
New feature?yes
BC breaks?no
Deprecations?no
Tests pass?yes (AppVeyor failure unrelated)
Fixed ticketsN/A
LicenseMIT
Doc PRN/A

Just a quick suggestion after#28943 being merged. Wouldn't it make sense to move this inTest namespace to be used by anyone wanting to unit test their middleware?

Copy link
Contributor

@srozesroze left a comment

Choose a reason for hiding this comment

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

Yep, sounds reasonable to me.

@ro0NL
Copy link
Contributor

should we actually use it?#28999

@ogizanagi
Copy link
ContributorAuthor

@ro0NL : Done and addedMiddlewareTestCase::getThrowingStackMock().
Thanks for pointing this out

@fabpot
Copy link
Member

Thank you@ogizanagi.

@fabpotfabpot merged commit215c895 intosymfony:masterOct 27, 2018
fabpot added a commit that referenced this pull requestOct 27, 2018
…agi)This PR was merged into the 4.2-dev branch.Discussion----------[Messenger] Move MiddlewareTestCase in Test ns| Q             | A| ------------- | ---| Branch?       | master <!-- see below -->| Bug fix?      | no| New feature?  | yes <!-- don't forget to update src/**/CHANGELOG.md files -->| BC breaks?    | no     <!-- seehttps://symfony.com/bc -->| Deprecations? | no <!-- don't forget to update UPGRADE-*.md and src/**/CHANGELOG.md files -->| Tests pass?   | yes (AppVeyor failure unrelated)    <!-- please add some, will be required by reviewers -->| Fixed tickets | N/A   <!-- #-prefixed issue number(s), if any -->| License       | MIT| Doc PR        | N/AJust a quick suggestion after#28943 being merged. Wouldn't it make sense to move this in `Test` namespace to be used by anyone wanting to unit test their middleware?Commits-------215c895 [Messenger] Move MiddlewareTestCase in Test ns
@ogizanagiogizanagi deleted the messenger/middleware_test_case branchOctober 27, 2018 18:15
@nicolas-grekasnicolas-grekas modified the milestones:next,4.2Nov 1, 2018
This was referencedNov 3, 2018
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@xabbuhxabbuhxabbuh approved these changes

@chalasrchalasrchalasr approved these changes

@nicolas-grekasnicolas-grekasAwaiting requested review from nicolas-grekas

+2 more reviewers

@srozesrozesroze approved these changes

@ro0NLro0NLro0NL approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

4.2

Development

Successfully merging this pull request may close these issues.

8 participants

@ogizanagi@ro0NL@fabpot@sroze@xabbuh@chalasr@nicolas-grekas@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp