Some of the below stats related to what functions are getting called, how many times and how long a function call takes were useful for our case.<\/p>\n
- \n
- ncalls \u2013 how many times the function\/method has been called<\/li>\n
- tottime \u2013 the total time in seconds excluding the time of other functions\/methods<\/li>\n
- percall \u2013 average time to execute function (per call)<\/li>\n
- cumtime \u2013 the total time in seconds includes the times of other functions it calls<\/li>\n
- percall \u2013 similar to the previous percall, however this one includes network delays,sleep<\/li>\n<\/ul>\n
\nHow to use cProfile<\/h3>\n
We will use cProfile to get some useful stats for our GUI tests which is built based on Python Selenium Page Object Model Framework.<\/a>. cProfile is included in Python’s standard library.<\/p>\n
\nCoding changes in Python Framework for profiling:<\/strong>
\nTo add profiling to your code you just need 5 to 6 lines of additional code. We need to import cProfile first, then create a profile object, enable it, disable it after the function we want to profile has been called and save the stats to a file. You can look at the example below.<\/p>\nimport cProfile, pstats\r\npr = cProfile.Profile()\r\npr.enable()\r\n\r\ntest_example_form()---your code\r\n\r\npr.disable()\r\nps = pstats.Stats(pr).print_stats()\r\n\r\n<\/pre>\n
\nStatistics to know how many time a particular function has been called<\/strong>
\nIn our Qxf2 based framework test, there is a test case named test_successive_form_creation. We are trying to fill in details like name, phone, email, etc and then submit the form multiple times. In case we need to get details on how many times the form was submitted we can get the details using the above code. You may need to filter out the function names. Under statistics we have the last column named as “filename:lineno(function)”, we can filter out the required function name by a search.<\/p>\n![\"\"](\"https:\/\/qxf2.com\/blog\/wp-content\/uploads\/2019\/08\/cprofile_statistics.png\")
<\/a>cprofile statistics<\/figcaption><\/figure>\n
\nLooking at the statistics to know how many times Exception has been caught<\/strong><\/p>\n
With cProfile statistics, we can track the Exceptions too. However, in Our framework, we have some wrapper(Wrapit.py), containing Exception Handlers so we can’t exactly see the exception. The Exception handler decorator is used to capture exceptions. This decorator is used, when an error occurs to prevents tests from stopping. If we want to check how many times exception handler in Wrapit.py got called, we can test the test_example_form with some missing info. Since our framework uses a testrail util to submit test results to testrail, we will try to report test results without passing testrail id. Now we can check the cprofile statistics to get this information as shown below:<\/p>\n
![\"\"](\"https:\/\/qxf2.com\/blog\/wp-content\/uploads\/2019\/08\/cprofile_exception.png\")
<\/a>cprofile_exception<\/figcaption><\/figure>
\nAlso in case you want to reuse the statistics from the file, you may want to save it to a readable file and reuse it. For more details of how to save the statistics in a csvfile, you can refer to our blog<\/a>.<\/p>\n
\nUsing cprofilev as a wrapper on command line:<\/h3>\n
We also found some cool tool to visually view the cProfile stats better. cprofilev<\/a> is a simple way of profiling your Python program. When you run python code with cprofilev from the command line, it gives you output on html page running on http:\/\/localhost:4000. When you run your code, it opens up 4000 port for profile statistics. User can view the same on that port. The beauty of cprofilev is you can sort the statics, as well as you can view particular function statistics just by clicking on that particular function.<\/p>\n
Installation of cprofilev:<\/p>\n
\r\npip install cprofilev\r\n<\/pre>\n
We can run our code with cprofilev as below:<\/p>\n
\r\npython -m cprofilev test_example_form.py\r\n<\/pre>\n
![\"\"](\"https:\/\/qxf2.com\/blog\/wp-content\/uploads\/2019\/08\/cprofilev_new_example-1.png\")
<\/a>cprofilev statistics<\/figcaption><\/figure>\n Hope you find this article useful!!<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
In general, when we have some performance problem with our code, profilers can be used to help identify where the problem actually lies. It can be used to check how long the functions defined in your code took to execute, how many times a particular function is being called etc. We were able to use cProfile to find out some […]<\/p>\n","protected":false},"author":21,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[194,18,61],"tags":[],"class_list":["post-11087","post","type-post","status-publish","format-standard","hentry","category-cprofile","category-python","category-testing"],"_links":{"self":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/11087","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/comments?post=11087"}],"version-history":[{"count":45,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/11087\/revisions"}],"predecessor-version":[{"id":11389,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/11087\/revisions\/11389"}],"wp:attachment":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/media?parent=11087"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/categories?post=11087"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/tags?post=11087"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}