Changes between Version 22 and Version 23 of Developers/DevelopingCodeChanges

Timestamp:

2016-02-17T15:49:12+01:00 (8 years ago)

Author:

nicolasmartin

Comment:

--

Developers/DevelopingCodeChanges

@@ -68 +68 @@
 Test your change appropriately and record the results. The testing required will depend on the change and the potential impact on other configurations. When testing, things to consider include
 
- * full sucessfull SETTE tests: to check nothing is broken or goes wrong in the reference configurations SETTE tests: if running with some changes in the results, those have to be justified and checked in detail. New code should not change results when it is switched off, and not alter results when tuned on.
- * full succesfull specific tests: to be defined before starting, in order to check that development does indeed what is expected
- * ''Add here possible use of Trusting tool for a development branch (Nicolas?)''
+ * full successful SETTE tests: to check nothing is broken or goes wrong in the reference configurations SETTE tests: if running with some changes in the results, those have to be justified and checked in detail. New code should not change results when it is switched off, and not alter results when tuned on.
+ * full successful specific tests: to be defined before starting, in order to check that development does indeed what is expected
 
+''In particular the Trusting tool has been developed in order to ease the validation all along the working on the code, not all in one with SETTE. The developer can regularly evaluate the changes for a any given configuration compared with benchmark results he has defined.''
 === Document your Change ===
  * Progress in the development should be documented as the work goes on in the !ticket created at the beginning/