From 2e65cd6c9810e7b684ec9c80a659e76340eb705e Mon Sep 17 00:00:00 2001
From: Rob Levin <rlevin@sugarcrm.com>
Date: Sat, 24 Nov 2012 17:25:39 -0800
Subject: [PATCH] Added phpunit boiler plat snippet.

---
 README.md                     |  1 +
 php-unit-test.sublime-snippet | 27 +++++++++++++++++++++++++++
 2 files changed, 28 insertions(+)
 create mode 100644 php-unit-test.sublime-snippet

diff --git a/README.md b/README.md
index 7972cd4..7d07ad8 100644
--- a/README.md
+++ b/README.md
@@ -26,6 +26,7 @@ __ For PHP files:__
 * __php-mit__: insert the MIT license as a PHP docblock
 * __php-newbsd__: insert the new BSD license as a PHP docblock
 * __php-section-comment__: insert a prominent comment to help break up the sections of your class
+* __php-unit-test__: Generates PHPUnit scaffolding for a particular SUT (system under test).
 
 Contributions Welcome
 ---------------------
diff --git a/php-unit-test.sublime-snippet b/php-unit-test.sublime-snippet
new file mode 100644
index 0000000..c182036
--- /dev/null
+++ b/php-unit-test.sublime-snippet
@@ -0,0 +1,27 @@
+<!--
+    php-stacktrace
+        Insert stacktrack in your error_log. This is useful if you need to quickly see the call stack for an unfamiliar peice of code that's deep within a system.
+
+    HOW TO USE
+        In your PHP class, simply type the following:
+
+            php-stack-trace<TAB>
+
+        Sublime Text will add the stacktrace code for you. Then use <TAB> to add a grep friendly token to your log message.
+-->
+<snippet>
+    <content><![CDATA[
+require_once('${1:[Class Name (system under test) ... ]}.php');
+
+class ${1:[Class Name (system under test) ... ]}Tests extends PHPUnit_Framework_TestCase
+{
+    public function test${2:[SomeThingUsefulToTestGoesHere]}()
+    {
+        ${3:// code...}
+    }
+}
+]]></content>
+    <tabTrigger>php-unit-test</tabTrigger>
+    <scope>source.php</scope>
+    <description>Generates PHPUnit scaffolding for a particular SUT (system under test).</description>
+</snippet>
\ No newline at end of file