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

Print out pending test information gone from new version of Cedar. #303

Open
pivotal-domenic-curro opened this issue Dec 4, 2014 · 6 comments

Comments

@pivotal-domenic-curro
Copy link

I've updated Cedar, and I no longer receive a 'P' during test run nor do I receive information about the pended test (one that I have places an 'x' in front of).

@akitchen
Copy link
Contributor

akitchen commented Dec 4, 2014

Hey @pivotal-domenic-curro

that's pretty weird. Could you provide a bit more context? For instance, are you integrating Cedar via CocoaPods, as a cross-project dependency or a pre-compiled static library? Does cleaning/deleting DerivedData make a difference?

I ask because this is the first time we've heard of this, and many test suites come to mind which don't exhibit this issue.

Thanks!

@danger-ranger
Copy link

We're integrating it with CocoaPods. We're seeing the same issue across devices and cleaning and deleting derived data has no effect

@tjarratt
Copy link
Contributor

Hey @pivotal-domenic-curro and @xtreme-gavin-enns I've been on a couple few iOS projects in the SF office since you filed this issue and I haven't seen it occur with CocoaPods on the three codebases I worked on. Do you think we can close this out? Is there still something we can investigate and possibly fix?

@akitchen
Copy link
Contributor

Isn't this due to XCTest not supporting pending tests? I assume the difference in observed behaviors here is one of test bundle vs. spec suite app.

On Thu, Jun 11, 2015 at 10:43 PM, Tim Jarratt notifications@github.com
wrote:

Hey @pivotal-domenic-curro and @xtreme-gavin-enns I've been on a couple few iOS projects in the SF office since you filed this issue and I haven't seen it occur with CocoaPods on the three codebases I worked on. Do you think we can close this out? Is there still something we can investigate and possibly fix?

Reply to this email directly or view it on GitHub:
#303 (comment)

@thunderweasel
Copy link

Yeah, based on conversations I've had with people around the office the problem is just with people using the XCTest version. As someone who prefers running their tests in a test bundle, I think it would be nice if we could somehow still get the pending test output in the console when running test bundles, but it seems like this isn't really easy to do without pending tests showing up as "passing" in Xcode, which might be kind of problematic.

@akitchen
Copy link
Contributor

We have a story for this in the backlog now; I'm not sure if it's a regression or not but we'll see if at least the cedar reporter can support this

https://www.pivotaltracker.com/story/show/99707426

On Thu, Jul 23, 2015 at 8:07 AM, pivotal-ryan-mcleod
notifications@github.com wrote:

Yeah, based on conversations I've had with people around the office the problem is just with people using XCTest. As someone who prefers running their tests in a test bundle it would be nice if we could somehow still get the pending test output in the console when running test bundles, but it seems like this isn't really possible to do without pending tests showing up as "passing" in Xcode, which might be kind of problematic.

Reply to this email directly or view it on GitHub:
#303 (comment)

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

No branches or pull requests

5 participants