Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Console] Cleaned up the unit tests. #6989

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2013

Conversation

jakzal
Copy link
Contributor

@jakzal jakzal commented Feb 6, 2013

Cleaned up some unit tests in the Console component as suggested in #6935. I didn't fully cleanup the Application tests to not to delay this PR. I might do it later as a separate one.

Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #6935
License MIT
Doc PR n/a


/**
* @expectedException \InvalidArgumentException
* @expectedExceptionMessage The command "foofoo" does not exist.
Copy link
Member

Choose a reason for hiding this comment

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

Isn't it nicer to line these comments out, as we do with other PHPdoc annotations?

/**
 * @expectedException        \InvalidArgumentException
 * @expectedExceptionMessage The command "foofoo" does not exist.
 */

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point.

@fabpot
Copy link
Member

fabpot commented Feb 7, 2013

I'm against these changes because it's going to make merging between tests so much complicated.

@jakzal
Copy link
Contributor Author

jakzal commented Feb 7, 2013

@fabpot that's true, I was actually thinking of this as well.

However, many of those tests are hard to follow. I could put additional effort to back-porting it to the other branches if needed. If that's not the way to go, please close this PR.

@fabpot
Copy link
Member

fabpot commented Feb 7, 2013

I'm not sure this is worth the effort. But if you want, doing that in the 2.1 branch would be, indeed, better (and cross your fingers for the merge into 2.2 ;)).

@vicb
Copy link
Contributor

vicb commented Feb 7, 2013

👍 tests should be considered as part of the documentation.

@wouterj
Copy link
Member

wouterj commented Feb 7, 2013

👍 for the same reasons as @vicb I use tests a lot to discover how to use features that aren't documented yet in the documentation.

fabpot added a commit that referenced this pull request Apr 9, 2013
This PR was merged into the master branch.

Discussion
----------

[Console] Cleaned up the unit tests.

Cleaned up some unit tests in the Console component as suggested in #6935. I didn't fully cleanup the Application tests to not to delay this PR. I might do it later as a separate one.

| Q              | A                                        |
|--------------|--------------------------------|
| Bug fix?          | no |
|New feature? | no |
|BC breaks?    | no |
|Deprecations? |	no |
|Tests pass? | yes |
|Fixed tickets | #6935 |
|License | MIT |
|Doc PR | n/a |

Commits
-------

5ca04b0 [Console] Cleaned up the unit tests.
@fabpot fabpot merged commit 5ca04b0 into symfony:master Apr 9, 2013
@jakzal jakzal deleted the console-tests-cleanup branch April 20, 2013 22:32
@jakzal
Copy link
Contributor Author

jakzal commented Apr 20, 2013

@fabpot I forgot about this PR. Do you want me to submit another one for 2.1/2.2 branches?

@fabpot
Copy link
Member

fabpot commented Apr 21, 2013

@jakzal No, refactoring such as this one really belongs to master only. Thanks.

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.

4 participants