| #!/bin/bash | |
| launchctl unload -w /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist | |
| launchctl unload -w /Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist | |
| launchctl unload -w /Library/LaunchAgents/com.adobe.ARMDCHelper.cc24aef4a1b90ed56a725c38014c95072f92651fb65e1bf9c8e43c37a23d420d.plist | |
| launchctl unload -w /Library/LaunchDaemons/com.adobe.agsservice.plist | |
| launchctl unload -w /Library/LaunchDaemons/com.adobe.ARMDC.Communicator.plist | |
| launchctl unload -w /Library/LaunchDaemons/com.adobe.ARMDC.SMJobBlessHelper.plist | |
| launchctl unload -w /Library/LaunchDaemons/com.adobe.adobeupdatedaemon.plist | |
| sudo launchctl unload -w /Library/LaunchDaemons/com.adobe.ARMDC.Communicator.plist |
Despite of they feel to be almost the same, there is a subtle difference between them: In request specs, you can exercise the full stack of a HTTP request (from routing to the view layer, so to speak).
Request specs also allows you to access more than one endpoint at a time, so you are able to test a whole scenario’s flow, whereas in controller specs you can exercise only one endpoint per test case (i.e., a single controller’s action).
# request spec
specify do
get '/my-first/enpoint'
| #!/bin/bash | |
| if [ "$1" == "" ]; then | |
| echo Usage: $0 pngfile | |
| exit 0; | |
| fi | |
| FILE=`basename $1 .png` | |
| if [ ! -e $FILE.png ]; then |
Get Homebrew installed on your mac if you don't already have it
Install highlight. "brew install highlight". (This brings down Lua and Boost as well)