search

floriangrundig / karma-test-runner

Grails plugin to run javascript tests with karma in grails lifecycle "test-app"
Apache License 2.0
7 stars 5 forks source link

e2e iframe permissions #8

Closed mloeks closed 9 years ago

mloeks commented 10 years ago

Hi,

thanks for this great and very useful plugin! I managed to run the unit tests but get errors for my e2e tests. The karma config is very similar to what is provided in the sample 'grails-angular-phonecat' project.

I'm only trying to run a simple test: browser().navigateTo('/')

'/' is mapped to 'localhost:8080/grails-app-name' in the karma config proxies entry. The grails app is running on localhost:8080.

This is the error I get: Error: Permission denied to access property 'coverage' [double underscores, github makes it bold!] at [...]/node_modules/karma-ng-scenario/lib/adapter.js:43

I suspect this has something to do with loading the web-app in the iframe of the browser which karma opens and some cross-origin violations?

I'm using: Ubuntu 13.10 Java 7 Grails 2.3.7 karma-test-runner 0.2.1 karma-remote-reporter 0.1.5 karma-ng-scenario 0.1.0

I know that this error might not even be related to this plugin, since I also get it when I run karma via CLI. However, I did not find any other hints on how to get e2e tests to run in a grails project with ng-scenario and karma.

Any help is appreciated! Sorry for posting this as an "issue", which it might not be. But I did not find any other possibility to contact the author.

Thanks and best regards, Matthias

floriangrundig commented 10 years ago

Hey Matthias,

is this still an issue?

cheers

mloeks commented 10 years ago

Hi Florian,

yes it is. I could not find a solution for this issue so far. Any help on this or ideas what could cause the issue are appreciated.

Many thanks, Matthias

floriangrundig commented 10 years ago

Hi,

this error usually occurs if you navigate to a page (in your case "/") and this page makes a full page reload -> all the karma testing stuff is gone and you get this error. So if you load your page manually is there a redirect or something like that (you can use e.g. chrome developer tools to see what happens with you request)? Can you post a screenshot of the chrome developer tools network tab with your request or the git repo so I can try to reproduce the error...

Cheers

floriangrundig commented 9 years ago

I close this - no response from matze09

mloeks commented 9 years ago

Hi Florian, sorry for not responding. It's ok to close this for the time being. I could not yet solve the issue but found another workaround to do the e2e tests. I'll get back to you in case this issue should get relevant once again. Thanks for your input, Matthias