1. Snippets should use placeholders for user information in a format that resembles the original value. For example:

   Account SID: ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
   Call SID:    CAXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
   API Key:     SKXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
   

   Note: This is important as Twilio libraries use these values as a part of the URL for API requests. When testing the snippets real requests will be made to a fake server.

   In the case of phone numbers, the following should be used:

   Destination Phone Number: +15558675309
   From/Twilio Number: +15017250604
   

   For auth_token:

   Auth Token: your_auth_token
   

2. Snippet file names are important. A snippet's file extension is the only way to mark them for a specific language. This is important because the language will be visible on the docs. Also, you must mark snippets with the twilio-client version that is used in that particular snippet.

   For example, a java snippet that uses twilio-java v7.x should be named as follows:

   any_snippet_name.7.x.java

   The same applies to the rest of languages and library versions, and this is the list of currently supported languages and versions:

   any_snippet_name.6.x.java
   any_snippet_name.7.x.java
   any_snippet_name.2.x.js
   any_snippet_name.3.x.js
   any_snippet_name.4.x.rb
   any_snippet_name.5.x.rb
   any_snippet_name.4.x.cs
   any_snippet_name.5.x.cs
   any_snippet_name.4.x.php
   any_snippet_name.5.x.php
   any_snippet_name.5.x.py
   any_snippet_name.6.x.py
   any_snippet_name.json.curl
   any_snippet_name.xml.curl
   

   Client version is important, as that is how the test harness knows which version of the client it should use for testing.

This repository is configured to test that a snippet is valid. For compiled languages, this means just compiling the snippet, and for dynamic languages, actually running the snippet. If a snippet makes requests to the Twilio API, they will be made to a fake API server If you want a snippet to be tested, there are two ways to mark it as testable:

1. Mark a specific snippet for testing.

   You can mark a specific snippet for testing by adding a "testable" field in the meta.json file like this:

   {
     "title": "Snippet title",
     "type": "server",
     "testable": true
   }
   

2. Mark an entire directory as testable.

   You can also mark entire directories as testable. If the marked directory contains several snippets, all of them will be marked as testable recursively. To mark a directory for testing, create a test.yml in the root of the directory you want to mark as testable with a testable field like this:

   testable: true
   

Notes:

1. You can mark a directory or a snippet to be not testable too.

   meta.json -> "testable": false
   test.yml -> testable: false
   

   This way, you can mark snippets or directories to be tested or not, by exception.
2. For a snippet to be testable, it has to contain the basic things a program in that language should have. For example in Java, the code snippet should have a public class and a main method in it.
3. Specific dependencies are supported for snippets. If a new dependency is introduced, the testing scripts should be modified to support it.

The current status of the snippet tests allows to test snippets only in the rest/, pricing/ and security directories.

The next steps describe how to run the snippets test locally in a UNIX based operating system (examples will be provided for Debian based Linux distributions and OSX using Homebrew). This has not been tested in a Windows OS.

You can take a look at the .travis file on this repository to find out what dependencies and tasks are required in order to run the snippet tests. But, a detailed list of steps will be provided next.

Make sure you have the following dependencies installed on your system.

1. Install Node.js.

   On Linux:

   $ curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
   $ sudo apt-get install -y nodejs
   $ sudo npm install -g n
   $ sudo n lts

   On OSX:

   $ brew install node
   

2. Install Python and PIP.

   On Linux:

   $ sudo apt-get install python-pip python2.7-dev build-essential
   $ sudo pip install --upgrade pip

   On OSX:

   $ brew install python

3. Install JDK8 and Gradle.

   On Linux:

   $ sudo add-apt-repository ppa:webupd8team/java
   $ sudo add-apt-repository ppa:cwchien/gradle
   $ sudo apt-get update
   $ sudo apt-get install oracle-java8-installer
   $ sudo apt-get install gradle

   On OSX:

   Download OSX JDK8 installer from http://www.oracle.com/technetwork/java/javase/downloads/index.html

   $ brew install gradle

4. Install PHP 5 with CURL.

   On Linux:

   $ sudo apt-get install curl php5-cli php5-curl curl

   On OSX:

   $ brew install homebrew/php/php55

5. Install Composer.

   $ curl -sS https://getcomposer.org/installer | sudo php -- --install-dir=/usr/local/bin --filename=composer

6. Install Ruby and RubyGems.

   $ curl -sSL https://get.rvm.io | bash -s stable --ruby

7. Install MonoDevelop.

   On Linux (http://www.mono-project.com/docs/getting-started/install/linux/#usage):

   $ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
   $ echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
   $ sudo apt-get update
   $ sudo apt-get install mono-complete

   On OSX:

   $ brew install mono

The testing and installation scripts use ruby. Before installing language dependencies you need to install the following gems:

$ gem install json
$ gem install colorize
$ gem install parallel

You can use the following command to install dependencies in your system:

$ ruby tools/snippet-testing/model/dependency.rb

This will download all the necessary dependencies for the snippets to run. You can also pass the -i flag to the testing command you'll use in the next step, like this:

$ ruby tools/snippet-testing/snippet_tester.rb -i

Note: This will also install missing dependencies before running the tests. sudo will be used within the dependency installation script so you might need to enter your password. Do not run the whole script with sudo as it would install dependencies for the wrong user.

1. Clone and run the fake-api server in a different terminal session.

   $ git clone [email protected]:TwilioDevEd/twilio-api-faker.git
   $ cd twilio-api-faker
   $ sudo gradle run

2. Make your system trust the fake server's self signed certificate.

   On Linux:

   $ sudo apt-get install ca-certificates
   $ sudo cp twilio-api-faker/keystore/twilio_fake.pem /usr/local/share/ca-certificates/twilio_fake.crt
   $ sudo update-ca-certificates

   On OSX:

   Use the system's keychain to trust the provided certificate in the keystore directory of the fake-api repo. Go here for more information.

3. Change your hosts file.

   Edit your /etc/hosts file. Add the following entries:

   127.0.0.1 notifications.twilio.com
   127.0.0.1 notify.twilio.com
   127.0.0.1 taskrouter.twilio.com
   127.0.0.1 api.twilio.com
   127.0.0.1 lookups.twilio.com
   127.0.0.1 pricing.twilio.com
   127.0.0.1 monitor.twilio.com
   127.0.0.1 ip-messaging.twilio.com
   

4. Export Necessary Environment Variables.

   This repository includes a .env.example file. Change it to match your configuration and the use the source command to export the variables.

   $ source .env.example

5. Finally, run the tests.

   $ ruby tools/snippet-testing/snippet_tester.rb

   Note: Remember to mark the directories you want to be tested with a test.yaml file. For more information go here.

   You can also specify a directory to be tested (relative or absolute path). If a directory is specified, then the default testing behavior for that directory and everything it contains is true.

   $ ruby tools/snippet-testing/snippet_tester.rb -d rest/making-calls