It's not a perfect solution but it does work, and means fully automated tests and deployments. In the future I'm going to look into TeamCity generating a useful test report which can then be automatically uploaded as an Octopus deployment artifact.Īny build specific stuff (such as changesets, etc) are done in TeamCity just before packaging, when TC will generate a PostDeploy.ps1 script that echos octopus variables I can access during the deployment. This means that the deployment is 'paused' while tests are executed.
#TEAMCITY OCTOPUS CODE#
This new TC build is responsible for running the test script (in my case it's selenium based functional testing), and returns a non-zero code if the tests fail. Octopus then deploys the website, and after deployment runs a powershell script that triggers another TeamCity build. TeamCity is responsible for taking the source code, running unit tests, packaging and sending build artifacts to Octopus. Smoke tests don't really sit within the scope of Octopus - however I've got this working in conjunction with TeamCity. Is that all that is missing to mark this feature as “done”, or is there more we would need to do? Viewing NUnit results XML isn’t that nice though, so I guess it would be nice to be able to render those NUnit test results in the browser, or to add ‘badges’ to a deployment (such as the number of tests passed). The next part is viewing the test results – in Octopus 2.0 you can “attach” files to a deployment via PowerShell which are then uploaded and available on the deployment page. Do we need to write more blog posts/documentation to show how it can be done? So the actual process of performing the tests is pretty easy. There are a few things in Octopus that already help with this – first, it’s possible to package your NUnit tests and run them as part of a package test (we do this ourselves), or to write a PowerShell step that pings your website to see if it is online. I’d like to get feedback on where we should go with this. Thanks for the suggestion and for voting everyone.
0 kommentar(er)
