La liste de diffusion est fermée depuis juillet 2022, mais sert toujours d'archive d'informations sur QF-Test.
Cependant, si vous souhaitez rester informé des nouveautés concernant QF-Test, vous pouvez simplement vous abonner à la newsletter :
abonner à la newsletter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] code coverage for QFT tests
Hi Vasilena, QF-Test only instruments the org.eclipse.swt... jar. I don't think you'll want coverage information for the low level SWT methods - you should probably focus on instrumenting just the jar files of your plugin. That way, there shouldn't be any conflict. Best regards, Greg "Treneva, Vasilena" <Vasilena.Treneva@?.com> writes: > Hi All, > > Do you know if it is possible to achieve code coverage (for eclipse based plugins) for QFT tests? > > The library that we want to use is JaCoCo Java Code Coverage Library, however as far as I know QFT > instruments eclipse jars and JaCoCo would intend to do the same… > > Do you know what is the best approach here? Has anyone tried something similar? Any advice? > > Thanks, > > Vassilena -- Gregor Schmid Gregor.Schmid@?.de Quality First Software GmbH http://www.qfs.de Tulpenstr. 41 Tel: +49 8171 38648-0 DE-82538 Geretsried Fax: +49 8171 3864816 GF: Gregor Schmid, Karlheinz Kellerer HRB München 140833
|
1. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.