User Tools

Site Tools


developers:coverage

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
developers:coverage [2018/02/17 05:47] – [How to trigger a coverage report ?] Xavier Gonzedevelopers:coverage [2024/09/02 14:25] (current) Maryam Azizi
Line 1: Line 1:
 +<WRAP important>**IMPORTANT WARNING**\\ **<color #ed1c24>This Page is obsolete.</color>** Please refer to www.abinit.org!</WRAP>
 +
 ====== Code Coverage ====== ====== Code Coverage ======
  
Line 20: Line 22:
 ===== How to trigger a coverage report ? ===== ===== How to trigger a coverage report ? =====
  
-There is one slave dedicated to "on-demand" execution of branches by the developers, that produces a code coverage report, at present, tikal_gcc49_cov. It can be launched by the general "[[https://bbportal.abinit.org|on-demand]]" interface (contact Jean-Michel or Xavier if you do not yet have access to it).+There is one slave dedicated to "on-demand" execution of branches by the developers, that produces a code coverage report, at present, higgs_gnu_7.5_cov. It can be launched by the general "[[https://bbportal.abinit.org|on-demand]]" interface (see [[bb:misc|Use of buildbot for ABINIT]], contact Jean-Michel or Xavier if you do not yet have access to it).
 Code coverage reports from recent runs of the tests are available [[http://coverage.abinit.org/|here]] Code coverage reports from recent runs of the tests are available [[http://coverage.abinit.org/|here]]
 If you see parts of the code which are not well tested, please contribute to improving coverage by writing new tests ! \\ If you see parts of the code which are not well tested, please contribute to improving coverage by writing new tests ! \\
developers/coverage.1518846439.txt.gz · Last modified: 2018/02/17 05:47 by Xavier Gonze