1. Studio Fx on Rails Demonstrating the Studio Fx API

2. Requirements Software – Ruby >= 1.8.6 – Rails >= 2.3.2 gem install rails – MySQL >= 5 – Other Ruby Gems to install xml/libxml net/https Hardware (tested) – Mac OS X – Linux

3. MySQL Install and configure MySQL – Linux example yum install mysql yum install mysql-devel yum install mysql-server chgrp -R mysql /var/lib/mysql chmod -R 770 /var/lib/mysql service mysqld start – set the passwords for your root account: /usr/bin/mysqladmin -u root password 'new-password’ Open MySQL and create the database – mysql –u root –p – create database ddt_development;

4. Studio Fx On Rails Check out the source from mu-labs google_code: – http://code.google.com/p/mu- labs/source/browse/trunk/analyzer/automation/S tudio_Fx_On_Rails http://code.google.com/p/mu- labs/source/browse/trunk/analyzer/automation/S tudio_Fx_On_Rails

5. Create the Database Tables Edit /config/database.yml – set the name of the MySQL database – set the MySQL root password Create the database tables – From : rake db:migrate This will create the tables that are defined in the db/migrate directory (‘runs’ and ‘results’)

6. Run Rails Start the Rails server. From, run: – ruby script/server Open the browser to Rails – http:// :3000 http:// :3000 You should see the Rails Home Page – (next slide) Continue on to the Studio Fx Home Page – http:// :3000/runs

7. Rails Home Page

8. Studio Fx on Rails / Runs

9. Load templates from a Mu From the ‘Runs’ page: – Enter the IP address of the Mu – Click the 'Get Templates/Set IP' button Loads all of the Mu’s templates for – Testbeds – Targets – Scenarios – Testsuites

10. Create a New Test Run: 1 Click on the ‘New Run’ link and see:

11. Create a New Test Run: 2 Select Testbed, Target, Scenario and Testsuite

12. Create a New Test Run: 3 Click on the ‘Create’ button and see:

13. Create a New Test Run: 4 Click on the ‘Back’ link to see the new Run

14. Run the Testsuite Click on the ‘Execute’ link to run the test suite – The browser will be busy until the test is completed – When the test is done, click on the ‘Results’ link to view the test results

15. View the Results

16. View Results Details Click on the ‘Show’ link to view more details, including the options and their values

17. Filter the Results The results can be filtered by test name, run_id or both, and, in all cases, to see only the 'latest' results /results?name=testname&run_id=1 /results?name=testname&run_id=1&latest /results?run_id=1 /results?run_id=1&latest /results?name=testname /results?name=testname&latest

18. Filtered Results

19. Sample Code Most of the interesting code is found here: – /app/models/run.rb This code executes the Rails back-end commands, creating the DdtApi object and invoking its methods – /lib/ddt_api.rb The DdtApi class is where all of the Mu Studio Fx API code is invoked

20. Mu Template fetching When we collected the templates from the Mu, we used a Mu REST Api – https:// /rai/rest/mu/findUsing?type= https:// /rai/rest/mu/findUsing?type – type was Testbed, Target, Scenario and DDTSuite The test tool collected the responses and parsed them into hash maps, using the template names as keys and the uuid’s as values

21. Test Execution Executing the tests (run.rb:run_test) invoked the following sequence of calls from the DdtApi class: – new_session – testbed(testbed_uuid) – target(target_uuid) – setup_session – scenario(scenario_uuid) – run(testsuite_uuid)

22. Collecting Results After the test completes, the tool: – calls the DdtApi.collect_results method – parses the results – adds them to the MySQL database (results table)

23. Other DdtApi methods Studio Fx on Rails does not use all of the DdtApi methods. Other available methods include – Methods that manage csv files (import, export, post, run, and eval (preview)) – post_template (to send a scenario or other xml template to the Mu) – teardown_session (invoked when you are finished using the Mu)