Prepared the structure for testing.

Modified the QrEncoder class.
Added QrEncoderTest.

Author: Martin Brecht-Precht

.gitignore

@@ -1,2 +1,3 @@
 /vendor
-composer.lock
+composer.lock
+vagrantfile

.travis.yml

@@ -0,0 +1,28 @@
+language: php
+
+before_install:
+  - sudo apt-get -qq update
+  - sudo apt-get install -y qrencode
+  - pear config-set preferred_state beta
+  - printf "\n" | pecl install imagick
+  - echo "extension=imagick.so" >> ~/.phpenv/versions/$(phpenv version-name)/etc/php.ini
+  - php -m
+
+branches:
+  only:
+    - master
+
+php:
+  - '5.3'
+  - '5.4'
+  - '5.5'
+  - '7.0'
+  - hhvm
+
+install:
+  - composer install
+
+matrix:
+  allow_failures:
+    - php: hhvm
+    - php: '5.3'

CONTRIBUTING.md

@@ -68,6 +68,33 @@ Any bugfix that doesn’t include a test proving the existence of the bug being
 
 We’ve found that test-first development really helps make features better architected and identifies potential edge cases earlier instead of later. Writing tests before the implementation is strongly encouraged.
 
+Sometimes testing is hard because it is not possible to create an environment on the developers machine to fulfill the softwares requirements in the middleware setup. For example installing imagick on Mac OS X could be a task straight out of hell. In this case it is useful to provide a out-of-the-box running machine setup like [docker](https://www.docker.com/) ot [vagrant](https://www.vagrantup.com/) and run tests on the virtual machine via the commandline interface.
+
+## Contributing requirements
+
+For development purposes there is a [vagrant](https://www.vagrantup.com/) setup included in the repo to fulfill the server side requirements easily. 
+
+### Installation and testing example (Mac OS X)
+
+#### Installation of vagrant
+
+Get your vagrant version from [https://www.vagrantup.com/downloads.html](https://www.vagrantup.com/downloads.html) and run the installer. 
+
+#### Starting the virtual machine and connect via SSH
+
+```
+cd php-qr-code-suite
+vagrant up
+vagrant ssh
+```
+
+#### Running the tests via command line interface
+
+```
+cd /var/www/php-qr-code-suite
+phpunit --bootstrap vendor/autoload.php --configuration phpunit.xml.dist
+```
+
 ## Full example
 
 Here’s an example workflow for `php-qr-code-suite` hosted on Github, which is currently in version 2.0.x. Your username is `yourname` and you’re submitting a basic bugfix. 

composer.json

@@ -24,12 +24,15 @@
   ],
   "autoload": {
     "psr-4": {
-      "QrCodeSuite\\": ""
+      "QrCodeSuite\\": "src/"
     }
   },
   "require": {
     "php": ">=5.3",
     "ext-gd": "*",
     "ext-imagick": "*"
+  },
+  "require-dev": {
+    "phpunit/phpunit": "~4.8"
   }
 }

phpunit.xml.dist

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<phpunit colors="true" bootstrap="vendor/autoload.php">
+	<testsuites>
+		<testsuite name="QR Code Suite Testsuite">
+			<directory>test</directory>
+		</testsuite>
+	</testsuites>
+</phpunit>

QrEncode/Exception/QrEncoderException.php renamed to src/QrEncode/Exception/QrEncoderException.php

@@ -142,4 +142,12 @@ public function replaceRow($index, QrCodePointRow $row)
 		return $this;
 	}
 
+	/**
+	 * @return int
+	 */
+	public function countRows()
+	{
+		return count($this->rows);
+	}
+
 }

QrEncode/QrCode/QrCode.php renamed to src/QrEncode/QrCode/QrCode.php

@@ -80,4 +80,12 @@ public function replacePoint($index, QrCodePoint $point)
 		return $this;
 	}
 
+	/**
+	 * @return int
+	 */
+	public function countPoints()
+	{
+		return count($this->points);
+	}
+
 }