Hello Everyone!

With @morozgrafix we are working to create a space for MagicMirror in Slack.

This brings a space for discution about new the features, bugs and improvement.

Initially the focus in a for/to developers, where we can living together to improve every day MM.

So, if you are interested and you are owner a module or core contributor (some patch is enough) please contact where I can send you the invitation or say Hi here if you email is available in your profile where send the invitation.

@nwootton You can use the testsuite for kickoff. A good point in the future if we can integrate the modules test can be run inside the testsuite of MM.

@strawberry-3.141 said in config error somewhere, need help:

https://twitter.com/roramirez/ status/843121280601669632

:)

This feature is include in the last release. Now you can use npm run config:check for check the configuration file :)

@Sean So, can be there a bug with using that browser. What version of Chrome is?

@Sean If you start with npm start dev, do you have the same problem?

@Mykle1 said in Electron CPU usage:

Perhaps @roramirez has some input here

What version of electron did you is installed in the system?

@wtidwell Can you share the configuration when did you get a big CPU usage?

What version are you using?

@gekberlin There a module https://github.com/nrkno/MMM-Slack you can try.

@surger13 That part is controller by moment.js. It’s not possible configurated. Only way to make this is change the source code of calendar.js in the module directory.

@Cato Hi!, The documentation for tests are living only in test source ;) This is something. We need to an better documentation.

Are you interested to do it? https://trello.com/c/UwqL27A3/29-add-documentation-of-testsuite

I’m not a very good at writing documentation.

But in short terms,

The tests are living in tests directory, there two kind of test, unit and e2e.

We are using mocha and spectron`, the last one is for the tests of e2e. For every e2e test is using a configuration file. When the test run load the configuration file and we check expected result of the MagicMirror instance in Electron mode.

You can using the follow sentences to run testsuite

• Unit test: npm run test:unit
• E2e tests: npm run test:e2e
• Unit + e2e: npm test

If you can run especific test you need execute mocha from your path where is installed, in my case inside of MagicMirror directorio. Example of running the specific unit test for calendar functions.

NODE_ENV=test ./node_modules/mocha/bin/mocha tests/unit/functions/calendar_spec.js

Result:

  Functions into modules/default/calendar/calendar.js
    capFirst
      ✓ for 'rodrigo' should return 'Rodrigo'
      ✓ for '123m' should return '123m'
      ✓ for 'magic mirror' should return 'Magic mirror'
      ✓ for ',a' should return ',a'
      ✓ for 'ñandú' should return 'Ñandú'
    shorten
      ✓ for ' String with whitespace at the beginning that needs trimming' should return 'String with whit…'
      ✓ for 'long string that needs shortening' should return 'long string that…'
      ✓ for 'short string' should return 'short string'
      ✓ for 'long string with no maxLength defined' should return 'long string with no maxLength defined'
      ✓ should return an empty string if shorten is called with a non-string
      ✓ should not shorten the string if shorten is called with a non-number maxLength
      ✓ should wrap the string instead of shorten it if shorten is called with wrapEvents = true (with maxLength defined as 20)
      ✓ should wrap the string instead of shorten it if shorten is called with wrapEvents = true (without maxLength defined, default 25)


  13 passing (29ms)

If need something is not clear let me know.