NQUnit looks sweet, should be able to get CI going without too much hassle. Resharper has a few problems refreshing the list of tests, got to sort that out (not using Resharper QUnit integration).
My previous employer didn’t pay me my entire salary for last pay. I think they ignored annual leave. Will have to chase this up. Damn corporations!
Got NUnit running on the build server (http://danderson00.blogspot.com/2011/10/running-nunit-tests-under-tfs-build.html). Also got QUnit tests working, soon to be blogged. Some notes:
- Disable IE ESC on build server
- Run IE as the build service account, turn off protected mode for intranet sites and allow active content to be executed from my computer
- Configure DCOM for build service user (http://salvoz.com/blog/2010/05/19/watin-and-team-build-2010/)
- Use NuGet to get NQUnit.NUnit package – dependencies install automatically.
- Set Interop.SHDocVw to not embed interop types (http://robdmoore.id.au/blog/2011/03/13/nqunit-javascript-testing-within-net-ci/)
- Disable ReSharper QUnit support (not required when NQUnit installed)
Now trying to get my Windows Phone 7 tasks app building on the build server. Some missing SDKs, potential NuGet issues. A pre-build step in each project with NuGet references is a potential solution, just to call NuGet, pointing it at the packages.config file (http://www.pandincus.com/blog/combining-nuget-with-team-foundation-build).
Some stuffing around to get the Windows Phone SDK to install on Windows Server 2008 R2 - http://blogs.msdn.com/b/astebner/archive/2010/05/02/10005980.aspx.
Thinking about some interesting consequences of rendering a view from a model using knockout. Pretty tightly couples your view to your model. Definitely affecting how batter totals and over totals will be set up. Humm…
No comments:
Post a Comment