What does this progress bar display mean (with only part of the bar in green, with no red, and with 0% displayed.)
[img=https://image.ibb.co/ncvJiH/ProgBar.jpg]Progress Bar[/img]
After reading the link provided by NCrunch Developer below, I understand what this means, but it appears that this is only an interim display, meaningful to display the progress of the testing process while the tests are running, and after the tests have completed, the bar should change to display the outcome of all the tests.
In my case, no matte how many times I restart the entire test suite, the display never goes any further than the display pictured above. It gets to this point and appears to freeze, or stop, as pictured above, but there is no error message or explanation.
Is this a defect, or a symptom of something else wrong? What is going on?
The screenshot you've posted describes that around 70% of the work in NCrunch's processing queue has been processed (shown by the green bar progress), no tests are failing (bar is green), and the 'risk' level is 0% or very close to it. Risk level is determined by the number of tests in the processing queue that were impacted by code changes. In this case, because the risk is so low, it's unlikely that any of the tests in the processing queue have been impacted by code changes, so it's unlikely that a test will fail given the state of the code.
Why does the bar not continue to where the entire thing is green and the 0% changes to "OK" ? It has frozen, (stopped) in the display as I showed it. No matter how long I wait it never goes any further.Even if I restart the entire suite of tests over again, it only goes to approximately the same place and stops again.
The continuation of the bar is dependent on the test tasks in the processing queue being completed by the engine.
If you have a big, long running test that is marked using the 'RequiredCapabilities' attribute or your engine is otherwise configured not to run it, this can result in a task being 'stuck' in the processing queue and left unexecuted by the engine. It should be possible to identify this task by opening the Processing Queue Window and examining the test.
Note that the bar also will only have its progress updated when a task actually completes. This means that if you have a test task that takes several hours to run, the bar may sit in an uncompleted state for a long period of time before suddenly hitting 100% when the task finally completes.
cbretana wrote:This solution has 4-5000 tests, which normally only take a few minutes to complete. Is there some way to see which test might be the culprit?