Changes between Version 59 and Version 60 of ProgrammingGuidelines


Ignore:
Timestamp:
10/26/12 11:52:49 (7 years ago)
Author:
welberge
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProgrammingGuidelines

    v59 v60  
    33[[PageOutline]] 
    44= Programming guidelines and toolkit selection = 
    5 We ask contributors to Elckerlyc to adhere to certain programming guidelines. During the development of Elckerlyc we have selected certain 'standard' libraries for specific tasks (for e.g. logging, unit testing, collections). Contributions to Elckerlyc should preferable not introduce dependencies on new libraries that provide very similar functionality as these libraries. 
     5We ask contributors to Asap to adhere to certain programming guidelines. During the development of Asap we have selected certain 'standard' libraries for specific tasks (for e.g. logging, unit testing, collections). Contributions to Elckerlyc should preferable not introduce dependencies on new libraries that provide very similar functionality as these libraries. 
    66== Library overview == 
    77||=Functionality=||=library=|| 
     
    156156 
    157157== Unit and integration testing == 
    158 Elckerlyc uses the [[http://www.junit.org/|JUnit]] framework for its automatic testing.  
     158Asap uses the [[http://www.junit.org/|JUnit]] framework for its automatic testing.  
    159159=== Testing guidelines === 
    160160 1. Test cases should be simple. Reduce complexity in setup with generic setup functions and/or @Before. Reduce checking complexity and clarity with custom asserts. Avoid using conditional branches in tests cases.