nickserv / karma-edge-launcher Goto Github PK

Cannot finish the tests. In the following repo, gulp watch works well, but gulp test hang own process. When I remove Edge from target browsers, gulp test has no problem.

0. clone https://github.com/falsandtru/spica
1. npm i
2. gulp test

Note: karma start --browsers Edge --single-run works well.

I'm trying to use karma-edge-launcher to run our test suite on appveyor, but I get ERROR: The process "MicrosoftEdge.exe" not found..

But I don't know how to install MicrosoftEdge.exe from appveyor's PowerShell.

ps: Install-Product "MicrosoftEdge.exe" appveyor on google gives me nothing.

This would be great information to have in the README.

That package also hard codes the exe path, so it'll need to be updated when the current version of karma-edge-launcher is on npm.

This is waiting on Microsoft's next fast ring release of Windows 10 Insider Preview (see Upcoming changes to Windows 10 Insider Preview builds).

In the next build we release to Windows Insiders in the Fast ring, the “Project Spartan” name will officially change to Microsoft Edge. One result of this naming means that the Microsoft Edge app has a new app ID.

https://www.npmjs.com/package/karma-edge-launcher

Unfortunately, resolve is very buggy on recent versions of Node, and their CI builds are only running deprecated versions of Node.

I depended on edge-launcher@beta by accident. It would be better to use @latest, but only if it supports the -k flag with the recent bug fixes.

npm install throws the error "No name provided in package.json"

Hello,

I tried to use your edge launcher and got a 404 on the npm package install. Am I doing something wrong or is it not available anymore?

Thanks,
Aleks

I have a pull request for karma-detect-browsers that adds support for this plugin. You may find this useful if you're already using the plugin, or if you want to conditionally test Edge on Windows 10. If you're interested in testing it, you can install my fork with npm install --save-dev nickmccurdy/karma-detect-browsers#edge.

I'll close this issue if the original pull request is merged or closed.

As specified in the Readme I've ran the npm install karma-edge-launcher --save-dev to install.

I've configured it in karma browsers to run, but when I run the tests I received the error

21 07 2016 15:01:23.489:ERROR [plugin]: Cannot find plugin "./node_modules/karma-edge-launcher".
  Did you forget to install it?
  npm install .\node_modules/karma-edge-launcher --save-dev

I thought this was weird, the install wen't flawlessly so I went to node_modules to check if the karma-edge-launcher is or not installed.
But surprise, surprise it was there, but the folder had no js file, only the readme.md, project.json and LICENSE.

I've open the project.json to check for any clue and I found that the karma-edge-launcher is associated to this repository which is not yours.

So how can I install your karma-edge-launcher?

At least for me start microsoft-edge:http://localhost works just fine.

Hi there,

I have no idea what I am doing wrong, but while I run tests with Edge browser, it opens example.com instead of localhost.
If I change browser to Chrome, Firefox even IE - everything works good.

I tried that with:

• karma start --browsers Edge
• using grunt and grunt-karma
• using Webstorm

Any ideas?

Best regards,
Greg.

Microsoft just released the Edge Diagnostics Adapter for debugging Edge. Since it's tricky to launch Edge as a modern-style app (and there are still bugs on master currently), I'm going to try switching to this adapter.

If this is fixed, not much else will block this launcher from being published.

Edge should automatically close after karma start if singleRun is enabled. Currently, it stays open but it doesn't seem to cause any issues or warnings with Karma.