tfsbuild

Run Jest unit test with TFS 2015

≯℡__Kan透↙ 提交于 2019-12-06 01:30:03
问题 Has anyone attempted to integrate jest unit tests with TFS 2015? I tried to use Chutzpah Test Adapter (https://visualstudiogallery.msdn.microsoft.com/f8741f04-bae4-4900-81c7-7c9bfb9ed1fe?SRC=VSIDE) however it's not able to recognize jest. I receive below error: Can't find variable Jest When I run the unit tests through "npm test" I get the results. However to integrate with TFS 2015 I need a test runner which can run Jest unit test so that I can run the unit tests in conjunction with vstest

Restricting TFS check-in policy to specific users

梦想的初衷 提交于 2019-12-05 23:59:49
问题 The title says it all really. Our team wants to somehow restrict a TFS check-in policy to some select users. We are currently using something similar, but to restrict server paths. We have a Custom Path Policy policy attached to a Work Items policy in our project, and it is working as expected. I wondered if it would be reasonable to create another policy like that, that scopes a certain other policy to a group of predefined users. We would like to use a feature like that with this code

Check-ins to TFS2013 source control triggers CI build associated with separate TFS Git Repository

空扰寡人 提交于 2019-12-05 20:46:43
问题 I have a TFS 2013 server with several TFS team project collections and developers working happily against them. The project collections have a set of TFS builds associated, including relevant CI builds which trigger on each check-in, or in some cases, rolling (accumulated) check-ins. This process works flawlessly and has been the way of working for several years. Recently, we've introduced a Git repository into the mix which also sits on our TFS 2013 server and appears as a node that I can

TFS 2013 default template run powershell script and log output

浪子不回头ぞ 提交于 2019-12-05 20:20:38
问题 running a powershell script from within a build process has become really really straight forward with VS 2013. Unfortunately no write-host commands are being logged to the tfs build log. So after a build completed I cannot look into the log file and see what the powershell shell script actually did. The log file only says: Run optional script after MSBuild 00:03 Run optional script before Test Runner 00:00 Run VS Test Runner 00:00 Run optional script after Test Runner 00:00 ... The

Maven works in cmd but not powershell

无人久伴 提交于 2019-12-05 20:04:59
问题 I want to build with maven my java projects on TFS Build Server. TFS Build Definition use invokeprocess in workflow. invokeprocess able to run powershell script and command batch file. Maven build successed with " mvn assembly:assembly -P prod " command in windows command prompt. But does not success in powershell. (I connected to server with remote and executed on powershell ise) (either as a regular user or as an administrator) I installed Maven 3.1.1 and Java Dev Kit 6 update 45 on Windows

VSO/VSTS: Error when using Publish Build Artifacts on the host agent

牧云@^-^@ 提交于 2019-12-05 19:38:36
When using the Publish Build Artifacts task, the following error gets thrown in the build (just after "Get sources"): The definition for the task does not have a handler that matches any supported by this agent. Supported handlers: AzurePowerShell, AzurePowerShellHandler, PowerShell, PowerShellHandler, PowerShellExe, PowerShellExeHandler, Process, ProcessHandler I am using the VSTS (formally known as VSO) Host Agent. I can reproduce this issue too. Checked the source code for " Publish build artifacts ", this issue seems to be caused by the PowerShell script is missing. I have help you submit

Checkins to TFVC Team Projects trigger builds in Git Team Project

一个人想着一个人 提交于 2019-12-05 17:45:35
I have a TFS project set up for continuous integration. My problem is that checkins on other TFS projects are triggering builds of my project even when no change has been made to my project. It seems to be related to my project being a Team Foundation Git repository, and none of the other projects are. Where can I look to find out what's triggering this build? Edit: To be more clear, what I mean is that I have entirely separate Team Projects. All of them but one use Team Foundation Version Control except one which uses Git. Somehow, checkins on the TFVC Team Projects trigger a build on the Git

How to associate a Build to the test plan in Microsoft Test Manager (MTM) 2010?

烂漫一生 提交于 2019-12-05 17:19:04
I am new using Microsoft Test tools, please help: When trying to run a test case from MTM, I am receiving the following warning message: Cannot create automated test run. A build associated with the active test plan is required to submit an automated test run Background info: I have created a Build definition in VS 2010 I have created a Build service host with Agents:Controller and Agent When I open MTM>Testing Center>Properties Build Configurations I can see my build definition selected in "Filter for Builds:" Problem: In MTM>Testing Center>Properties Build Configurations > " Build in use:"

dotnet test not creating test results folder

核能气质少年 提交于 2019-12-05 16:57:50
问题 As part of our ASP.NET Core 2.0 build process I have added a dotnet test command which I have added as a Windows batch file. Here is my command. dotnet test "MyProject.csproj" --no-restore --results-directory "MyProject\TestResults" --verbosity minimal And here is the output when run from the command line. So it all appears to work correctly, yet no test results / test output is created. 回答1: To output the test results from dotnet test, you can try pass -xml /some/path/out.xml or use the work

How do I get rid of “API restriction UnitTestFramework.dll already loaded” error?

本小妞迷上赌 提交于 2019-12-05 13:09:22
问题 The following error pops up every now and then: C:\Program Files\MSBuild\Microsoft\VisualStudio\v9.0\TeamTest\Microsoft.TeamTest.targets(14,5): error : API restriction: The assembly 'file:///C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll' has already loaded from a different location. It cannot be loaded from a new location within the same appdomain. How do I get rid of it? 回答1: Edit the .csproj file Remove