Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Dali 3.1 M2"

Line 30: Line 30:
 
| ...
 
| ...
 
| ...
 
| ...
| Change the map type for parcels from Embeddable to One-to-Many and removed <Address, PropertyInfo>
+
| Open the orm.xml mapping file, Add the PropertyRecord Entity to the file, Add the parcels attribute to the orm.xml mapped as element collection, add <map-key-class class=""/> to the orm.xml via the editor and then Save
 +
| Verify the error Map Key class is not defined appears in the Problems pane
 +
|-
 +
| ...
 +
| ...
 +
| Add Test inside the "" <map-key-class class="Test"/> and Save
 +
| Verify the Map Key class is not defined changes to Map Key class does not exist on project classpath in the Problems pane
 +
|-
 +
| ...
 +
| ...
 +
| Change the map type for parcels from Embeddable to One-to-Many and remove <Address, PropertyInfo>
 
| Verify 3 error appear
 
| Verify 3 error appear
 +
|-
 +
| ...
 +
| ...
 +
|
 +
|
 +
|-
 +
| ...
 +
| ...
 +
|
 +
|
 +
|-
 +
| ...
 +
| ...
 +
|
 +
|
 +
|-
 +
| ...
 +
| ...
 +
|
 +
|
 +
|-
 +
| ...
 +
| ...
 +
|
 +
|
 +
|-
 +
| ...
 +
| ...
 +
|
 +
|
 +
|-
 +
| ...
 +
| ...
 +
|
 +
|
 +
|-
 +
| ...
 +
| ...
 +
|
 +
|
 
|-
 
|-
 
| 357941
 
| 357941

Revision as of 10:03, 4 October 2011

Dali 3.1

Dali 3.1 M2 Manual Testing

Manual Testing for 3.1 M2 Release
Bug No. Description Test Steps Test Step Results
303527 [JPA2.0] MapKeyJoinColumn/MapKeyJoinColumns model support ... ...
348102 [Validation] @XmlElements validation and content assist ... ...
354676 [Validation][JPA2.0] MapKeyClass validation needed for 1-m and m-m mappings Import the Bug354676 project on the testing box in the lab Project is imported successfully and 3 errors and 1 warning appear in Problems pane
... ... Make the Map generic (Edit Map to be Map <Address, PropertyInfo> parcels;) and then Save Verify MapKeyClass and Target Class errors are removed along with the warning.
... ... Open the orm.xml mapping file, Add the PropertyRecord Entity to the file, Add the parcels attribute to the orm.xml mapped as element collection, add <map-key-class class=""/> to the orm.xml via the editor and then Save Verify the error Map Key class is not defined appears in the Problems pane
... ... Add Test inside the "" <map-key-class class="Test"/> and Save Verify the Map Key class is not defined changes to Map Key class does not exist on project classpath in the Problems pane
... ... Change the map type for parcels from Embeddable to One-to-Many and remove <Address, PropertyInfo> Verify 3 error appear
... ...
... ...
... ...
... ...
... ...
... ...
... ...
... ...
357941 ArrayIndexOutOfBoundsException when switching from PrimaryKeyJoinColumn strategy to mappedBy Create JPA 2.0 Project Project is created successfully
... ... Add to entities from tables and join two of the tables as a one-to-one Entities are added successfully
... ... Go to the One-to-one mapping field in the jpa details pane and click on the Primary Join Key Columns within the Joining Strategy section. Verify the editor for the entity adds the following annotation for the field @PrimaryKeyJoinColumn
... ... Now select Mapped by in the jpa deails pane under the Joining Strategy section Verify no errors appear and the editor for the entity now shows @OneToOne(mappedBy = "")
... ... Select Primary Join Key Columns radio button Verify no errors appear and editor is updated
... ... Select Join Columns radio button Verify no errors appear and editor is updated (for Join columns there is no annotation unless you override the default)
... ... Select Primary Join Key Columns radio button Verify no errors appear and editor is upated
... ... Select Join Table radio button Verify no errors appearand editor is updated

Back to the top