Changes between Version 4 and Version 5 of Document/Development/Testing/IsolateFromFrameworkCouplings

Show
Ignore:
Timestamp:
06/14/09 01:28:36 (4 years ago)
Author:
poundjd (IP: 68.32.33.27)
Comment:

minor changes to improve readability.

Legend:

Unmodified
Added
Removed
Modified
  • Document/Development/Testing/IsolateFromFrameworkCouplings

    v4 v5  
    1 Ideally, unit tests must be isolated and decoupled from the rest of the system. In large frameworks like EBox we must make a effort to isolate the tests. 
    2 Remember: if we had to run the tests as root or as the ebox user it will be a very bad smell about coupling. 
     1Ideally, unit tests must be isolated and decoupled from the rest of the system. In large frameworks like eBox we must make a strong effort to isolate the tests from the applications and framework. 
     2 
     3Remember: if we had to run the tests as root or as the eBox user that would indicate a very tight coupling between eBox and the unit tests, and that is a bad thing. 
    34 
    45Isolation issues: 
    56 
    6  * EBox configuration 
    7  * Sudo commands execution 
    8  * EBox::Config file path 
    9  * EBox logs 
     7 * eBox configuration 
     8 * sudo command execution 
     9 * eBox::Config file path 
     10 * eBox logs 
    1011    * EBox exceptions (they write to logs) 
    1112 * Coding module bad practices