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

Notification

Icon
Error
Tests are not executed
Options
Previous Topic Next Topic
Luciferius
#1 Posted : Thursday, March 21, 2013 12:37:00 PM(UTC)
Rank: Member

Groups: Registered
Joined: 2/28/2013(UTC)
Posts: 22

Thanks: 2 times
Was thanked: 4 time(s) in 4 post(s)
Hello,

Up to now Ncrunch work pretty well for me, but now sometimes there are tests which will not be executed. Two examples:
I change something in the test method which fails. Ncrunch builds in the background, but after that the test is not executed.
Or many tests fail, I repair alle tests at once. It executes only some test the other are not executed.

The status says for example "4 tests are queued for execution" and in the Processing Queue the test runner has the status pending, but it does nothing. These tests have the highest priority, so that should not be a problem. If I click on "Run all tests" these are executed. After that the behavior is the same.

Up to now the tests were allways executed.

Regards, Luciferius.
Back to top
 |  Edit by user
Remco
#2 Posted : Thursday, March 21, 2013 10:41:56 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi, thanks for posting!

I'm wondering if you wouldn't mind me bombarding you with a few questions to narrow down the scope of this issue.

- Which engine mode are you using? Is it the 'Run impacted tests' mode?
- How often does this issue occur? I.e. how many times per day of use?
- Have you noticed any pattern as to which tests seem to cease to run?
- Can you submit a bug report straight after the bug appears?


Thanks!

Remco
Back to top
Luciferius
#3 Posted : Friday, March 22, 2013 6:41:20 AM(UTC)
Rank: Member

Groups: Registered
Joined: 2/28/2013(UTC)
Posts: 22

Thanks: 2 times
Was thanked: 4 time(s) in 4 post(s)
Hi,

Here are some more infos:

Engine mode: "Run all tests automatically"
How often: Hard to say, in our company we would call it a mandelbug. Sometimes it happens all the time and sometimes it happens only once.
Pattern: I am not 100 percent sure, but I would say it only happens when one or more tests are failing and are known as such: So they fail one or more times in the past and even now after some changes.
I will submit the bug report after it happens the next time.

Regards, Luciferius.

EDIT: It also happens, when there are no failing tests. I have submitted the bug report.
Back to top
 |  Edit by user
Remco
#4 Posted : Friday, March 22, 2013 11:13:40 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks for sending through the report. I've inspected the log file and found evidence of an intermittent code coverage mapping issue that is surfacing on your solution. A fix for this issue is being included in the 1.45 release that I hope to have ready next week. Hopefully the new release should solve it.

Cheers,

Remco
Back to top
Remco
#5 Posted : Saturday, March 30, 2013 9:39:43 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
For anyone interested, a fix for this problem has been introduced with the newly released version of NCrunch (v1.45).
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.041 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download