New answers tagged integration-tests
My company used anonymized data from production. If it's not too hard to filter out personally identifiable information then that's a great way to get realistic test data.
Mocks are acceptable in this case, but you don't need it. Instead of unit testing method(), instead unit test just the portion that handles the response. Extract a function that takes ResponseData (of whatever kind is appropriate) and then performs the action. Instead of mocking, now you just construct a ResponseData object and pass it in. You can leave ...
What I've done, and it works: Have all code call webservices through proxy. The proxy calls a class that statically knows if we are using proxy or not and redirects accordingly. Mocks are just HashMaps that for each request returns a given reply. Run the tests several times in this order: 3.1 First all webservices are tested. From each machine, even ...
Yes you should always test the system with all real-world architecture if you can, some problem may be only occurred in real system/data tests (out of memory/locked connection/environment stableness). If the business logic and data communication is proven to be working great, the next thing you should focus on will be stress test for the service: Regards to ...
Top 50 recent answers are included