Have Geek Brain

Final integration testing for QA

The medium-sized rails that our company works with are nearing the end of development and we are going to start doing QA testing on it. We've been writing unit, functional and integration tests all along, and our test coverage is around 99% (although that doesn't mean anything).

We feel like we have a pretty good test suite, but I was wondering if we should write final integration tests for every little action we are going to do during our QA process. If so, can Shoulda or Cucumber be used? We haven't used any of these testing tools yet, but they sound pretty cool. Any ideas or thoughts would be really helpful.

thanks

+2


a source to share


1 answer


If your integration test suite sounds good (meaning it satisfactorily tests the functionality of all interfaces, i.e. how well all modules and classes integrate), then your next step is functional or acceptance testing.



For functional and acceptance tests, there should be a list of requirements. The functional testing that you perform must prove that the software meets these requirements. Acceptance testing is usually done by someone else ("customer" or "quality assurance").

+1


a source






More articles:


All Articles