Jump to: navigation, search

Dali 3.1 M2

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
... ... In the JPA Details pane change the Target Class to test and Save Verify the following error apepars in problems pane - Target class does not exist on project classpath
... ... Change the Target class back to the default and Save Target class does not exist on project classpath error is removed
... ... Remove the PropertyRecord Entity from the orm.xml and Save Only 1 error remains in the problems pane for Collection Table
... ... Go back to the PropertyRecord editor, Change the map type for parcels from Embeddable to One-to-Many and remove <Address, PropertyInfo> and Save Verify 2 errors appear in problems pane stating - Target class is not defined - Map Key class is not defined a
... ... 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 and only one error appears
... ... Open the orm.xml mapping file, Add the PropertyRecord Entity to the file, Add the parcels attribute to the orm.xml mapped as One-to-One, 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
... ... In the JPA Details pane change the Target Class to test and Save Verify the following error apepars in problems pane - Target class does not exist on project classpath
... ... Change the Target class back to the default and Save Target class does not exist on project classpath error is removed
... ... Remove the PropertyRecord Entity from the orm.xml and Save Only 1 error remains in the problems pane for Target Entity...
... ... Go back to the PropertyRecord editor, Change the map type for parcels from One-to-Many to Many-to-Many and remove <Address, PropertyInfo> and Save Verify 2 errors appear in problems pane stating - Target class is not defined - Map Key class is not defined a
... ... 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 and only one error appears
... ... Open the orm.xml mapping file, Add the PropertyRecord Entity to the file, Add the parcels attribute to the orm.xml mapped as Many-to-Many, 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
... ... In the JPA Details pane change the Target Class to test and Save Verify the following error apepars in problems pane - Target class does not exist on project classpath
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
357948 Null text range for message ID: QUERY_STATEMENT_UNDEFINED Create JPA 2.0, EL 2.2.x project Project is created successfully
... ... Create JPA Entity with one field as the key field. JPA entity is created successfully
... ... Select the Entity in the JPA Structure pane and then expand the Queries Field in the JPA Details pane and Click on Add button for Query Add Query dialog appears
... ... Enter a name and select Named Query from the Type drop down and click on OK button. Query is created correctly
... ... Save the project Verify the project is saved and no errors appear in the Error Log