Skip to content
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

Running PHPUnit with --tap and processing results #305

Closed
jakubkulhan opened this issue Mar 19, 2014 · 4 comments
Closed

Running PHPUnit with --tap and processing results #305

jakubkulhan opened this issue Mar 19, 2014 · 4 comments

Comments

@jakubkulhan
Copy link

Current state is that the entire build either fails or succeeds.

I'd like to be able to see which tests failed. PHPUnit supports TAP, so processing it's output should be easy.

@meadsteve
Copy link
Contributor

I think the output from phpunit should be logged at LogLevel::INFO which I think you should be able to see in the web interface. Can you confirm if you can.

This may be the same underlying issue as point 2 in #303

@jakubkulhan
Copy link
Author

It gets logged, I can see it in Build Log. This is not a bug report, more of a feature request.

For example in Bamboo, I can see on builds summary page how many tests failed:
snimek obrazovky 2014-03-20 v12 19 36

And on build detail page which tests passed and which failed:
snimek obrazovky 2014-03-20 v12 22 07

This would be extremely helpful feature.

@meadsteve
Copy link
Contributor

ah got it. I misunderstood. This is indeed a feature request. The first though that springs to mind is that a plugin should be able to register the number of tests is performed and how many passed/failed. Our phpunit plugin could then be extended to implement this.

@dancryer dancryer added this to the Version 2 milestone Apr 16, 2014
dancryer pushed a commit that referenced this issue Apr 25, 2014
@dancryer
Copy link
Owner

This can be arranged. I've already made PHPMD and PHPCS do this, so PHPUnit shouldn't be too tough. :)

prezire pushed a commit to prezire/PHPCI that referenced this issue Feb 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants