Organising 'Sample Test Files' in Visual Studio and SVN -
my question test files mean non-code files on of automated tests depend (*.xml, *.xls, *.jpg etc). i'll use sample test files not confused test files meaning code files containing tests.
most of automated tests issolated unit tests have integration tests in single project (myapp.tests.integration) verify behaviour of classes interact external dependencies.
my collection of sample test files contained in project in solution called myapp.tests.testfiles. each file has build action of 'content' , copy if newer' set in it's properties.

when run tests solution built , files copied output directory "bin\debug" , integration tests refer them there.
the problem triggered question i'd been committing sample test files svn repository, hosted online limited amount of storage, alongside code. files occupying excessive amount of space in repository. i've since reconstructed repository , reduced sample test files minimum size.
in cases sample test files unlikely change while want them available check out repository working copy, there's no real reason have them under version control long can reconstruct myapp.tests.testfiles\testfiles directory structure run tests against.
that's scenario, i'm hoping answers following points:
- is there better way work these files?
- would better keep these files somewhere outside of solution?
- can keep required files in svn repository not under version control?
- would learning more msbuild helpful me?
i doubt there agreement on "best" way organize things. know in scm system typically have single folder contains folder deployable code , test code. let's i'm building widget , have dll called mylibrary. folder widget have folder called mylibrary , 1 called mylibrary_test. in vs same thing , keep test project in same solution deployable project. work alone larger teams may find other organizing styles more suitable.
i treat test code deployable source code. in source code management system. svn keeps difference files keeping versioned copies of test files not expensive. svn tries keep deltas on binaries doesn't work out 1 mighthope. don't believe svn designed keep single latest copy of source file. "delta" approach wouldn't work well. first time accidentally make change test file you're going wish go , grab lat working version.
Comments
Post a Comment