Testing against dev builds

[FichteFoll]

It's currently not possible to test against the dev builds. This would require:

1. Downloading and installing the dev build (easy on Windows).
2. Somehow providing an interface to place a valid license in the correct location to allow execution of the dev build.

Travis CI has a kind of "secret value setting" thing where you can provide secret information that is not part of .travis.yml, but I don't exactly remember how it works, nor have I ever used it.

[randy3k]

It is more difficult than @guillermooo's https://github.com/randy3k/UnitTesting/issues/25

1. I don't know enough to make it possible. Unless brew cask and apt-get provide installations of the dev build, I found no ways to install the dev builds on Travis-CI.
2. Not sure if there is a way to activate Sublime via command line.

[FichteFoll]

2. If ST finds a license file (either XORed with system info or plain) at the usual location, it is activated. By copying the license to the correct location, ST gets activated.

[buildersbrewery]

2. You cannot assume that the system info will stay the same when using Travis, so this leaves us with plain text license files. Which will be happily used by anyone who comes along until Jon or Will add it to the blacklist of the next release.

In other words, I guess this can be closed as "wontfix".

---

This is the same reason #43 was closed.

[randy3k]

In fact, we could use Travis encrypted secret for this purpose. Though it does not work on PRs which reduces the usability of such feature.

[buildersbrewery]

... Though it does not work on PRs which reduces the usability of such feature.

...yeah