qa:runtests:requirements

Differences

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

Link to this comparison view

Next revision
Previous revision
qa:runtests:requirements [2009/05/20 11:40]
zoe created
qa:runtests:requirements [2009/07/25 11:21]
zoe
Line 6: Line 6:
   * We should have a better way to collect output from test runs than we currently have (they are mailed to the qa-reports list). A better solution would be to have a web page or set of web pages that show the last known status of PHP test pass and fails on as many platforms as possible. Doing this will be much easier if we can make run-tests.php produce XML output.   * We should have a better way to collect output from test runs than we currently have (they are mailed to the qa-reports list). A better solution would be to have a web page or set of web pages that show the last known status of PHP test pass and fails on as many platforms as possible. Doing this will be much easier if we can make run-tests.php produce XML output.
   * The  run-tests.php code has been around since 2000. It is in a single file and has had many additions and changes over the years. As a result the logic which started off clear and simple has become tangled and will become increasingly difficult to maintain. Therefore, ease of maintenance is the final reason for considering a re-write.   * The  run-tests.php code has been around since 2000. It is in a single file and has had many additions and changes over the years. As a result the logic which started off clear and simple has become tangled and will become increasingly difficult to maintain. Therefore, ease of maintenance is the final reason for considering a re-write.
 +
 +
  
 ===== Usability ===== ===== Usability =====
Line 23: Line 25:
  
 Any new code must be easy to maintain and easy to extend. This means that we have to be clear about and agree on things like formatting, naming conventions and so on. Any new code must be easy to maintain and easy to extend. This means that we have to be clear about and agree on things like formatting, naming conventions and so on.
 +
 +===== Additional requirements=====
 +
 +  * Be able to skip whole directories with one check
 +  * Provide the same functionality as REDEIRECTTEST, not necessarily using the current design
 +  * Provide an API so thatthe code can be used by other applications (from Greg Beaver).
 +  * An option to specify arguments to valgrind
  
qa/runtests/requirements.txt · Last modified: 2017/09/22 13:28 (external edit)