`
369128396
  • 浏览: 80953 次
  • 性别: Icon_minigender_2
  • 来自: 北京
社区版块
存档分类
最新评论

Kondor+ Adaptor Development Process

 
阅读更多
This need to discuss with team

NO  Steps  Comments 
1  read the elaboration document detailly before coding   
2  if mapping file is relate with new funcationality, verify the mapping file can work for new/modify/cx
  
3  code for functionality.
    If there is some important design or some implementation is different from current design document,
    update design document. ( review with your peer coder is suggested)

Error handling should be kept in mind.  Quick implementation for protoype is recommended. 
4  junit code for the important method.
  
5  If this update affects the input or output of the K+ Adapter( the K+ Adapter version must be updated),
   the MessageUpdaterFactory::createUpdaters should be updated.
   new case file like "trunk\test\data\input_kpluslbn.console_20090720.log.xml" should be added to verify the implementation.
  
6  check in your code after
     1)all of the junit test pass including other asset type.
    run it by 'ant test.report'
     2)basic healther check passed
     3)the functionality test relate with you new code can work.
     4)confirm no compile error in the code

     5) Input correct information when checking in. Follow the comments format of check in if exits.   
7  quick integration test base on integration test case.   
8  detail interation test base on integration test case.   
9  check whether all of the delivery is ready for release.
   if so, go to release process. 
分享到:
评论

相关推荐

Global site tag (gtag.js) - Google Analytics