This depends on how the integration works. When I have done this in the past, one team was responsible for creating data in a specific format that other services could comsume. The other team was responsible for testing that their product could consume data in that particular format. We also found that it can be useful to have a task on the work queue for a person to spend some time testing how different products integrate.
End to End testing in Agile projects
I am interested in hearing your thoughts on how End to End testing across multiple applications could/should be managed across agile teams, where the teams are responsible for an application/system with integration with another application/system.
I'd be interested in knowing how other companies handle this from a strategic and project level. Thanks
As per me, it is a very critical topic for large agile programs that are executed. In fact if there are clear stories on interfaces and integrations, it can be kept in scope of a sprint and tested. Few more thougths from practical implementations
1. Add tasks in the beginning of the sprint keeping in view the interfaces that are available and can be tested.
2. I have actually added a parallel team that works on the items that slip or constrined to be part of sprint. This parallel team does the interface testing, non-functional, e2e scenarios etc. This parallel team had stories that need to be tested and validated before each program increment. Basically sprint teams work in sprint and these parallel teams works outside the sprint but with in program increment.
FYI - Prg inc. is nothing but set of 4 sprints together that delivers a meaningful module at the end of it.
Hope this helps if not ignore :-)