integration-testing

I am trying to create a comprehensive integration test suite for a RESTful (Services) Java-based application that runs in Tomcat(7.x) and depends on an Postgresql (9.x) instance. Further, I would like to be able to run this suite as a self-contained process, exclusively from maven 3.x, if possible, by using the maven failsafe plugin. That way, the tests can be run across the 3 major platforms (Mac OSX, Linux & Windows). From what I have learned, I believe that the key to making this happen is doing something like these steps (in this order): Start an "embedded" version of the postgresql DB

People at my company see unit testing as a lot of extra work, that offers fewer benefits than existing functional tests. Are unit and integration tests worth it? Note a large existing codebase that wasn't designed with testing in mind. (I'm assuming that you're using "functional test" to mean a test involving the whole system or application being up and running.) I would unit test new functionality as I wrote it, for three reasons: It helps me get to working code quicker. The turnaround time for "unit test failed, fix code, unit test passed" is generally a lot shorter than "functional test

So I've found bits and pieces that have enlightened me some on the [Authorize] tag, but nothing that solves my problem. My scenario is that I have Web Api methods that I want to hit with integration tests using RestSharp. However RestSharp is getting my login page, instead of the results of the call. [Authorize] public Item GetItem([FromBody] int id) { return service.GetItem(id); } The product uses a custom login system, and what I would REALLY like would be a way to disable the [Authorize] badge only for integration tests. However I read that you can allow anonymous users and it would

I need some advice about efficient way of writing integration tests for our current ASP.NET MVC application. Our architecture consists of: A Service Layer below Controllers Service Layer uses Repositories and Message Queue (sometimes) to send messages to external applications. What I think should be done is to: Write behavioral unit tests for all pieces in isolation. So, for example, we should unit test the Service Layer while mocking Repositories and Message Queues. Same goes for Controllers. So we mock the Service Layer and unit test the Controller. Finally, we write separate integration

I have a Rails 3 integration test which tests my routes. It contains tests such as: assert_routing( "/#{@category.url.path}/#{@foo.url.path}", { :controller => 'foo', :action => 'show', :category => @category.to_param, :foo => @foo.to_param } ) I would also like to test a case where no routes should match. Obviously, testing generation has no meaning in this case, so I just need the inverse of assert_recognizes. I'd like to be able to do something like this: assert_not_recognized('/adfhkljkdhasjklhjkldfahsjkhdf') Any ideas, short of wrapping assert_recognizes in an assert_raises block (which