If I understand correctly, http://meego.com/developers/meego-api shows MeeGo API.
Bests Jeff > -----Original Message----- > From: jari.tahvanai...@nokia.com [mailto:jari.tahvanai...@nokia.com] > Sent: Tuesday, April 26, 2011 4:39 PM > To: Zheng, Jeff; meego-qa@lists.meego.com > Subject: RE: MeeGo API coverage > > Hello, > > No need to have separate tree for coverage. We agreed on this meego-qa > weekly meeting today. > > For second question two additional ones > ... what suites are making "MeeGo API test suite"? > ... is there document/file somewhere listing the MeeGo API interfaces? > > Br, Jari > > -----Original Message----- > From: meego-qa-boun...@lists.meego.com > [mailto:meego-qa-boun...@lists.meego.com] On Behalf Of ext Zheng, Jeff > Sent: 22 April 2011 08:40 > To: meego-qa@lists.meego.com > Subject: [Meego-qa] MeeGo API coverage > > Hi, > > I tried to check in ConnMan API coverage into > https://meego.gitorious.org/meego-quality-assurance/mcts-coverage and > found > that tree has not been updated for 3 months. So I have questions here: > > 1. Is it necessary to maintain a separate tree for just mcts coverage? Can we > keep > the coverage into mcts tree. For example coverage.ods in each test > suite home directory? > 2. Is it possible that each MeeGo API test suite provides MeeGo API coverage > info? > > Bests > Jeff > _______________________________________________ > MeeGo-qa mailing list > MeeGo-qa@lists.meego.com > http://lists.meego.com/listinfo/meego-qa _______________________________________________ MeeGo-qa mailing list MeeGo-qa@lists.meego.com http://lists.meego.com/listinfo/meego-qa
