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.3 RC1 Release"

 
(9 intermediate revisions by the same user not shown)
Line 8: Line 8:
  
 
|-
 
|-
| 407467
+
| 372286
| Both @OrderBy and @OrderColumn apply once selecting Order column radio button
+
| switch from embedded to embedded-id causes exception and duplicate attribute overrides
| Create JPA Project and JPA entites with at least 2 attributes
+
| Create JPA project
| JPA project and entities are created successfully
+
| JPA Project is created successfully
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Select an attribute in one of the entities and change the mapping to OneToMany
+
| Create two entites as follows
| Attribute is updated in editor to show @OneToMany
+
  @Entity
 +
public class Employee {
 +
 
 +
@Embedded
 +
private EmploymentPeriod period;
 +
}
 +
@Embeddable
 +
public class EmploymentPeriod {
 +
 
 +
private Date startDate;
 +
}
 +
| Entities are created successfully
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Expand Ordering in JPA Details pane and select Order column radio button
+
| Select the period attribute in the Employee entity in the JPA Structure tab
| Verify @OrderColumn annotation appears in the editor for the attribute and @OrderBy does not appear
+
| period appears in the JPA details pane
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Change mapping from OneToMany to ManyToMany
+
| Click on the mapped as link in the JPA Details pane and select Embedded ID and OK
| Verify mapping is updated and @OrderColumn annotation still appears
+
| Verify period is updated and mapped as Embedded ID and no index out of bounds errors appear in Error Log.
 
|-
 
|-
| ...
+
| 390124
| ...
+
| JPA Content tree does not have the right items for binary type
| Select None radio button in JPA Details for Ordering 
+
| Create JPA project
| Verify @OrderColumn annotation is removed from editor
+
| JPA project is created successfully
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Change mapping from ManyToMany to Element Collection
+
| Create the Test entity as per the bug
| Verify mapping is updated
+
| Entity is created successfully and appears correctly in the Explorer pane.
 
|-
 
|-
| ...
+
| 397765
| ...
+
| New Entity toolbar drop-down button appearing in all perspectives instead of just JPA perspective
| Expand Ordering in JPA Details pane and select Order column radio button
+
| Make sure JPA perspective is open and Create a new JPA project
| Verify @OrderColumn annotation appears in the editor for the attribute
+
| JPA project is created successfully
|-
+
| 407652
+
| Generate entities from tables wizard does not generate entities implementing java.io.Serializable
+
| Create a Java project
+
| Java project is created successfully
+
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| R-Click on Java project select configure > Convert to JPA Project...
+
| Find the JPA Entity button on the toolbar and click on the arrow
| Modify Faceted Project dialog appears
+
| Verify the drop down menu shows JPA Entity, JPA ORM Mapping File, EclipseLink ORM Mapping File & EclipseLink Dynamic Entity
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Leave defaults and click on Next and then Finish buttons.
+
| Change perspective to Java perspective
| Project is updated to JPA
+
| Verify JPA Entity button on the toolbar does not appear
 
|-
 
|-
 
| ...
 
| ...
| ,,,
 
| R-click on JPA project select JPA Tools > Generate Entities From Tables...
 
| Generate Custom Entities
 
|-
 
 
| ...
 
| ...
| ...
+
| Change perspective to web or other perspectives
| Select a few tables and then click on Finish button
+
| Verify that JPA Entity button on the toolbar does not appear
| Verify entities are created successfully, without error. Also verify that the entities implement serializable
+
|-
+
| 408149
+
| Missing key in jpt_jaxb_eclipselink_core_validation_description.properties
+
| Download latest Dali build
+
| All pre-reqs and build were downloaded successfully
+
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Open org.eclipse.jpt.jaxb.eclipselink.core jar file from the plugins directory
+
| Change perspective back to JPA
| All files appear in winzip dialog
+
| Verify JPA entity button appears on the toolbar
 
|-
 
|-
| ...
+
| 407630
| ...
+
| [JPA 2.0] [Validation] manytoone + ID not allowed in conjunction with an ID class.
| Open jpt_jaxb_eclipselink_core_validation_description.properties with wordpad
+
| Create JPA project  
| Verify OXM_FILE__NOT_LATEST_VERSION= appears on line 18 in the .properties file
+
| Project is created successfully
|-
+
| 408172
+
| 2.1 is default facet version for JAXB facet 
+
| Select File > New > Other
+
| New dialog appears
+
|-
+
| ...
+
| ...
+
| Select JAXB > JAXB Project and click on Next button
+
| JAXB Project page appears and verify that 2.2 appears as the default for JAXB version
+
|-
+
| 408174
+
| [EclipseLink] StringIndexOutOfBoundsException when typing new java type in oxm.xml
+
| Create a new JAXB 2.2 EL2.5 project
+
| JAXB project is created successfully
+
|-
+
| ...
+
| ...
+
| Create a new package, R-Click on New package and select EclipseLink MOXy OXM File
+
| New EclipseLink MOXy OXM File dialog appears and oxm.xml appears as default for file name
+
|-
+
| ...
+
| ...
+
| Click on Finish button
+
| Verify oxm.xml file is created successfully without error
+
|-
+
| ...
+
| ...
+
| Go to Source and enter null java-type name and Save
+
          <java-types>
+
    <java-type name=""></java-type>
+
  </java-types>
+
| Verify no errors appear in Error log
+
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Update source to have blank <java-type></java-type> and Save
+
| Create the DependentId Class per the bug
| Verify no errors appear in Error log
+
| The Dependent class is created successfully without error
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Update source to have a name <java-type name=test></java-type> and Save
+
| Create the Dependent entity per the bug
| Verify error in problems pane stating that name must be specified is removed
+
| Dependent entity is created successfully and verify that the following error does not appear in the problems pane The relationship 'emp' maps an ID, which is not allowed in conjuction with an ID class.

Latest revision as of 14:21, 12 June 2013

Dali 3.3

Dali 3.3 RC1 Release Manual Testing

Manual Testing for 3.3 RC1 Release
Bug No. Description Test Steps Test Step Results
372286 switch from embedded to embedded-id causes exception and duplicate attribute overrides Create JPA project JPA Project is created successfully
... ... Create two entites as follows
 @Entity

public class Employee {

@Embedded private EmploymentPeriod period; } @Embeddable public class EmploymentPeriod {

private Date startDate; }

Entities are created successfully
... ... Select the period attribute in the Employee entity in the JPA Structure tab period appears in the JPA details pane
... ... Click on the mapped as link in the JPA Details pane and select Embedded ID and OK Verify period is updated and mapped as Embedded ID and no index out of bounds errors appear in Error Log.
390124 JPA Content tree does not have the right items for binary type Create JPA project JPA project is created successfully
... ... Create the Test entity as per the bug Entity is created successfully and appears correctly in the Explorer pane.
397765 New Entity toolbar drop-down button appearing in all perspectives instead of just JPA perspective Make sure JPA perspective is open and Create a new JPA project JPA project is created successfully
... ... Find the JPA Entity button on the toolbar and click on the arrow Verify the drop down menu shows JPA Entity, JPA ORM Mapping File, EclipseLink ORM Mapping File & EclipseLink Dynamic Entity
... ... Change perspective to Java perspective Verify JPA Entity button on the toolbar does not appear
... ... Change perspective to web or other perspectives Verify that JPA Entity button on the toolbar does not appear
... ... Change perspective back to JPA Verify JPA entity button appears on the toolbar
407630 [JPA 2.0] [Validation] manytoone + ID not allowed in conjunction with an ID class. Create JPA project Project is created successfully
... ... Create the DependentId Class per the bug The Dependent class is created successfully without error
... ... Create the Dependent entity per the bug Dependent entity is created successfully and verify that the following error does not appear in the problems pane The relationship 'emp' maps an ID, which is not allowed in conjuction with an ID class.

Back to the top