LOAD_PLUGINS=1 QUNIT_SKIP_CORE=1 QUNIT_SINGLE_PLUGIN='discouse-humble-box' /home/ravenstorm/.rbenv/versions/2.5.3/bin/rake qunit:test Chrome is not installed. Download from https://www.google.com/chrome/browser/desktop/index.html rake aborted! Command failed with status (1): [LOAD_PLUGINS=1 QUNIT_SKIP_CORE=1 QUNIT_SIN...] /home/ravenstorm/discourse/lib/tasks/plugin.rake:117:in `block in <main>' Tasks: TOP => plugin:qunit
Install Chrome and then give it another try.
Oh sorry i’ve pasted an old error code which i had stored in a pastebin
navigate to http://localhost:60099/qunit?qunit_single_plugin=discouse-humble-box&qunit_skip_core=1&seed=187998423095278311109560784485973475676 Tests timed out rake aborted! Command failed with status (124): [node /home/ravenstorm/discourse/vendor/ass...] /home/ravenstorm/discourse/lib/tasks/qunit.rake:89:in `block in <main>' Tasks: TOP => qunit:test (See full trace by running task with --trace) rake aborted! Command failed with status (1): [LOAD_PLUGINS=1 QUNIT_SKIP_CORE=1 QUNIT_SIN...] /home/ravenstorm/discourse/lib/tasks/plugin.rake:117:in `block in <main>' Tasks: TOP => plugin:qunit
Try running the test in the browser as David suggested earlier. So, in your browser, when the server is running, go to
your-local-site/qunit. Very often, for me, timeouts in the Terminal have errors in JS that I could see and fix after visiting
/qunit on the browser.
Thats one of the problems
I can’t find acceptance tests on my
Even after turning on all modules and filtering it with
humble nothing is here
s is quite important!
You might need to do
rm -rf tmp, and then restart your development server for the changes to take effect.
Do what David said above (rename the folder to
discourse-humble-box to match the folder name. I did these two changes, and I see tests locally:
Yea i’ve seen those as well now, but these aren’t really eye-opening results tbh.
But gotta dig deeper and lookup why these errors are shown.
Thanks for the help guys.
For example the second test case… if i am testing it myself by hand… it works, but running it on qunit it fails
Ok, got a brief idea whats bringing me the errors and it confuses me:
http://localhost:9292/ in my browser has the plugin installed and working
http://localhost:9292/qunit the test shows, that the plugin is not even installed
I thought these two are using the same enviroment ?
Could this be caused by my local dev-enviroment since it’s not using docker and I’m not able to install the plugin like Install Plugins in Discourse ? It’s just sitting in the
plugins folder like the others.
Any idea how this is possible ?