Who is responsible for integration testing, developer or tester?

Who is responsible for integration testing, developer or tester?

Who is responsible for integration testing, the developer or the tester?

    Requires Free Membership to View

    Login

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

This answer will always depend on the project you're working on. Even in the same company, I've seen responsibility for integration test execution separated between the two project roles differently (sometimes it's the programmers who run those tests, other times it's the testers). It will often depend on who's managing the project, the development methodology being used, company culture, how consulting contracts are written (who's responsible for delivering what), and sometimes even what tools and technology are being used.

However, I think I can provide a better answer than "it depends." If I'm managing or working as part of the leadership team on a project, it's my expectation that both programmers and testers are responsible for integration testing. It's not an area of testing where I've found strict role separation useful (but that could just be due to the types of projects I've worked on). It's also been my experience that the closer the two roles work together when doing technology-facing testing, the better the testing results are.

The programmers will likely have a deeper grasp of the technical concerns of the integration. The testers will likely better understand the risks around quality criteria other than capability (does it do what we think it should be doing). They'll be thinking about performance, error handling and alerting, operational criteria, usability, and edge cases related to critical functions. It's one of the areas where I've found it easiest for the two roles to collaborate.

This was first published in February 2009

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top