Makefiles specify commands for the `make` command in the current folder. By using `make` we can be nicer to new developers as they need to remember less commands. For example, to "run buildout" you previously had to run: - virtualenv -p python2.7 . - bin/python boostrap.py -d - bin/buildout Now, you just run ``make``. That's it. Make will run those three commands above for your. Similar for tests and syntax validation: - bin/test -s eestec.portal - bin/flake8 src/eestec/portal Now, you just run ``make tests``. To generate documentation run ``make docs``. Nice, ain't it?
This adds support to have demo/dummy content installed in your Plone instance or in your tests. Installation is done with a custom GenericSetup extension profile, while content gets created with the help of `quintagroup.transmogrifier`. There is also a convenience buildout config file `demo.cfg` which automagically creates a Plone instance with demo content upon running `bin/buildout`. Above all, Travis CI builds now first create an instance with demo content (to make sure demo content import works) and only then continues with running unit tests.
…ng stuff for testing @@register