On 3/4/14, 12:31 AM, "Silvio Moioli" <smoi...@suse.de> wrote:
>> From: Paul Robert Marino <prmari...@gmail.com >><mailto:prmari...@gmail.com>> >> I think we need a map of what these shared file and functions effect so >> we can do more formal QA testing in the future > >On 03/03/2014 08:09 PM, Lamont Peterson wrote: >> Agreed. > >Unfortunately I think such a "map", if ever existed, would be far too >complex to be of any practical value. Consider this image, which "maps" >only database tables, a relatively small fraction of the total software >complexity: > >http://turing.suse.de/~smoioli/relationships.real.compact.png > >Developers already have tools in modern IDEs such as Eclipse to check >for (partial) call trees[1], and are expected to use them. I do not >think we can do much more than that in this regard, of course new >opinions are welcome :-) > >Cheers, > >[1] http://eclipse-tools.sourceforge.net/call-hierarchy/usage.html >-- >Silvio Moioli >SUSE LINUX Products GmbH >Maxfeldstraße 5, 90409 Nürnberg Germany > >_______________________________________________ >Spacewalk-devel mailing list >Spacewalk-devel@redhat.com >https://www.redhat.com/mailman/listinfo/spacewalk-devel > You’re right (and thanks for the vivid DB relationships diagram). In my mind, the auto-generated map should simply be a calling-me list: Function A is called by: file.java : 45 file2.java : 134 That’s for developers. The map for QA could be simpler and generated from merely stuff one can hit “submit” on? -- Lamont Peterson Sr. Systems Administrator | Unix Systems Operations Intermountain Healthcare Office: 801.442.6497 | lamont.peter...@imail.org _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
