@roramirez & @MichMich looks like develop branch got broken with this commit https://github.com/MichMich/MagicMirror/commit/354b745c39a19915c3a8547445a5049555bd37ff#diff-75953debd6cf3faf33d4ff10e8353645R11

Line 11 of defaults.js got this change port: process.env.MM_PORT || 8080, and server is not starting up throwing error in the console log:

Uncaught ReferenceError: process is not defined
    at defaults.js:11
(anonymous) @ defaults.js:11

@ESOB This error WARNING! Could not load config file. seems very odd. Can you please post your config.js file? Also another option is to backup your config.js and do file copy of config.js.sample to config.js to have good known configuration to begin with.

When starting with npm start dev or node serveronly do you see any errors in the Console Log of the dev tools of the electron or your browser?

P.S. I wanted to fork this troubleshooting conversation into a separate thread, but can’t seem to find a way.

@ESOB sorry I was replying before you edited post with update. Try temporarily changing your config.js to another port if 8080 is taken for some reason.

@ESOB did you run npm install after pulling development branch? Next step would be to try to start it in node serveronly mode and point your browser at http://:8080 or run npm start Dev and see if you get any errors in console log of the browser or electron app

@ESOB looks like your port 8080 is in use. Do you happen to have another instance of MM running already? Or maybe something else is taking your port 8080.

@istepgueu I will look into it. may need some help with translations.

Just quickly glanced at it and it seems that RSS feed doesn’t have complete text of the horoscopes only partial information. I’m not sure how useful it would be when displayed on the MM

For example here is the text from RSS feed

Amour : 31 01 2017 Vous aimeriez bien vous changer les idées auprès de votre...<br>Travail : 31 01 2017 Une bonne stratégie vous évitera de perdre du temps dans des...<br>Vitalité : 31 01 2017 Avec Mars dans votre secteur d'ombre, vous ne serez pas à l'abri d'un...<br>Humeur : 31 01 2017 Vous ferez de votre mieux pour ne pas prendre les choses qui n'en valent...<br /><a href="https://www.horoscope.fr/horoscopes/horoscope_taureau.html" title="Horoscope du taureau">Horoscope du taureau</a> ou visitez ce site : <a href="http://www.voyanceprivee.org" title="voyanceprivee.org" rel="nofollow">voyanceprivee.org</a>

It would look like this (after some formatting):

Amour : 31 01 2017 Vous aimeriez bien vous changer les idées auprès de votre...
Travail : 31 01 2017 Une bonne stratégie vous évitera de perdre du temps dans des...
Vitalité : 31 01 2017 Avec Mars dans votre secteur d'ombre, vous ne serez pas à l'abri d'un...
Humeur : 31 01 2017 Vous ferez de votre mieux pour ne pas prendre les choses qui n'en valent...

@washichi TBH I have too many to list. (for this project I mostly use SublimeLinter main package in combination with SublimeLinter-contrib-eslint, also use PrettyJSON for validation and formatting cleanup)

Where are you getting this error? What’s your MagicMirror/modules directory structure looks like?

@roramirez cool thanks. I have it all ready on my fork. Will submit PR for review.

@roramirez I’ve played a little with test suite and added basic test for clock module. Then I realized that if we want to test different config options for a given module we may need to have to create multiple configs, which may be challenging with current tests directory organization.
Also I believe that process.env.MM_CONFIG_FILE = "tests/confs/config_name.js" line needs to be moved into before step (seems to work there or it can go into beforeEach if needed). Otherwise when running npm run test:e2e first config that gets picked up seems to persist throughout all of the tests and always used by the app.js.

I was wondering if structure similar to this makes sense:

tests
├── configs
│   ├── env.js
│   └── modules
│   │   └── clock
│   │   │   └── clock_12hr.js
│   │   │   └── clock_24hr.js
│   │   │   └── clock_analog.js
│   │   └── helloworld
│   │       └── helloworld.js
├── e2e
│   ├── env_spec.js
│   └── modules
│       ├── clock_spec.js
│       └── helloworld_spec.js
├── functions
│   └── compare-version_spec.js
└── global_vars
    └── root_path.js

but this would involve changing app.use("/tests/confs", express.static(path.resolve(global.root_path + "/tests/confs"))); in the server.js to be somewhat dynamic and I’m not very familiar with express on how it can be done. I think that’s easily solved by just changing it to app.use("/tests/configs", express.static(path.resolve(global.root_path + "/tests/configs")));

@fersev what is fade in/fade out switch?

@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?