On 12.6.2014 17:21, Kervinen, Antti wrote:
When a developer changes code, tests may notice that something broke up. Those tests may have be written for the modified component, or for some other component that took a hit from the change.
As middleware developer, I think the most important part of these test frameworks and automated image testing is specifically to notice any breakage to other software components. Unit tests only tell if the component functions as itself, but it doesn't tell if there's widespread breakage for the application using the middleware component.
Using gSSO and syncEvolution as example, the most useful output would be to immediately get feedback if one of my changes to gSSO broke syncEvolution. This has significant reduction to time and effort needed to fix such cases.
This becomes more and more important when number of components depending on middleware X increase. For example if glib is updated to most recent version, it would be very nice to see before wide integration cycle if there is any breakage when only _that_ particular component change went in. Figuring out cause of the breakage from image where number of changes have already been integrated is much harder.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
