@roramirez I just submitted PR to add chai-as-promised to devDependencies. I was missing it from globally installed packages and ran into an error when tried to run tests.

I just stick with SublimeText 3 on my MacBook and develop most of the stuff while running node serveronly and pointing Chrome at localhost:8080. Been using sublime with tons of add-on packages (including code linters) for years now and very happy with it. When things are ready I SSH to my RasPi and test on it. As @yawns said, the only drawback of this is that you can’t work with GPIO and other RasPi proprietary things while developing locally. I haven’t ran into many problems with that. There is also an scp package that can copy files to remote on save, I use that when I need to run directly on RasPi.

If folks find it helpful. I can copy contents of that gist here. Just let me know.

Nice write up and cover story. Saw it over the weekend. Congrats!

I haven’t looked thoroughly at the code and I wanted to suggest setting a default timeout that can be overwritten in individual tests as needed. It may make test code a little bit cleaner and less repetitive.

Good job getting it going!

@simongaviria1 there are still a few limitations that I haven’t solved. It was more of an experiment to see if it would run.

@yawns Thanks! I just added a small bit related to installation steps to the README.

@pflnpi0305 It will not work if you don’t have a copy of the module installed locally, black screen is there because MM is attempting to load JS files for the module from the directory that doesn’t exist. You need to run this in terminal while connected to your RasPi (directly or via SSH).

cd ~/MagicMirror/modules
git clone https://github.com/morozgrafix/MMM-horoscope.git

After that you would need to restart MM node process in order it to pickup new node_helper for horoscope module.

Thanks

@pflnpi0305 Do you see any errors in the console log when you run it start the mirror with npm start dev command? Also are you running off the master branch or dev?
We can try to start eliminating things out to narrow down what is causing the black screen for you.

Can you try this config with only horoscope module:

/* Magic Mirror Config Sample
 *
 * By Michael Teeuw http://michaelteeuw.nl
 * MIT Licensed.
 */

var config = {
	port: 8080,
	ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1"],

	language: 'en',
	timeFormat: 24,
	units: 'metric',

	modules: [
		{
			module: 'MMM-horoscope',
			position: 'bottom_right', // This can be any of the regions.
			config: {
				// See ‘Configuration options’ for additional options and more information.
				sign: 'aries', // Zodiac sign
				}
		},
	]

};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== 'undefined') {module.exports = config;}

Also can you please double check that MMM-horoscope and contents exist under ~/MagicMirror/modules directory? (I know I’m asking for obvious things, just trying to get some more info about your installation).

@pflnpi0305 if you are using pm2 then you can restart mm with pm2 restart mm, to stop it you would run pm2 stop mm, to list processes managed by pm2 you would do pm2 list and to start you would run pm2 start mm

If you are still have issues, post your latest version of config.js here again. Are you getting any errors?