Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bad file paths simply result in "No Specs" but leave no errors on the console #14

Open
iislucas opened this issue Mar 7, 2015 · 0 comments
Open

bad file paths simply result in "No Specs" but leave no errors on the console #14

iislucas opened this issue Mar 7, 2015 · 0 comments

Comments

@iislucas
Copy link

iislucas commented Mar 7, 2015

To reproduce:
clone: https://github.com/uProxy/uproxy-networking/tree/454e3bfef553525b9280d48f13255d6e2e2e8646
run grunt tcpIntegrationTest

Observe the chrome-app just says there are no specs, and doesn't show any errors.
Also; note the missing files don't get a <script...> tag, so you can't debug it that way either.

It would be great if it could tell you what is missing/lost/failing to be loaded.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Simplify semantics and usage of copying and script inclusion UWNetworksLab/grunt-jasmine-chromeapp
1 participant
@iislucas