I had some questions around system/integration test. We have a development team and a full QA team, which does customer focused testing for our product. We want to introduce a middle test team which is more of an extension of the engineering orr, a system integration test team if you will.
Thinking about the rules for what the developers are expected to test, what this new team is expected to test, and the final QA customer team. The problem it is supposed to solve is the QA team gets code which is not really tested well, and falls apart right away, since developers are doing unit tests mostly, and QA is doing scale, customer focused scenarios. We are doing smoke to take care of the immediate fall apart, but want to do some more, take a bit of load off the devs, but not all the way.
The project is in python and its a bunch of different modules that interact with each other.
Developers today do only unit tests, class level, and some very very limited "system" level tests.
I was interested in finding out what other folks do for a mix like this. I want the developers to do more "System" level testing, something where they test their components end to end in the system perspective also, at some scale larger than one operation or two concurrent operations. But I am coming up against the question of what is expected out of this new team in that case. The only things I can think of are scale and a full all-components-together testing, but thats something the QA team will do in any case.