Question

I’m trying to create a build workflow for TFS that enables the following sequence of events (for now for a Web App, but in the future for Sharepoint projects to):

Build -> Test (Unit Tests) -> Deploy to IIS – Test (Coded UI) – Test (Load)

Up to the deploy I managed to configure the workflow, the problem start after. I’m having trouble the decide where to start. Is it better to create a new activity for each test using workflow components or go the powershell route?

One caveat, the virtualization infrastructure that exists is not MS so I cannot go the Lab Management route.

Thanks in advance for your insights

Answer 1

If you are in position to implement your test-invoking via Powershell, I think this would be your best way to proceed.
You would have to implement an “execute Powershell” part in your build script (see here) & maintain your *.ps1 in the source control.

For different/various projects you could construct a Build Argument that points to a user-inserted Path to the powershell-file that should execute in the given build definition.
This Path could even be from source control. In this case you would have to enter $/path/.../script.ps1 in the Proces of each Build Definition and have a ConvertWorkspaceItem execute before consuming it during Build.

Since you are not using MTM/Lab Management, I think this can be a nice/flexible alternative.