Hi, Jimmy, I am Moblin QA engineer in SH. I am investigating the component "Content Manger" from QA perspective.
I reviewed your test design doc and log some questions here: 1) The Tracker is an open source project. Are we going to merge/integrate the latest version of “Tracker” into Moblin 2.0 in future? I found each of “tracker” components is going to be modified in the doc. And I am afraid the merge/integration will become very hard. 2) When multiple tags of content files will be added? How are the tags updated by user? 3) D-Bus searching interface will not be exposed to application developers, right? (P3, Sec4, Sub-Sec3) Furthermore, which part of interfaces will be exposed to application developers and which part will not? 4) Whether “the sample test app” (P3, Sec4, Sub-Sec4) is looked as the part of formal release? Namely, do developers expect QA test sample test app as product? 5) How about your unit test plan? Do you want to use any automatic unit test framework? Thanks, Lei Yang -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jimmy Huang Sent: 2008年9月4日 8:42 To: dev Subject: [Moblin Dev] (Re-attached) Content Manager Design Draft Attachedfor Review (Re-attached with doc) Hi, All, I completed a design document draft of Content Manager for Moblin 2.0, which is part of the Application and Framework infrastructure. It is based on Meta Tracker (Trackerd) and SQLite. Please review the document and provide feedbacks, or comments are welcome. Thanks. Content Manager project is hosted here: http://test.moblin.org/projects/content-manager Jimmy _______________________________________________ dev mailing list [email protected] https://www.moblin.org/mailman/listinfo/dev
