Running qunit tests from the command line produces no output.

[klenwell]

Following instructions in README and wiki. Tests run in browser with qunit as expected.

When I set up teaspoon with jasmine and run tests from the command line, they run ok. I see the following output:

$ xvfb-run bundle exec rake teaspoon DRIVER=capybara_webkit suite=default
Starting the Teaspoon server...
Teaspoon running default suite at http://127.0.0.1:34088/teaspoon/default
..

Finished in 0.00800 seconds
2 examples, 0 failures
$

But when I run the tests from the command line with qunit, I get nothing:

$ xvfb-run bundle exec rake teaspoon DRIVER=capybara_webkit suite=default
Starting the Teaspoon server...
Teaspoon running default suite at http://127.0.0.1:47364/teaspoon/default

$

Note: I set up qunit and jasmine in separate branches. In my qunit branch, my test file is located at test/javascripts/spike_test.js.

Have I missed something?

[jejacks0n]

If make sure your paths are correct in the confit. You can generate the qunit setup using the generator, which is confirmed as working.

---

Jeremy Jackson

On Jul 13, 2015, at 7:18 PM, klenwell notifications@github.com wrote:

Following instructions in README and wiki. Tests run in browser with qunit as expected.

When I set up teaspoon with jasmine and run tests from the command line, they run ok. I see the following output:

$ xvfb-run bundle exec rake teaspoon DRIVER=capybara_webkit suite=default Starting the Teaspoon server... Teaspoon running default suite at http://127.0.0.1:34088/teaspoon/default ..

Finished in 0.00800 seconds 2 examples, 0 failures $ But when I run the tests from the command line with qunit, I get nothing:

$ xvfb-run bundle exec rake teaspoon DRIVER=capybara_webkit suite=default Starting the Teaspoon server... Teaspoon running default suite at http://127.0.0.1:47364/teaspoon/default

$ Note: I set up qunit and jasmine in separate branches. In my qunit branch, my test file is located at test/javascripts/spike_test.js.

Have I missed something?

— Reply to this email directly or view it on GitHub.

[klenwell]

@jejacks0n Yes, I generated the setup for both qunit and jasmine with the generator.

If make sure your paths are correct in the confit.

Do you mean that I should double check my paths in the teaspoon_env.rb file? I used the defaults, which look sane.

[jejacks0n]

Check the project specs then? We can run them from an empty rails app, so you should be able to as well.

---

Jeremy Jackson

On Jul 13, 2015, at 7:39 PM, klenwell notifications@github.com wrote:

@jejacks0n Yes, I generated the setup for both qunit and jasmine with the generator.

If make sure your paths are correct in the confit.

Do you mean that I should double check my paths in the teaspoon_env.rb file? I used the defaults, which look sane.

— Reply to this email directly or view it on GitHub.

[klenwell]

I'd expect the project specs to be consistent between the qunit and jasmine branches I set up. So I don't think that would explain the issue. Unless I'm misunderstanding what is mean by term project specs.

In any event, I'm ready to accept that it's something peculiar to my current project setup. I just wanted to raise the issue here in case there was something obvious that I had missed and as a record in the event somebody else experience the same issue.

[jejacks0n]

Term = repo -- sorry, on mobile.

---

Jeremy Jackson

On Jul 13, 2015, at 9:11 PM, klenwell notifications@github.com wrote:

I'd expect the project specs to be consistent between the qunit and jasmine branches I set up. So I don't think that would explain the issue. Unless I'm misunderstanding what is mean by term project specs.

In any event, I'm ready to accept that it's something peculiar to my current project setup. I just wanted to raise the issue here in case there was something obvious that I had missed and as a record in the event somebody else experience the same issue.

— Reply to this email directly or view it on GitHub.

[mikepack]

I see you're using capybara webkit and you may have run into this now-resolved issue: #403. Could you point your Gemfile at teaspoon master and see if it's fixed?

gem 'teaspoon', github: 'modeset/teaspoon'
gem 'teaspoon-qunit'
gem 'capybara-webkit'

[mikepack]

Closing but will reopen if #403 does not fix the issue.