|
Content with label test in TeamCity 4.x Documentation (See content from all spaces)
Related Labels:
framework, coverage, net, xml, ant, details, rake, label, recently, nant, dotnet, reordering, trigger, graph, artifact, type, nunit, number, project,
rakefile, addin, committer, build, admin, runner, reports, statistics, setting, custom, result, status, parallel, risk, recent, vcs, agent, search, message, testng, service, junit, chart, comment, failure, msbuild, code, history, mstest, script, report, ui, change, failed, launcher, import, reference, ruby, queue
more »
Page:
Ant_
page is under construction. Basic information on setting up the Ant Build Runner can be found in the Ant section of the UI Reference. This section contains additional information related to the Ant Build Runner. Support for Running Parallel Tests By using the {{<parallel ...
Other labels:
parallel, ant, script
|
Page:
Build Script Interaction with TeamCity
TeamCity doesn't support your testing framework or build runner out of the box, it is still possible to reap the many of benefits that TeamCity provides by customizing your build scripts to interact with the TeamCity server. This makes a wide range of features available to any ...
Other labels:
build, script, report, custom, chart, graph, status, number
|
Page:
Code Coverage
NET coverage support see .NET Testing Frameworks Support Code coverage is a number of metrics that measure how your code is covered by unit tests. Code coverage information displays for those build configurations, where this metric is configured in the Code ...
Other labels:
code, coverage, build, runner
|
Page:
MSTest Support
NET runners TeamCity provides support for MSTest 2008 testing framework via parsing of the MSTest 2008 results file (.trx file). Due to specifics of MSTest 2008 test runner, TeamCity does not support onthefly test reporting for MSTest ...
Other labels:
mstest, dotnet, net
|
Page:
NUnit Support
multiple ways to run tests with NUnit to support TeamCity's test reporting ability: for NAnt build: use standard {{<nunit2>}} task in NAnt build (it is automatically replaced NUnit for NAnt build runner with TeamCitycapable task); for MSBuild build: use standard ...
Other labels:
nunit, framework, launcher, nant, msbuild, addin
|
Page:
Problematic Tests
tab shows a list of all build configuration tests which have failed at least once within the last 120 hours and provides the information on: Test name Total runs of the test Failure rate in percent Last failure time !problematicTestsTab.png ...
Other labels:
failed, failure, recent, recently
|
Page:
Rake
Since TeamCity 4.0, the Ruby Rake support is bundled in TeamCity. For detailed information, please refer to the Rake Runner plugin documentation TW:Rake Runner. This page contains reference information about the Rake build runner fields Option Description ...
Other labels:
ruby, rake, build, runner, xml, reports, rakefile
|
Page:
Running Risk Group Tests First
section covers: Reordering Risk Tests for JUnit and TestNG Supported environments: Ant and IPR runners JUnit and TestNG frameworks when tests are started with usual JUnit or TestNG tasks TeamCity also allows to implement tests reordering feature for a custom ...
Other labels:
reordering, build, runner, risk
|
Page:
Statistics
Build Configuration > Statistics tab The charts in this tab demonstrate important project statistics including: successful build rate, wait time in build queue, build duration, artifact size, and test count. The charts show code coverage, duplicates and inspection ...
Other labels:
statistics, build, result, artifact, queue, ui, chart, type
|
Page:
Test Details Page
project home page> > Problematic Tests tab > !testDetailsIcon.gif! next to <test name> <build configuration home page> > Problematic Tests tab > !testDetailsIcon.gif! next to <test name> <build results home page> > Tests tab > !testDetailsIcon.gif! next to <test ...
Other labels:
details
|
|
|