Activity overview
Latest activity by ssvoss
I don't love it. I'd rather use the PowerShell Commandlets but I ended up using MSBuild to build/deploy the database to the server (can't use in memory since I have a full text index). Then I point Invoke-DatabaseTests directly at the testing database which already has the tests deployed to it.
Exec { msbuild $SOLUTION /NoLogo /v:Minimal /t:Build /p:OutputPath=$outputDir
/p:Configuration=Release /p:DeploymentMode=DeployOnBuild
/p:ShadowServer=ServerName /p:ShadowUserName=$Uname /p:ShadowPassword=$Pass
/p:TargetServer=ServerName /p:TargetDatabase=TestingDatabase
/p:TargetUserName=$Uname /p:TargetPassword=$Pass} "Failed to build $_"
$testResultsFile = "$env:WORKSPACE\out\tSQLtResults.junit.xml"
$testResults = Invoke-DatabaseTests $testingDb
Export-DatabaseTestResults $testResults -OutputFile $testResultsFile
/ comments
I don't love it. I'd rather use the PowerShell Commandlets but I ended up using MSBuild to build/deploy the database to the server (can't use in memory since I have a full text index). Then I point...
Project Dependencies on Invoke-DatabaseTests
I have a solution for my database that includes one project for the DB objects I need in every environment (main project) and another project with all the testing objects (test project). As describ...