search

twolfson / sublime-plugin-tests

Testing framework for Sublime Text plugins
The Unlicense
22 stars 2 forks source link

ST2 and vagrant #28

Closed randy3k closed 10 years ago

randy3k commented 10 years ago

continue the discussion in https://github.com/twolfson/sublime-plugin-tests/pull/27#issuecomment-36101394

I have been trying to use it on vagrant. When I run the test for ST2 I got the following.

vagrant@precise64:/vagrant$ nosetests -v
test_left_delete_multi (sublime-plugin-tests_test.TestLeftDelete) ... Xlib:  extension "RANDR" missing on display ":99.0".
Unable to connect to dbus

I have no problem with ST3 through... Do you have any thoughts?

twolfson commented 10 years ago

Is this the sublime-plugin-tests test suite or your own repo?

randy3k commented 10 years ago

I am trying sublime-plugin-tests with a vanilla vagrant. Finally, i figured out why. I didn't set the environment variable SUBLIME_AUTO_KILL for ST2. 

export SUBLIME_AUTO_KILL=TRUE

solves my problem.

twolfson commented 10 years ago

Hooray! =)

randy3k commented 10 years ago

I just wonder why we have to specify this variable. If it is something important, why not hard code it in the package.

twolfson commented 10 years ago

It allows you to run Sublime Text outside of Vagrant in your normal host environment. This means you can develop inside the same version of Sublime you are developing against without needing to re-open Sublime after every test run =P

randy3k commented 10 years ago

Obviously, I am not getting any benefits for being a Mac user..

twolfson commented 10 years ago

Actually, it is supposed to work against Python 2/3 and all OS'es. Unfortunately, I rage quit active development on this shortly after releasing. Headless testing environments for a GUI will frustrate you like no other.

If you are interesting in getting Mac support working, look into sublime-info. If you get the paths properly resolving, then the higher level modules should fall like dominoes.

https://github.com/twolfson/sublime-info