PowerShell/pester.sh

#!/usr/bin/env bash

./bin/powershell --noprofile -c "Invoke-Pester test/powershell/$1 -OutputFile pester-tests.xml -OutputFormat NUnitXml -EnableExit"
failed_tests=$?

# XML files are not executable
chmod -x pester-tests.xml

# Exit with failure if number of failed tests exceeds threshold
[ ! $failed_tests -gt 11 ]
Add test failure threshold to pester.sh Set to 14 because of non-tty and random process failures. 2016-01-22 23:29:30 +01:00			`#!/usr/bin/env bash`

Use --noprofile for Pester tests 2016-02-01 22:10:39 +01:00			`./bin/powershell --noprofile -c "Invoke-Pester test/powershell/$1 -OutputFile pester-tests.xml -OutputFormat NUnitXml -EnableExit"`
Add test failure threshold to pester.sh Set to 14 because of non-tty and random process failures. 2016-01-22 23:29:30 +01:00			`failed_tests=$?`

Output Pester results in XML again And bump submodule. 2015-12-23 22:12:40 +01:00			`# XML files are not executable`
			`chmod -x pester-tests.xml`
Add test failure threshold to pester.sh Set to 14 because of non-tty and random process failures. 2016-01-22 23:29:30 +01:00
			`# Exit with failure if number of failed tests exceeds threshold`
Decrease failed test threshold to 11 The updated packages fix our Start/Stop process tests, which were failing intermittently due to the process name appearing incorrect. See dotnet/corefx#5421 for further details. 2016-02-01 19:49:25 +01:00			`[ ! $failed_tests -gt 11 ]`