Databases
StackOverflow2013
Postsdbo
POGeneric test deployment items generated during build?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGeneric test deployment items generated during build?
    primarykey
    data
    text
    <p>How can I specify a generic test's deployment items to be files that are generated by the build process? My current understanding of the default build process template is that automated tests (edit build definition -> process -> basic -> automated tests) will run after the specified solution (I specify only one .sln file in edit build definition -> required -> items to build -> projects to build) is successfully built, but the executable wrapped by my generic test is a file written during the same TFS build.</p> <p>Additionally:</p> <ol> <li>The user triggering the new build does not have access or ability to edit the build definition</li> <li>When creating or editing a generic test, users do not directly edit the XML and do not have permissions to specify deployment items located in the build folders of the build agent (using the file picker for deployment items in the generic test GUI)</li> <li>I cannot use <code>DeploymentItem</code> attribute because this isn't managed code (please correct me if I am wrong about this)</li> </ol> <p>I tried specifying a public (or otherwise user-accessible) drop directory (edit build definition -> build defaults -> copy build output to the following drop folder), and then specifying the generic test's deployment items from the drop directory, but I believe this does not help because the generic test is run prior to the build output being copied to the drop folder, and I also need the generic test to <em>not</em> run using an outdated copy of the wrapped executable previously existing in the drop folder from the output of a previous successful build, in the event that errors prevent a successful new build of the executable to be wrapped for the generic test.</p> <p>Can this be accomplished through the use of environment variables or other variables available somewhere in the build definition or generic test definition?</p> <p><sub> (Copied and adapted from <a href="http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/01d2598f-6f68-4afc-8a9a-4b7358af86fe" rel="nofollow">my post on MSDN</a>) </sub></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStaz
    1. UStaz
    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. This table or related slice is empty.
    1. VO
      singulars
      1. POGeneric test deployment items generated during build?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you need to configure this once, or do you need users to be able to specify custom deployment items for any build? What about using *.testsettings file with `Enable deployment` checked for running tests? You can select any file in this deployment, including files from mylib\bin\debug which are generated during build - why is it not work for you? Also, if you are using mstest, you can use DeploymentItem attribute for each test - will it work for you?
      singulars
      1. POGeneric test deployment items generated during build?
      1. USLanorkin
    2. COI need users with TFS commit permissions to be able to specify custom deployment items for any _generic test_ (which is done through the VS GUI or .generictest xml file). The generic tests are stored in the TFS repository as part of the team project. I am unclear what you are suggesting regarding `enable deployment` (I might be mistaken about what that option is for). `DeploymentItem` attribute is not an option for this task.
      singulars
      1. POGeneric test deployment items generated during build?
      1. UStaz
 

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