Files
SwiftShell/SwiftShellTests/Scripts/runtests.bash
T
Kare Morstol a7a68866a1 Use $SWIFTSHELL_FRAMEWORK_PATH instead of $DYLD_FRAMEWORK_PATH in the swiftshell launcher script.
Because of this change in El Capitan:

	"Spawning children processes of processes restricted by System Integrity Protection, such as by launching a helper process in a bundle with NSTask or calling the exec(2) command, resets the Mach special ports of that child process. Any dynamic linker (dyld) environment variables, such as DYLD_LIBRARY_PATH, are purged when launching protected processes."

https://developer.apple.com/library/prerelease/mac/documentation/Security/Conceptual/System_Integrity_Protection_Guide/RuntimeProtections/RuntimeProtections.html
2015-11-09 22:07:23 +01:00

32 lines
1.1 KiB
Bash
Executable File

#!/usr/bin/env bash
PROJECT_ROOT=../..
# Build the framework and record any errors.
BUILDERRORS=$(xcodebuild -project $PROJECT_ROOT/SwiftShell.xcodeproj/ 2>&1 >/dev/null)
# If there were any errors (exit code is not 0), print them and exit.
if [ $? -ne 0 ]; then
printf "$BUILDERRORS \n"
exit 1
fi
# Make sure the swiftshell script will use the newly built framework.
export SWIFTSHELL_FRAMEWORK_PATH=$PROJECT_ROOT/build/Release/
# Import the unit testing script.
. assert.sh
# Be aware the “assert” command does not check standard error output or exit code.
assert "./print_arguments.swift 1 2" "[\"./print_arguments.swift\", \"1\", \"2\"]"
assert_raises "./exitswhenopeningnon-existentfile.swift" 1
assert "cat onetwothree.txt | ./print_linenumbers.swift" "line 1: one\nline 2: two\nline 3: three"
assert "./stream_out.swift" " 3"
assert "./callswiftscriptfromswift.swift" "line 1: one\nline 2: two\nline 3: three"
assert "./readfilelinebyline.swift" "one\ntwo\nthree"
assert_raises "./readandwritefiles.swift" 0
# end of test suite
assert_end SwiftShell