PageSourceSearch

https://johnnyreilly.com/assets/js/42c034ef.9f18b6b8.js

js johnnyreilly.com collected 2026-09-24 19:31:55 UTC 3,918 bytes, 1 lines download raw bytes

1"use strict";(self.webpackChunkjohnnyreilly_com=self.webpackChunkjohnnyreilly_com||[]).push([["23673"],{37631(t,e,n){n.r(e),n.d(e,{assets:()=>u,contentTitle:()=>r,default:()=>p,frontMatter:()=>s,metadata:()=>a,toc:()=>l});var a=n(95869),o=n(74848),i=n(28453);let s={slug:"team-foundation-server-continuous-integration-and-javascript-unit-tests-in-unit-test-project",title:"Team Foundation Server, Continuous Integration and separate projects for JavaScript unit tests",authors:"johnnyreilly",date:new Date("2014-05-15T00:00:00.000Z"),tags:["automated testing","visual studio"],hide_table_of_contents:!1,description:"Learn how to run JavaScript tests on TFS/VSO by creating a separate unit test project to house tests, and installing Chutzpah on TFS/VSO.",atUri:"at://did:plc:yy3apqjlms24kso7ahn7lbmb/site.standard.document/3mr5bszefy32w"},r,u={authorsImageUrls:[void 0]},l=[];function c(t){let e={p:"p",...(0,i.R)(),...t.components};return(0,o.jsx)(e.p,{children:"Do you like to separate out your unit tests from the project you are testing? I imagine so. My own practice when creating a new project in Visual Studio is to create a separate unit test project alongside whose responsibility is to house unit tests for that new project."})}function p(t={}){let{wrapper:e}={...(0,i.R)(),...t.components};return e?(0,o.jsx)(e,{...t,children:(0,o.jsx)(c,{...t})}):c(t)}},28453(t,e,n){n.d(e,{R:()=>s,x:()=>r});var a=n(96540);let o={},i=a.createContext(o);function s(t){let e=a.useContext(i);return a.useMemo(function(){return"function"==typeof t?t(e):{...e,...t}},[e,t])}function r(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(o):t.components||o:s(t.components),a.createElement(i.Provider,{value:e},t.children)}},95869(t){t.exports=JSON.parse('{"permalink":"/team-foundation-server-continuous-integration-and-javascript-unit-tests-in-unit-test-project","editUrl":"https://github.com/johnnyreilly/blog.johnnyreilly.com/edit/main/blog-website/blog/2014-05-15-team-foundation-server-continuous-integration-and-javascript-unit-tests-in-unit-test-project/index.md","source":"@site/blog/2014-05-15-team-foundation-server-continuous-integration-and-javascript-unit-tests-in-unit-test-project/index.md","title":"Team Foundation Server, Continuous Integration and separate projects for JavaScript unit tests","description":"Learn how to run JavaScript tests on TFS/VSO by creating a separate unit test project to house tests, and installing Chutzpah on TFS/VSO.","date":"2014-05-15T00:00:00.000Z","tags":[{"inline":false,"label":"Automated Testing","permalink":"/tags/automated-testing","description":"How to perform the automation of tests."},{"inline":false,"label":"Visual Studio","permalink":"/tags/visual-studio","de
1scription":"The Visual Studio IDE."}],"readingTime":2.85,"hasTruncateMarker":true,"authors":[{"name":"John Reilly","title":"OSS Engineer - TypeScript, Azure, React, Node.js, .NET","url":"https://johnnyreilly.com/about","imageURL":"https://johnnyreilly.com/img/profile-2025.jpg","key":"johnnyreilly","page":null}],"frontMatter":{"slug":"team-foundation-server-continuous-integration-and-javascript-unit-tests-in-unit-test-project","title":"Team Foundation Server, Continuous Integration and separate projects for JavaScript unit tests","authors":"johnnyreilly","date":"2014-05-15T00:00:00.000Z","tags":["automated testing","visual studio"],"hide_table_of_contents":false,"description":"Learn how to run JavaScript tests on TFS/VSO by creating a separate unit test project to house tests, and installing Chutzpah on TFS/VSO.","atUri":"at://did:plc:yy3apqjlms24kso7ahn7lbmb/site.standard.document/3mr5bszefy32w"},"unlisted":false,"prevItem":{"title":"Migrating from AngularJS to AngularTS - a walkthrough","permalink":"/migrating-from-angularjs-to-angularts"},"nextItem":{"title":"TypeScript, JSDoc and Intellisense","permalink":"/typescript-jsdoc-and-intellisense"}}')}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.