I'm using vs\tfs 2010 to queue builds with tests. When using vs to queue the build, I can access the "View Test Results" in the build summary. But when I queue the build using the TFS web access, this link is missing from the build summary.
My guess is that opening test results requires Visual Studio or Test Manager. Even so, I wouldn't see the harm in allowing you to download the file(s). As a cheap work around you could click "View Log" and scroll down towards the bottom to see the test results.
Additionally, you could create a custom build control to display a hyperlink to the build results:
http://www.ewaldhofman.nl/post/2010/05/27/Customize-Team-Build-2010-e28093-Part-8-Send-information-to-the-build-log.aspx
http://www.ewaldhofman.nl/post/2010/10/02/Customize-Team-Build-2010-e28093-Part-13-Get-control-over-the-Build-Output.aspx
Related
I know I can set up continuous integration - and that makes builds happen seamlessly. However this isn't appropriate for all our projects.
So for those, I can right-click the build and select queue new build and wait for the popup and queue it.
However, I never have to change those options. And this is about more than saving a click. More than once I've right-clicked and selected Queue build, left my desk before it appears (sometimes it takes 5-8 sec), meaning to meet with a co-worker or take lunch break prior to a large build.
Then I return to my desk and unlock my PC only to be greeted by the 'queue build' popup. Then I have to wait for it to build.
Usually I remember ... but the times I get burned are bitter indeed!
It's not able to suppress the options pop up when you queue the build either in visual-studio or web. For vNext build, it will also open a web portal.
As a workaround, you could try to use TFS API or Rest API to trigger the build instead of manually through Visual Studio. Please follow below tutorials:
For vNext Build:
How to trigger a build in TFS 2015 using REST API
For XAML Build: TFS API Queue a New Build with Custom Parameters
Besides you could also add a use voice here , TFS PM and Admin will kindly review your suggestion.
We're using MSTest with Team Services (was Visual Studio Online) builds to run our Selenium Tests and, for the failed ones, I'm taking a screenshot in the TestCleanup that added to the Test Results by using TestContext.
Now, when I'm checking the test results for the failed tests, and want to open the attachment (a .png image), Team Services is always prompting for download instead of just displaying it in the browser, which could really become a pain when you have a new build of your app and a lot stuff was changed causing multiple tests to fail.
Is there any possibility to force Team Services or the browser to open the images in the browser?
I'm open to anything from changing the type of attachment, potential "hacks" that could determine Team Services to display the image in browser, browser extensions, etc.
There isn't any option to configure this at VSTS/VSO side for now, I have help you submit a feature request on VSTS User Voice, refer to this link for details: Open attachments of test result from web portal in browser.
However, if you are using Firefox, I know there is an Open in Browser add-on which allow you to open the document from browser directly.
I have the following problem where Associated Automation not showing tests.
The project has been checked in and the Unit Tests show up fine on Test Explorer
When I query and search for a Test Case in TFS then attempt to link a Unit Test to the Test case via the associate button, nothing appears in the Choose Test window.
Any help please?
We have TFS2012 and if i check into a branch with CI enabled a gated dialog will appear asking to build (when using both vs2012 and vs2013).
However unlike in vs2012, vs2013 doesn't seem to get a callback to tell it if the checkin was successful.
The Team explorer checkin still shows the details of the checkin (description, associated TFS items) and no dialog pops up to show it was successful like in 2012. Am I missing a configuration step?
I suggest you to configure this in your Web Portal of project, you access Alerts Section and adjust this by creating New Alert based on your check in.
Check your Administration Console TFS if it's not resolved, in order to configure your notification server.
I have a Visual Studio 2008 solution that contains around 30 projects. Some of these are web services / WCF services / ASP.NET MVC applications.
When I run all unit tests (Ctr+R, A) it insists on spinning up all the Development Servers for these various projects. This means that it takes far too long to run the tests and, actually, none of my unit tests require these frameworks.
So, how do I stop Visual Studio doing this?
Click on the projects in your solution and bring up the properties window (F4).
Change Always start when debugging to false.
If you're running the tests, not debugging, then the "Always start when debugging" setting will have no effect.
Instead, have a look at the test settings that you're using to run the tests. (Find which settings you're using by going Test > Select Active Test Settings. You can then edit the test settings by going Test > Edit Test Settings and selecting your active test settings)
I have found the following test settings can force the ASP.NET development server to start up, although there could be more!
Non-default test host: In the edit test settings window, choose the "Hosts" section. Host type should be set to "Default", not "ASP.NET"
Code Coverage: In the edit test settings window, choose the "Data and Diagnostics" section. Select "Code Coverage" and click "Configure". The development server will start for each service that is selected here for ASP.NET Code Coverage. (Normal code coverage is identified by an icon of a blank page with two gears on top of it. ASP.NET code coverage is identified by an icon of a globe with two pages on top of it.) To change from ASP.NET code coverage to normal code coverage, deselect the ASP.NET code coverage, then choose "Add Assembly...". Browse to the bin folder of your web service project and choose the dll of the web service.