Skip to main content
18 events
when toggle format what by license comment
Feb 18 at 20:49 answer added jmoreno timeline score: 2
May 9, 2012 at 2:39 comment added Ricky Clarkson @user606723 That just means the tests are likely to get out of date and become useless. Better to compile them but not into the build artifact.
May 8, 2012 at 22:06 history edited Kyralessa
edited tags
Jan 11, 2012 at 9:44 answer added seanfitzg timeline score: 3
Jan 6, 2012 at 18:23 comment added Steven Evers Once/If you start using CI, where is the CI server going to get the tests from?
Jan 6, 2012 at 17:47 history edited parisminton
Added unit-testing tag; didn't know there was one before
Jan 5, 2012 at 23:47 answer added anon timeline score: 5
Jan 5, 2012 at 19:14 vote accept parisminton
Jan 5, 2012 at 15:31 comment added user606723 Note, that I would consider it a good idea to disable test class compilation in your build script.
Jan 5, 2012 at 11:27 history tweeted twitter.com/#!/StackProgrammer/status/154886708977086464
Jan 5, 2012 at 11:03 comment added MaR They are built separately, but otherwise u-tests are tightly coupled with code. To ensure consistency there must some kind of dependency management. Be it putting them into same repository, subrepository or maintaing version controlled "link" to test repository, etc.
Jan 5, 2012 at 10:39 comment added brabec The fact that some project don't include unit tests in their repository is more likely due to non-existence of these tests in the first place.
Jan 5, 2012 at 9:50 answer added Jan Hudec timeline score: 6
Jan 5, 2012 at 9:47 answer added BЈовић timeline score: 8
Jan 5, 2012 at 9:45 answer added user timeline score: 54
Jan 5, 2012 at 9:43 comment added user2567 Why not? Tests should come along with the project or they are barely useless.
Jan 5, 2012 at 9:42 answer added ftr timeline score: 123
Jan 5, 2012 at 9:25 history asked parisminton CC BY-SA 3.0