# Integrating Development and Testing to Improve Software Quality at FINN.no

DevFeed: [Integrating Development and Testing to Improve Software Quality at FINN.no](<https://devfeed.tech/articles/qa-role-is-dead-but-development-and-testing-together-provides-quality-for-finn-no-31962.md>)

Original publisher: [Read original article](<https://tech.finn.no2012/05/07/qa-role-is-dead-but-development-and-testing-together-provides-quality-for-finn/>)

Author: vivek

Published: 2012-05-07T07:29:20Z

Content type: opinion

Language: en

Sources: [Finn.no](<https://devfeed.tech/sources/finn-no.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [Development](<https://devfeed.tech/topics/development.md>), [Cucumber](<https://devfeed.tech/topics/cucumber.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [code-testing](<https://devfeed.tech/tags/code-testing.md>), [development](<https://devfeed.tech/tags/development.md>), [qa](<https://devfeed.tech/tags/qa.md>), [quality-assurance](<https://devfeed.tech/tags/quality-assurance.md>), [regression](<https://devfeed.tech/tags/regression.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## AI overview

The article argues that testing should be integrated into the development process rather than treated as a separate quality assurance department. At FINN, teams without a dedicated QA role reportedly achieved the same quality as teams with QA by sharing responsibilities and using different task-management practices.

## Source excerpt

When a developer is finished with a development issue, it must be tested. People often think the goal of testing should be to find all the errors. Well, it's not entirely realistic. Actually, it's impossible! Despite the title of "quality insurance" testers can never really ensure level of quality, nor can they be expected to find all the errors. The real goal of testing should be to improve the software. As at the end of the day we want to minimize the cost of fixing critical bugs after a release, minimize cost of handling customer complaints and pushing a patch in the production. So it is import to understand that Quality Assurance is a process, not a department. Today there are basically two different components of QA role in FINN. One of which is "QA in a team" and the other one is of a "team without the QA". The QA role today is often a safety net for many developers and teams. The role involves manual testing in the sprint, regression testing and writing Cucumber tests. In addition this role has some administrative tasks such as being contact person for the Release Manager, participating in the release status meeting, filling out the checklist of early / late shift, contact for Tech Support (E-journal issues), participating in status meetings at Call Center after release, and verifying the patch to production. Everything that's listed so far is managed also by teams without QA. What we have seen so far, is that a team without QA delivers the same quality as the team with QA in developing an FINN application. Then comes the question, how do they manage to do it? They have the same responsibilities as the "QA in a team", but they have different practices on how they manage the tasks (some have rolling QA role, others have a fixed arrangement but they are NOT dependent on one individual person). If we want to deliver a good quality code, testing must become a central pillar of the development process. When I say the role of QA is dead, but development and testing