Why does Karma show nothing? - karma-jasmine

Pretty much the title. I've been experimenting with Karma/Jasmine and this keeps happening. Sometimes there are errors in the console, sometimes not. Sometimes I add a blank line or two and it starts working. Sometimes I have to restart the ng test command and it starts working. It seems 90% of the time it has nothing to do with any actual fault in my test code. What does this blank screen mean? Have the tests not been run?

Related

What causes a complication to go blank in watchOS?

I've been debugging a complication of mine for several weeks now, and I am completely unable to figure out what runtime behavior (crash? hang? out of budget?) causes it to go completely blank.
I've left the exact same complication running overnight in the simulator as on my real watch, and my real watch (Series 2) will go blank yet the simulator catches no crashes or other failures that I can tell.
Does anyone know what going blank means for a complication on watchOS?
Sometimes it’s just watchOS, I think. When was the last time you power cycled the Watch? Also, have you looked at the Watch log files for your app? In devices from Xcode, you can view all the logs. See if there are any crash logs for your app on the Watch.

"Report" button in RIDE.py becomes inactive after the first run

After running a script when we make some changes and run it again the "Report" button at the top becomes inactive and the console remains blank.
Anyone facing this issue?
It only works if we clear cache memory after every run. I don't think it is an idle solution. Please share if anyone was a better solution.
I have seen this when i.e. the IEDriver.exe process is still running after the test stops.
Closing this process is then sufficient to enable the buttons (after next run).
A teardown closing all browsers should prevent this from happening.

Monaca IDE - console.log never appears

X-Post from here, for exposure: https://community.onsen.io/topic/222/monaca-ide-console-log-never-appears
Odd question, but only once while using Monaca IDE has anything ever shown up in the console.log portion of the IDE itself. It only occurred when I had a device synced via the debugger. I have since tried syncing it and I never get the device to show in the drop down box, it usually says unknown device /www/html/…
Now, do know that I have put several console.log(‘test’); lines of code to try this out and still no success. I would think that the IDE’s console area would show the log operations from the emulator and not from the device debugger as it has its own log that is view-able on the device, but this apparently isn’t the case. Is this correct or am I just really missing something simple here?
So this isn’t that big of an issue, but I figured out the problem. Basically, I keep the Monaca IDE tab open in Chrome all the time (I work via my laptop remotely). When I come back after a long absence (several hours, I don’t know what the time out is), the bottom section in the console has the Chrome error showing, like that page timed out. The IDE is still there, just that section is grayed out.
So to fix this, I would just refresh the page. The section pops back and all is good EXCEPT I just figured out that it is at that moment when the device connection no longer works. I can still click Run on Device and it works - syncing with the device - but the console.log no longer shows up. In order to get that back and working, you have to close the tab and reopen it; then everything works.

Timeout after 30000ms in Selenium IDE

I'm trying to open a page (target: /selenium#/login), but I keep getting a timeout error. The page seems to be done loading so I don't get why I keep getting the error. Also, the error only occurs when I'm playing the entire test suite. When I try to run each test case individually, the error doesn't appear.
EDIT: Forgot to mention, the error doesn't occur when I open a new tab right before the next test case starts (before the open command is read), so each test case has to be on an entirely new tab/window. Here's a screenshot: http://i.imgur.com/pF2e6iU.png

VB.NET: Stop smoothly in debug.assert (false) line

I always write code like this:
If SomethingIsTrue Then
'DoThis
ElseIf SomeOtherThingIsTrue Then
'DoThat
Else
Debug.Assert (False)'Doh!! I forgot to handle a certain condition
End If
In VB6 this worked great. During testing my app in the IDE, it just stopped in the Debug.Assert(False) line, and I saw where I missed something.
But VB.NET does not stop there but instead gives me a huge messagebox. This seems to be standard behaviour for Debug.Assert.
I have 2 questions, please:
1) How can I make it stop smoothly in that line instead of showing the messagebox?
2) How can I make it so that at runtime (!) no messagebox is shown but instead my application just keeps running without stopping or showing a messagebox?
Thank you!
I would write something along this line:
if debugger.isattached=True then
debugger.break
end if
Just wrap it in a shared sub, and you can simply call it in the else statement.
The code is typed without visual studio at hand, so I hope it will work.
How can I make it stop smoothly in that line instead of showing the messagebox?
Just click Retry on the message box that pops up. From MSDN:
Clicking Retry sends you to the code in the debugger if your application is running in a debugger, or offers to open a debugger if it is not.
Clicking Ignore will, well, ignore the message.
How can I make it so that at runtime (!) no messagebox is shown but instead my application just keeps running without stopping or showing a messagebox?
I don't mean what you mean with at runtime, since all asserts happen while your code is running, hence at runtime.
If you mean that asserts should be ignored while running your application without a debugger, just make a release build instead of a debug build. The Debug.Assert method works only in debug builds, and the point of debug builds is that they are easy to debug.
If you want nonetheless suppress the message box, see Customizing Assert behavior:
For example, you could override the TraceListener.Fail method to write to an event log instead of displaying the Assertion Failed dialog box.
To customize the output in this way, your program must contain a listener, and you must inherit from TraceListener and override its TraceListener.Fail method.