Tag Info

If you are talking about unit tests I would consider moving the long running tests to a different test suite. If they are taking a long time they probably aren't unit tests and should not be treated as such. These tests should be moved to the location where you run integration tests. If that's not what your looking for you could also look into running ...

Similar question posted on Software Testing Club Robotium looks like it help fulfill some of your needs? (props to Stephen Janaway)

It depends on the test framework you are using. The frameworks I know allow you to define your own assertions. With that, you could define a time based assertion like assertSpecifiedBefore(<specification>, <date>), which checks the last modification date of the specification is not newer than the date of test creation (<date>).

You might start with Jenkins. It is free, open source, and popular, and it has a lot of extension points. You can use it to launch arbitrary shell or script files. A moment ago, I Googled for "Jenkins .NET" and found several articles about using Jenkins to install/run .NET applications.

I am running Watir scripts from Jenkins CI on a couple of projects. I do plan to write about it at my blog soon. If you have specific questions, please ask. I have recently recorded a screencast about the entire test automation solution I have developed for a client: Test automation at HomeSwap.com

A quick Google shows plenty of people doing this, including This page from WatirMelon ( if you dont know of this site could be worth your while reading it, lots of good stuff on it ) and an example of using ci_reporter is here

You can try Railsonfire (Full disclosure I am one of the founders) We provide Continuous integration and Deployment for Ruby apps as a Cloud Service. Simple setup in < 2 minutes. If you need any help setting it up write me an email to flo@railsonfire.com, a tweet to @Railsonfire or use the olark chat box at the bottom of our site. If you do want to use ...

I think ci-infrastructure is what you are looking for. "Getting a fresh Jenkins server set up is kind of a pain and because of that, fewer projects have one than should. This project is designed to make it easy for people to fork and get set up with their very-own Jenkins server in the cloud because CI is awesome. "

I recently looked for the same thing and after not finding anything wrote my own implementation. I took the approach outlined in this blog: http://www.testingwithkunal.com/automated-deployment-validation-using-net/ and from there I added the ability to test for some additional things outlined in my response to this question: Deployment Testing

No, there are no general purpose open source tools that could perform validation for you. Yes, there are a lot of small tools that could enable you to automate that validation. The main question is what you need to validate. Do you have manual check list already? Using any popular scripting languages: Perl, Python, Ruby, Jscript you could automate the ...

The book How Google Tests Software (chapter 2, "Test Execution" section) describes how Google categorizes tests by size: small, medium, large, or enormous. The size takes into account not only how long the test takes but also the extent of its dependencies. For example, small tests should run into under 100ms and use extensive mocking to minimize ...

This is one reason why it is important to know how long each test takes, and to refactor if necessary. A lot of times folks will just continue to pile on functionality into a test, use unnecessary sleeps throughout their code instead of events or polling loops, or just add new (sometimes redundant tests) to an already over-bloated automated test suite. In ...