qa:runtests:requirements

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
qa:runtests:requirements [2009/07/25 07:23]
zoe
qa:runtests:requirements [2017/09/22 13:28] (current)
Line 7: Line 7:
   * 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.
  
-There is another, perhaps obvious, requirement. The new code must produce exactly the same results as the old code.+
  
 ===== Usability ===== ===== Usability =====
Line 31: Line 31:
   * Provide the same functionality as REDEIRECTTEST, not necessarily using the current design   * 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).   * 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.1248506597.txt.gz · Last modified: 2017/09/22 13:28 (external edit)