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] Possible enhancement
Hello Bryan, First of all have a look at the "External data and special groups" section in the manual [1]. QF-Test already provides some miscellaneous statistical values. For example you can get the number of successful test-cases in the current test-run with ${qftest:count.testcases.ok}. Next you can write your own TestRunListener [2] for statistics that QF-Test doesn't already provide. For example the following TestRunListener counts the number of executed (check/event) steps - add a Jython Server Script with the following content to your setup sequence: from de.qfs.apps.qftest.extensions.qftest import TestRunListener class StatisticTestRunner (TestRunListener): def __init__(self): self.allSteps, self.checkSteps = 0, 0 self.eventSteps = 0 def runStopped(self, event): print "steps: %s\ncheckSteps: %s" % (self.allSteps, self.checkSteps) print "eventSteps: %s" % (self.eventSteps) # reset counts self.allSteps, self.checkSteps = 0, 0 self.eventSteps = 0 def nodeEntered(self, event): self.allSteps += 1 nodeType = event.getNode().getType() if (nodeType.startswith("Check")): self.checkSteps += 1 elif (nodeType.endswith("EventStep") or nodeType == "TextInputStep"): self.eventSteps += 1 global statisticTestRunner try: rc.removeTestRunListener(statisticTestRunner) except: pass statisticTestRunner = StatisticTestRunner() rc.addTestRunListener(statisticTestRunner) [1] https://www.qfs.de/qftest/manual/en/user_variables.html#usec_externaldata [2] https://www.qfs.de/qftest/manual/en/tech_testrunlisteners.html#sec_testrunlisteners Greetings, Yann Am 18.11.2014 20:16, schrieb Kaufman, Bryan H (IS): Hello, Has anyone ever asked for a feature that would report the number of test steps executed in a test suite? It would be nice to know how many steps, how many checks, the volume of testing being performed, etc. during a test run. It seems like it could be good marketing as well, to be able to express how much work is being performed by the automated testing tool. Thanks, Bryan Kaufman Highly Satisfied QF-Test user since 2008 _______________________________________________ qftest-list mailing list qftest-list@?.de http://www.qfs.de/mailman/listinfo/qftest-list -- _______________________________________________________________ Get the most out of QF-Test - Support directly from the authors * Training & consulting: www.qfs.de/en/qftest/training.html * Phone & email support: www.qfs.de/en/qftest/support.html _______________________________________________________________ Yann Felix Spöri Support E: support@?.de T: +49 (0)8171 38648-20 F: +49 (0)8171 38648-16 Quality First Software GmbH | www.qfs.de Tulpenstr. 41 | 82538 Geretsried | Germany 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.