How to run a test entirely manually

# Assumed in the FrameworkBenchmarks directory to start
# Remove results/installs for a clean-slate
sudo rm -rf results installs
# Change to the testrunner user
sudo su testrunner
# Export some variables you need
export DBHOST=[enter the IP of your DB host here]
export FWROOT=$(pwd)
export IROOT=$FWROOT/installs
# Source the bash functions used by the suite
. toolset/setup/linux/bash_functions.sh
# Change into your test directory; using Gemini as an example:
cd frameworks/Java/gemini
# Export the last various you should need
export TROOT=$(pwd)
# Cat the setup script; using Gemini as an example:
cat start.sh
# This file will have a bunch of commands for getting the 
# Gemini application server running; execute them one by
# one and ensure everything is working appropriately.
# Using Gemini as an example:
# The `fw_depends` can all be on one line, but you can run
# them individually to narrow down a problem with just one
# of them.
fw_depends java
fw_depends resin
fw_depends maven
sed -i 's|db.ConnectString = .*/|db.ConnectString = '"$DBHOST"':3306/|g' Docroot/WEB-INF/GeminiHello.conf
# Go check that `Docroot/WEB-INF/GeminiHello.conf` is properly updated
# etc

# Once you have run all the commands from the setup script,
# the server SHOULD be running. Try to use `curl` to access
# one of the end-points specified in the benchmark_config.

# If you get a proper looking response, you have won.
# If not, you gotta fix something. Check logs etc.