Jump to: navigation, search

Difference between revisions of "Dali 3.4 M1 Release"

 
(10 intermediate revisions by the same user not shown)
Line 27: Line 27:
 
| Expand Ordering section
 
| Expand Ordering section
 
| Verify 3 radio buttons appears for None, Custom (which also contains a text field) and Order column (which also contains a Name text field)
 
| Verify 3 radio buttons appears for None, Custom (which also contains a text field) and Order column (which also contains a Name text field)
 +
|-
 +
| ...
 +
| ...
 +
| Click on Order column radio button
 +
| Verify <order-column/> appears in the orm.xml editor
 +
|-
 +
| ...
 +
| ...
 +
| Enter text into the Name field for Order column
 +
| Verify the text entered appears in the orm.xml editor ex. <order-column name="testname"/>
 +
|-
 +
| ...
 +
| ...
 +
| Remove the order-column annotation and enter <order-by/>
 +
| Verify order-column radio button is deselected and Custom radio button is selected and Default(primary key) appears in the text field in the JPA Details section
 +
|-
 +
| ...
 +
| ...
 +
| Click on None radio button
 +
| Verify <order-by/> annotation is removed in the editor
 +
|-
 +
| 313204
 +
| [API] Incorrect validation errors on EclipseLink example of derivied Id?
 +
| Launch Eclipse, open JPA Perspective, Import the program attached to the bug
 +
| Verify project is imported successfully
 
|-
 
|-
 
| ...
 
| ...
Line 32: Line 57:
 
|  
 
|  
 
|
 
|
 +
|-
 +
| 315480
 +
| Ability to open orm.xml file for target entity
 +
| Create JPA EclipseLink project, Some JPA entities
 +
| Project and entities are created successfully
 +
|-
 +
| 347842
 +
| [EclipseLink][Validation] No id class validation when id class defined on mapped superclass
 +
| Create JPA project with EL platform and then setup 3 classes/entities per the bug use case
 +
| JPA project is created successfully.  Verify a couple of validation errors appear for the  PartTimeEmployee entity in the problems pane. Verify these two validation errors appear 1. The attribute matching the ID class attribute id1 does not have the correct type int 2. There is no primary key attribute to match the ID class attribute id2
 +
|-
 +
| ...
 +
| ...
 +
| Create another JPA project with Generic platform and then setup 3 classes/entities per the bug use case
 +
| JPA project is created successfully.  Verify the above validation errors now appear for the CompanyEmployee mapped superclass in the problems pane. Verify these two validation errors appear 1. The attribute matching the ID class attribute id1 does not have the correct type int 2. There is no primary key attribute to match the ID class attribute id2
 +
 +
|-
 +
| 388631
 +
| Generate entities from tables: FileNotFoundException if directory name in Eclipse's path begins with '!'
 +
| Install eclipse build into a directory such as D:/! ... and then launch eclipse
 +
| Verify eclipse launches
 +
|-
 +
| ...
 +
| ...
 +
| Select New > JPA Project
 +
| New JPA Project dialog appears
 +
|-
 +
| ...
 +
| ...
 +
| Create a JPA Project with DB connection
 +
| JPA Project is created successfully
 +
|-
 +
| ...
 +
| ...
 +
| R-Click on JPA Project and select JPA Tools > Generate Entities from Tables...
 +
| Generate Entities from Tables dialog appears
 +
|-
 +
| ...
 +
| ...
 +
| Select some tables and click on the finish button
 +
| Verify the entities are created successfully and no errors appear due to eclipse and the workspace being in the /! directory
 +
|-
 +
| 414574
 +
| ClassCastException when editing order-by for custom in orm.xml editor
 +
| Create JPA Project and JPA entity with a few attributes and then map one of the attributes as an element collection
 +
| JPA Project and entity with attributes are created successfully
 +
|-
 +
| ...
 +
| ...
 +
| R-click on the project and select New > JPA ORM Mapping file
 +
| New Mapping file dialog appears
 +
|-
 +
| ...
 +
| ...
 +
| Leave defaults and click on Finish button
 +
| orm.xml file is created successfully and appears in editor
 +
|-
 +
| ...
 +
| ...
 +
| Add the Entity and the element collection attribute to the orm.xml mapping file
 +
| Verify the entity and attribute are added successfully and annotated correctly in the source for the orm.xml
 +
|-
 +
| ...
 +
| ...
 +
| Expand ordering section in the JPA Details pane for the element collection attribute and select the custom radio button
 +
| Verify <order-by></order-by> appears in the editor of the orm.xml file and no errors appear
 +
|-
 +
| ...
 +
| ...
 +
| Manually add text for the order by annotation (ex. <order-by>lName</order-by>) and Save project
 +
| Verify no errors appear and lName appears in the custom text field in the JPA Details pane

Latest revision as of 13:40, 9 October 2013

Dali 3.4

Dali 3.4 M1 Manual Testing

Manual Testing for 3.4 M1 Release
Bug No. Description Test Steps Test Step Results
190866 Unable to set 'Primary Key Ordering' for orm.xml multi-relationship mapping Create JPA Project, Create JPA entity with some attributes JPA project and entity are created successfully
... ... Add orm.xml mapping file to project orm.xml file is added successfully and opened in editor
... ... Add JPA Entity to the orm.xml mapping file, then add an attribute in the entity as an element collection to the orm.xml mapping file Attribute is added and appears in the JPA details
... ... Expand Ordering section Verify 3 radio buttons appears for None, Custom (which also contains a text field) and Order column (which also contains a Name text field)
... ... Click on Order column radio button Verify <order-column/> appears in the orm.xml editor
... ... Enter text into the Name field for Order column Verify the text entered appears in the orm.xml editor ex. <order-column name="testname"/>
... ... Remove the order-column annotation and enter <order-by/> Verify order-column radio button is deselected and Custom radio button is selected and Default(primary key) appears in the text field in the JPA Details section
... ... Click on None radio button Verify <order-by/> annotation is removed in the editor
313204 [API] Incorrect validation errors on EclipseLink example of derivied Id? Launch Eclipse, open JPA Perspective, Import the program attached to the bug Verify project is imported successfully
... ...
315480 Ability to open orm.xml file for target entity Create JPA EclipseLink project, Some JPA entities Project and entities are created successfully
347842 [EclipseLink][Validation] No id class validation when id class defined on mapped superclass Create JPA project with EL platform and then setup 3 classes/entities per the bug use case JPA project is created successfully. Verify a couple of validation errors appear for the PartTimeEmployee entity in the problems pane. Verify these two validation errors appear 1. The attribute matching the ID class attribute id1 does not have the correct type int 2. There is no primary key attribute to match the ID class attribute id2
... ... Create another JPA project with Generic platform and then setup 3 classes/entities per the bug use case JPA project is created successfully. Verify the above validation errors now appear for the CompanyEmployee mapped superclass in the problems pane. Verify these two validation errors appear 1. The attribute matching the ID class attribute id1 does not have the correct type int 2. There is no primary key attribute to match the ID class attribute id2
388631 Generate entities from tables: FileNotFoundException if directory name in Eclipse's path begins with '!' Install eclipse build into a directory such as D:/! ... and then launch eclipse Verify eclipse launches
... ... Select New > JPA Project New JPA Project dialog appears
... ... Create a JPA Project with DB connection JPA Project is created successfully
... ... R-Click on JPA Project and select JPA Tools > Generate Entities from Tables... Generate Entities from Tables dialog appears
... ... Select some tables and click on the finish button Verify the entities are created successfully and no errors appear due to eclipse and the workspace being in the /! directory
414574 ClassCastException when editing order-by for custom in orm.xml editor Create JPA Project and JPA entity with a few attributes and then map one of the attributes as an element collection JPA Project and entity with attributes are created successfully
... ... R-click on the project and select New > JPA ORM Mapping file New Mapping file dialog appears
... ... Leave defaults and click on Finish button orm.xml file is created successfully and appears in editor
... ... Add the Entity and the element collection attribute to the orm.xml mapping file Verify the entity and attribute are added successfully and annotated correctly in the source for the orm.xml
... ... Expand ordering section in the JPA Details pane for the element collection attribute and select the custom radio button Verify <order-by></order-by> appears in the editor of the orm.xml file and no errors appear
... ... Manually add text for the order by annotation (ex. <order-by>lName</order-by>) and Save project Verify no errors appear and lName appears in the custom text field in the JPA Details pane