[ET Trac] [Einstein Toolkit] #124: Implement a testing mechanism for simfactory

Einstein Toolkit trac-noreply at einsteintoolkit.org
Mon Nov 29 10:46:10 CST 2010


#124: Implement a testing mechanism for simfactory
-------------------------+--------------------------------------------------
 Reporter:  hinder       |       Owner:  mthomas
     Type:  enhancement  |      Status:  new    
 Priority:  major        |   Milestone:         
Component:  SimFactory   |     Version:         
 Keywords:               |  
-------------------------+--------------------------------------------------
 Currently there is no easy way to check that a change to simfactory hasn't
 broken critical functionality.  A system could be introduced to run
 through each command and check that it does the right thing.  It won't be
 possible to check every single combination of possible options, but the
 most commonly used options should be tested.

 A first attempt could involve testing that the commands work locally on
 the current machine. This would involve submitting jobs and testing that
 they have the expected behaviour.  On busy machines, this means that the
 tests could potentially take a long time to complete.

 Remote submission could be tested by running these tests from a central
 location (e.g. the developer's workstation or laptop).

 We could also include a python correctness checking step in these tests
 (e.g. using pychecker or pylint).

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/124>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit


More information about the Trac mailing list