Databases
StackOverflow2013
Postsdbo
POMsTest in TeamCity: tests found for one build configuration but not another
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMsTest in TeamCity: tests found for one build configuration but not another
    primarykey
    data
    text
    <p>I have a TeamCity project set up with two build configurations. One runs every three minutes, in a continuous manner. The other runs every hour, on the hour. These used to be one configuration, until I split out the continuous build. Both configurations have two build steps: the first to build the solution and the second to run unit tests with MsTest.</p> <p>Before the split into two configurations, the MsTest build step ran all tests with the attribute [Category("Unit")]. The "additional command line parameters" value in the MsTest build step was "/category:unit". I created a new test attribute category -- "Integration" -- in order to split two types of tests between the two configurations. The hourly build configuration is intended to use the "additional command line parameters" value of "/category:integration".</p> <p>Unfortunately, the hourly build configuration does not find any tests to run. It doesn't matter whether the command line parameters include "unit", "integration", or both ("unit|integration"). On the other hand, the continuous build finds and runs the tests corresponding to the category(ies) included in the command line parameters. The hourly build log includes the following output:</p> <pre><code>[14:48:07]Step 2/2: Test Solution Hourly (MSTest) (29s) [14:48:07][Step 2/2] Starting: C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe #TeamCityImplicit [14:48:07][Step 2/2] in directory: D:\TeamCity\buildAgent\work\23f125e3a59e551a [14:48:11][Step 2/2] No assemblies, run configuration and test metadata were found </code></pre> <p>The two build configurations are identical in every way except build triggering. They use the default checkout and work directories, and the same build configuration parameter. The same work directory is created for both. There are no dependencies between them. They run on the same agent.</p> <p>My question is: Why is the hourly configuration not finding the tests?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USarcain
    1. UScbohling61
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMsTest in TeamCity: tests found for one build configuration but not another
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMsTest in TeamCity: tests found for one build configuration but not another
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload