Clone wiki

ProjectplaceSublimeTestRunner / Home

Sublime Plugin

So this is the start of and epic adventure into the wonderful world of Sublime Text + Projectplace Unit tests.

How to get this thing to work on your machine

1.. Make sure you have installed Package Control in Sublime. If not head over here and learn how to do it:

2.. In Package Control search for "Add Repository" (cmd+shift+P on the mac to bring up the "search" field). Add to you managed repositories.

3. Search for "Install Package" in the Package Control. Please disable any vpn connections before this otherwise it might not work.

4. Search for ProjectplaceSublimeTestRunner, in the Install Package.

5. Install

6. Update the Sublime Project File. Open your .sublime-project file to edit(yes, this plugin needs some settings and these settings are saved in the sublime project file).

Add the projectplace_test_runner to the settings part like this:

            "root_dev_env": "<CHANGE TO YOU ROOT PREFIX",
            "domain":"<THE DOMAIN YOUR DEV ENVIRONMENT IS ON",
            "run_on_save": "1 or EMPTY"

root_dev_env will be something like ole, apr or shd. In other words, you personal dev environment prefix.

domain will be for Bangalore developers and for Stockholm developers

run_on_save (Optional) Add a single 1 as value and then sublime will run the associated test file when you save the file. Leave it empty if you do not want this, or remove the setting all together.

7. You are done. Happy testing!

Make a change to the plugin

1. Clone this repo into your the following place depending on your OS

~Library/Application Support/Sublime Text 2/Packages 


C:\Users\olled\AppData\Roaming\Sublime Text 2\Packages



Hack away and push improvements.

The good thing with Sublimes way to handle plugins is that your changes will be instantly visible inside you Sublime editor..

When you want to push an update to all clients with the plugin installed, you will need to:

2. Update the following variables in the packages.json file

"last_modified": "<NEW DATE LIKE 2013-03-13> <NEW TIME STAMP LIKE 17:00:00>"
"version": "<NEW VERSION>"

You add a description of your epic change, add a new version variable in messages.json like:

"0.0.7": "messages/0.0.7.txt"

Now you just need to create a new 0.0.7.txt file in the message directory describing your epic change! Push you changes and the clients can update to the new version of the plugin!

Good luck!