--- title: The devil is in the details (Visual Studio Team System... description: A developer describes a limitation in Visual Studio Team System's check-in policy system: when a Team Project contains multiple solutions, the built-in unit... canonical: https://daily.dev/posts/the-devil-is-in-the-details-visual-studio-team-system-test-policy--9mi5ppngy twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The devil is in the details (Visual Studio Team System test policy) | daily.dev og:description: A developer describes a limitation in Visual Studio Team System's check-in policy system: when a Team Project contains multiple solutions, the built-in unit... og:url: https://daily.dev/posts/the-devil-is-in-the-details-visual-studio-team-system-test-policy--9mi5ppngy og:image: https://api.daily.dev/og/posts/9Mi5pPngy.png og:image:alt: The devil is in the details (Visual Studio Team System test policy) og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The devil is in the details (Visual Studio Team System test policy) **[Maarten Balliauw](https://daily.dev/sources/maartenballiauw)** · 1 min read · 0 upvotes · 0 comments ## Summary A developer describes a limitation in Visual Studio Team System's check-in policy system: when a Team Project contains multiple solutions, the built-in unit testing policy cannot be scoped to run only the tests relevant to the solution being changed. To work around this, a custom check-in policy was created, with the source code shared (Visual Studio 2008 only) along with links to existing guides on building and installing custom check-in policies. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I make Visual Studio Team System run only the unit tests for the solution that changed before check-in? The built-in unit testing check-in policy in Visual Studio Team System cannot scope test lists per solution within a single Team Project, so a custom check-in policy must be written to detect which solution changed and run only its relevant tests. A working solution for Visual Studio 2008 implementing this custom policy is available as downloadable source code. _Developers wrestling with multi-solution test policies can find related fixes and discussions on daily.dev._ ## Similar posts on daily.dev - [The Visual Studio Debugger Agentic Workflow Gets a Test-Driven Upgrade](https://daily.dev/posts/the-visual-studio-debugger-agentic-workflow-gets-a-test-driven-upgrade-wr8lcrvrh) · Visual Studio Blog · 1 upvotes · 0 comments - [Security Tests That Prove Themselves — Daily DevOps & .NET](https://daily.dev/posts/security-tests-that-prove-themselves-daily-devops-net-4mutnqllj) · We Are .NET · 1 upvotes · 0 comments - [How to Tame Your Flaky Tests in TeamCity](https://daily.dev/posts/how-to-tame-your-flaky-tests-in-teamcity-srhpeck9w) · JetBrains · 0 upvotes · 0 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#version-control](https://daily.dev/tags/version-control) [View this post on daily.dev](https://daily.dev/posts/the-devil-is-in-the-details-visual-studio-team-system-test-policy--9mi5ppngy) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The devil is in the details (Visual Studio Team System test policy)","url":"https://daily.dev/posts/the-devil-is-in-the-details-visual-studio-team-system-test-policy--9mi5ppngy","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-devil-is-in-the-details-visual-studio-team-system-test-policy--9mi5ppngy"},"datePublished":"2026-10-04T13:04:59.952Z","dateModified":"2026-10-04T13:18:11.860Z","description":"A developer describes a limitation in Visual Studio Team System's check-in policy system: when a Team Project contains multiple solutions, the built-in unit...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9241cfc8430fc41b6fedf56174dddde6?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9241cfc8430fc41b6fedf56174dddde6?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Maarten Balliauw","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Maarten Balliauw","logo":"https://media.daily.dev/image/upload/s--rOTg3VYO--/f_auto,q_auto/v1791119043/logos/maartenballiauw?_a=BAMAMicg0","url":"https://daily.dev/sources/maartenballiauw"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-devil-is-in-the-details-visual-studio-team-system-test-policy--9mi5ppngy","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,version-control","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Maarten Balliauw","item":"https://daily.dev/sources/maartenballiauw"},{"@type":"ListItem","position":3,"name":"The devil is in the details (Visual Studio Team System test policy)"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-devil-is-in-the-details-visual-studio-team-system-test-policy--9mi5ppngy#faq","mainEntity":[{"@type":"Question","name":"How can I make Visual Studio Team System run only the unit tests for the solution that changed before check-in?","acceptedAnswer":{"@type":"Answer","text":"The built-in unit testing check-in policy in Visual Studio Team System cannot scope test lists per solution within a single Team Project, so a custom check-in policy must be written to detect which solution changed and run only its relevant tests. A working solution for Visual Studio 2008 implementing this custom policy is available as downloadable source code. Developers wrestling with multi-solution test policies can find related fixes and discussions on daily.dev."}}]} ```