TYPO3 Core

As a user I want to have acceptance testing to ensure functionality is still working after developers changed everything.
As a developer I want to be able to write acceptance tests in a way that I understand (language/framework wise).

• After every merge to master acceptance tests are run by travis.
• Acceptance tests may be written in either PHP or JavaScript.
• Infrastructure for acceptance testing can be setup by every developer on his own (documentation exists!)

• Travis configuration
• Codeception as dependency in composer.json (require-dev)
• Base configuration / setup for codeception based on phantomJs and the php server
• Base data package for installation of TYPO3 (database, possibly introduction package...)
• First backend test that checks if the login is displayed