You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Phantom PhantomJS's show up in the activity monitor after tests have run. Run testacular start runs the tests with PhantomJS even though it's not in the browsers array.
OSX (mountain lion)
Node 0.8.15
Testacular 0.5.5
A co-worker with simular setup was able to reproduce this issues as well. His activity monitor had at least 6 PhantomJS's running.
The text was updated successfully, but these errors were encountered:
I think the reason for this is when testacular crashes the PhantomJS instances stay open and they are on the connection page to testacular so they run the tests. Try
$ killall phantomjs
and run testacular again to see if this problem still occurs.
Phantom PhantomJS's show up in the activity monitor after tests have run. Run
testacular start
runs the tests with PhantomJS even though it's not in thebrowsers
array.A co-worker with simular setup was able to reproduce this issues as well. His activity monitor had at least 6 PhantomJS's running.
The text was updated successfully, but these errors were encountered: