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

Notification

Icon
Error
No Green Checkmark when Test Successfully Ends
Options
Previous Topic Next Topic
CoolBreeze
#1 Posted : Tuesday, March 24, 2015 4:34:44 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 7/11/2014(UTC)
Posts: 79
Location: United States of America

Was thanked: 9 time(s) in 9 post(s)
I have a suite of tests to test the UI of a web application. I'm using NCrunch.Net, MbUnit, and Selenium.

When I run most of the tests and when they succeed NCrunch displays the green check mark as expected to the left of the test name.

When I run one specific test the test appears to run through all test cases based on the output in the log but when completed NCrunch is still displaying the green clock to the left of the test name.

I added code to the Setup and TearDown functions to write to the Gallio.Framework.TestLog the date, time, and the name of the function.

When this test runs those functions do display that information just mentioned so I know NCrunch is executing those Setup and TearDown functions.

NCrunch Status column shows "Running [Passed last run]".

re: red circle with the number in the middle located on the lower right side of VS (when I hover over it with the mouse it displays "NCurnch engine is idle").

I do not see the white dot moving around that red circle.

This is not very important - but I would love to see the green check mark next to the successfully completed test

Thanks,

Ed
Back to top
Remco
#2 Posted : Tuesday, March 24, 2015 9:44:41 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 932 times
Was thanked: 1259 time(s) in 1172 post(s)
Hi Ed,

Thanks for sharing this issue.

When you see this happen, could you check the status of the tasks inside the Processing Queue window? Are the tasks shown here as still executing? Knowing this will help to establish whether this is a UI synchronisation issue or if there is something in the runner that is hanging.


Cheers,

Remco
Back to top
CoolBreeze
#3 Posted : Thursday, April 16, 2015 4:32:07 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 7/11/2014(UTC)
Posts: 79
Location: United States of America

Was thanked: 9 time(s) in 9 post(s)
Hi Remco,

I saw the same behavior again. Hopefully here's more info:

NCrunch doesn't update the information for a long-running test in the Tests window. The Tests windows shows the previous test information.

I manually run a long running test. When the test completes I see:

A green clock icon to the left of the test name. I was expecting a green check mark instead of the green clock icon.
Status states: "Running [Passed last run], Pixelised
Last Execution Time: 00:05:00.214
Server: local

When I mouse over the NCrunch icon in the lower right-hand corner the popup shows "NCrunch engine is idle".

For this test I use MbUnit.
There are no asserts (I just didn't add them yet).
The test runs for about 3 minutes.
I have mbunit and ncrunch timeout attributes for 5 minutes applied to the test.
NCrunch 2.13.0.5


You asked for the info in the Processing Queue window:
Task: green clock icon
Status Running
Priority: 0
Expected Processing Time: 00:03:4Ser0.909
Actual Processing Time: 00:03:40.909
Server: (blank)


Ed
Back to top
Remco
#4 Posted : Thursday, April 16, 2015 10:28:06 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 932 times
Was thanked: 1259 time(s) in 1172 post(s)
Hi Ed,

Just trying to confirm the state of the engine when this goes wrong - are you saying that you have a Test that is marked as running in the Tests Window, with a task that is marked as running in the Processing Queue, and the NCrunch corner spinner says that the engine is idle?

The Processing Queue is the closest physical representation of what the engine is actually doing. I would trust it over the Tests Window or the corner spinner. This means that if you have a task still running in the processing queue, most likely there is actually a test still running (perhaps in a hung state?), and the corner spinner is mis-reporting.

What happens if you choose to Kill the hung task in the Processing Queue?
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.034 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download