Jump to: navigation, search

Difference between revisions of "CDO Development Guidelines"

(Member)
(Guideline for writing test cases)
Line 13: Line 13:
  
 
==Guideline for writing test cases==
 
==Guideline for writing test cases==
 +
 +
 +
==General Requirements==
 +
 +
==Legacy Mode==
 +
 +
In the CDO Suite the Legacy Mode is always activated. This means that you do not need set this mode for every test case. But this also means that you need to deactivate it if you want to execute tests without legacy.
 +
 +
Please always use CDOUti.getCDObject and CDOUtil.getEObject() to get either the CDOObject or the expected interal instance, no matter whethter you are using legay or not. The will make the test compatible to all legacy test cases and avoids ugly ClassCastExceptions.

Revision as of 03:30, 26 April 2010

Coding Guidlines

This page is not yet finished. Do not take these guidelines for granted until the note is removed!

Basic Coding Guidelines

The following Guide describes the basic requirements for creating CDO source code. Not all of these guidlines can be coverred by the auto-format for Java source Code (Strg+Shift+F). If you like to write an extension that allows comfortably adjusting the code regarding these Guidelines you are welcome.

Members

Methods

Getter and Setter

Guideline for writing test cases

General Requirements

Legacy Mode

In the CDO Suite the Legacy Mode is always activated. This means that you do not need set this mode for every test case. But this also means that you need to deactivate it if you want to execute tests without legacy.

Please always use CDOUti.getCDObject and CDOUtil.getEObject() to get either the CDOObject or the expected interal instance, no matter whethter you are using legay or not. The will make the test compatible to all legacy test cases and avoids ugly ClassCastExceptions.