Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
1.31b doesn't execute MSpec tests
Options
Previous Topic Next Topic
AlexZeitler
#1 Posted : Wednesday, May 25, 2011 6:33:27 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/25/2011(UTC)
Posts: 4
Location: Karlsruhe

Thanks: 1 times
Hi,

first of all thanks doing such great work.

Version 1.30b worked quite well for me but after updating to 1.31b this morning my MSpec tests don't execute any longer.

When clicking on a row "Run 5 Tests" in the Processing Queue it shows the following exception in the details box below:

[08:26:22.7828-TestExecutionTask-43] Error 'Internal': System.TypeLoadException: Could not load type 'Castle.Core.Interceptor.IInterceptor' from assembly 'Castle.Core, Version=2.5.1.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc'.
at nCrunch.TestExecution.Frameworks.MSpec.MSpecTestFramework.#=qkZtigWnrFzrHjbmdz$TZHz9Jc2gcXdnxFbc$1d$77_U=.#=qw9VJtnyDYdsBYpFJWZ1xuQ==()
at #=qZfBi_VMr$9hYvCPxGnLkD5xFW0OSKSeBdU8BPxPUv5Ojf3rSdy7kw922DNNXry2t.#=quTMn4iDd$Fc_VoPTDz$iRqhyrKGu_gwbp7yrWCpNETs=(Action #=qi4uFd$JRapiS$ymC$WXirHGT6b097YlYfj72f8bBZUA=)
at nCrunch.TestExecution.Frameworks.MSpec.MSpecTestFramework.RunTests(TestOutput output, IList`1 testsToRun, MasterExecutionMapSet masterMapSet)
at nCrunch.TestExecution.TestRunnerThread.#=q5qAH8o1SN7xgq9ABN7XSIA==(IMasterExecutionMap[] #=qzqPXZoA$nSnZ7LqmRccxUclO$MwwnyD1HYX6LCXOAm4=, IList`1 #=q4dJfWSbgrHs7Mw_ByN7ruA==)

I'm running VS 2010 Ultimate EN on Windows 7 EN x64.

Alex
Back to top
WWW
Remco
#2 Posted : Wednesday, May 25, 2011 6:46:41 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi Alex - Thanks for posting this so promptly.

Are you using the Castle.Core assembly inside your project? I'm wondering if this could be a clash between a version of Castle used by your project vs. the version used by NCrunch's MSpec runner.

I'm curious (and a bit concerned) as to why this would suddenly appear in 1.31b ... if you uninstall and downgrade back to 1.30b, do the tests run ok?
Back to top
AlexZeitler
#3 Posted : Wednesday, May 25, 2011 6:50:27 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/25/2011(UTC)
Posts: 4
Location: Karlsruhe

Thanks: 1 times
Hi Remco,

thanks for your fast reply.

Indeed I'm using Castle.Core inside my project due to using NHibernate inside this project.

Just downgraded to 1.30b and everything is ok.

Alex
Back to top
WWW
slieser
#4 Posted : Wednesday, May 25, 2011 7:29:24 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/19/2011(UTC)
Posts: 5
Location: Cologne, Germany
Hi Remco,

same problem here. I'm using MSpec with Machine.Fakes with FakeItEasy. Castle.Core 2.5.1 is referenced by the project (I installed MSpec and MSpec.Fakes with nuget).


Regards
Stefan Lieser
Back to top
WWW
Der-Albert.com
#5 Posted : Wednesday, May 25, 2011 8:09:43 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 209

Thanks: 11 times
Was thanked: 55 time(s) in 51 post(s)
Same here (with Machine.Fakes.FakeItEasy).

Also the coverage is wrong. It shows good Test. But not real running them.

Image http://twitpic.com/528p9g/full
Back to top
BLOG
 |  Edit by user
Slesa
#6 Posted : Wednesday, May 25, 2011 9:16:59 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/25/2011(UTC)
Posts: 4
Location: Saarland, Germany

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
Me, too
Back to top
WWW
Remco
#7 Posted : Wednesday, May 25, 2011 12:25:06 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Can each of you guys punch through a bug report after you get the run failure?

Also ... are any of you working in an open source codebase? If I have access to a solution that surfaces the problem consistently, I should be able to fix it quite promptly :)
Back to top
Slesa
#8 Posted : Wednesday, May 25, 2011 12:31:32 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/25/2011(UTC)
Posts: 4
Location: Saarland, Germany

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
I tested it with this project https://github.com/Slesa.../tree/master/src/Lucifer this morning. Beside the mentioned effect of using Castle.Core, there is an error within Lucifer.Editor, where it does not find the assembly of Caliburn.Micro. That's what I sent a report about.
Back to top
WWW
1 user thanked Slesa for this useful post.
Remco on 6/1/2011(UTC)
Remco
#9 Posted : Wednesday, May 25, 2011 12:33:47 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Excellent - thank you :) I'll take a look.
Back to top
Remco
#10 Posted : Wednesday, June 1, 2011 7:09:39 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
I've taken a good look at this and reproduced both issues in the Lucifer solution:

1. As described, MSpec blows up when using the latest version of Castle in the testing environment. I've introduced a fix for this in the upcoming 1.32b release.

2. The Caliburn.Micro build issue appears to be triggered by a namespace clash issue where MSBuild cannot tell the difference between two different namespaces referenced within one of the source files. The cause of this issue is that NCrunch is erroneously including an entire dependency tree of assembly references when building the project, where it should only be including assemblies referenced directly from the project being built. I've fixed this issue in the upcoming 1.32b release. Meanwhile, a workaround could be to try rearranging some of the namespacing around this error. You should easily be able to reproduce the problem outside of NCrunch if you introduce a project reference from Lucifer.Caliburn from Lucifer.Editor.

Thanks again for providing the source. This made fixing the above issues much easier :)
Back to top
Remco
#11 Posted : Thursday, June 16, 2011 6:09:49 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
For anyone interested, a proper fix for both of the above issues has now been released as part of 1.32b.
Back to top
Der-Albert.com
#12 Posted : Friday, June 17, 2011 12:07:31 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 209

Thanks: 11 times
Was thanked: 55 time(s) in 51 post(s)
Confirmed! Thanks.
Back to top
BLOG
drlongnecker
#13 Posted : Thursday, June 30, 2011 4:35:17 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/30/2011(UTC)
Posts: 3
Hate to pull up an old topic, but the history on this one matched so well.

I'm a new user of 1.32b and my mspec tests are showing up in the runner; however, they are always passing.

Code example:

Code:
[Subject("a failure")]
public class a_when_doing_something_wrong
{
  It should_fail = () => "moo".ShouldEqual(2.ToString());
}


The test, however, passes in the runner. It properly fails when executing it from mspec:

Quote:
Machine.Specifications.SpecificationException: Should equal "2" but is "moo"


I've tried this at various nesting levels, with and without a because/context, and still nothing. I also do not appear to have any code coverage; however, the .pdb files are available.

This forum thread leads me that this is fixed, but is there a configuration setting I'm missing?

Thanks!

-dl
Back to top
BLOG
Remco
#14 Posted : Thursday, June 30, 2011 7:44:58 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks for reporting this issue.

This definitely looks like a new problem, and it's definitely not the intended behaviour.

Do you notice this for ALL the tests in your entire solution? Do they by chance still fail if you explicitly throw an exception from one of them?

Also ... is the missing code coverage universal or does it only apply to a specific project? Do you still see black markers where the coverage is missing?
Back to top
drlongnecker
#15 Posted : Thursday, June 30, 2011 9:21:09 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/30/2011(UTC)
Posts: 3
@Remco-

1) Yes, this was for all tests in the solution. I tried it on a few different solutions of varying size (ranging from ~30 tests to 800 tests). If I explicitly throw an exception, it still passes. That is what originally clued me into the problem. I assumed mspec's Catch.Exception was broken on my last build.

2) The code coverage (or lack thereof) seems universal. I verified that the .pdb files exist and, I'm assuming, are accessible. The black markers are appearing on all projects in the solutions.

I've tried in x64, x86, DEBUG, RELEASE, and combinations of each for build configurations. so far no luck.

Thanks!
Back to top
BLOG
Remco
#16 Posted : Friday, July 1, 2011 9:09:42 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Something is definitely going very wrong in there ... Would you mind kicking through a bug report if you haven't already? I have a feeling that something in your solution is causing a failure.
Back to top
drlongnecker
#17 Posted : Tuesday, July 5, 2011 2:50:39 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/30/2011(UTC)
Posts: 3
Submitted a bug report; thanks!
Back to top
BLOG
Remco
#18 Posted : Tuesday, July 5, 2011 9:09:28 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Excellent thank you!
Back to top
Remco
#19 Posted : Monday, September 5, 2011 7:43:46 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,135

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
For anyone interested, this issue should be fixed in the recently released 1.33b.
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.107 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download