Page History

...

• Projects of the tests are organized in the same way as projects of the sources (in most cases), see above listing.
• Tests should never write their output data into test-data/ directory. That directory is used for input data files used the tests. Instead they should copy required data into the test output directory (usually bin/Debug or bin/Release, it is very easy to do using FileUtils.Copy() method).
• Wiki MarkupMake sure that output files from the previous test run are deleted somethere in test \ [DS10:SetUp\].

Where can I find data files which can be used in data access or integration tests?

...

Why?
To make it easy to find the tests for a class.

Unit test categories.

...

Make sure that you put \ [DS10:Category(TestCategory.<name of the category>)\] attribute above your test if it is not a unit test. This is *very important* since it makes sure that all unit tests run very fast (3000 tests in <1 min).

Currently we use the following categories:

...

Info

Occasionally failing tests Usually it is trivial to determine which check-in caused a failing test. But sometimes the test fails on a (seemingly) unrelated check-in. In those cases it may be an unstable test: one that fails only occasionally, for example due to: a specific build server the order in which tests are run the culture (dot versus comma) threading race conditions locked files path inconsistencies DragDrop registration failed (see below) etc.. Unstable tests are usually a pain to debug, especially if it can't be reproduced locally. If it only fails on the build server, some time must be invested to add debug logging, or check if the build server has visual studio 2010 to debug (with remote desktop).

...

The how-to for tortoise is described

Clickable
Wiki Markup
{clickable:	http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-howto-rollback.html	http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-howto-rollback.html	here }{color:#0000ff}here{color}{clickable}

.

Section

Column To summarize: Go to your (clean, up-to-date) Delta-Shell check-out folder / Solution in Visual Studio Right click, navigate to SVN Show Log Select the revision(s) you want to undo. Right click to open the context menu (see image) Choose 'Revert changes from this revision' The changes have now been undone in your local files. Commit the changes! Contact the person responsible with details about revision numbers. The changes of the person responsible are not lost: they are available in the repository as previous revision. Column

Fix Drag&Drop problem

...