Jump to: navigation, search

Dali 3.0.2

Dali 3.0

Dali 3.0.2 Manual Testing

Manual Testing for 3.0.2 Release
Bug No. Description Test Steps Test Step Results
342171 Mapping One to Many - chooses override in Details and receive out-of-bounds error Create JPA Project, Create JPA entity with at 2 fields (making one a key id field) Project and entity are created successfully without error
... ... Select the entity in the Structure pane, select the attribute that is not the id field, map the attribute as one to many Attribute is mapped as one to many
... ... In details section for 2nd attribute click on join columns override default

checkbox

Verify no Out of Bounds error appears
347368 UnsupportedOperationException when element collection contains nested relationship mapping using JoinTable strategy Create JPA Project with the 3 mapped types stated in the Bug Project and mapping types were created successfully
... ... Create ORM mapping file, Add Employee entity to the mapping file Employee entity is added successfully
... ... Right-click the attribute "empType" of Employee entity in the JPA structure

pane and add it to the mapping xml as an Element collection

empType is added successfully
... ... Expand Value section in JPA Details, Select phone and check Override default checkbox and Save project Verify project is saved and no UnsupportedOperationException appears in the error log
349533 Generate Entities from Tables, cannot remove cascading of association Create JPA 2.0, Generic 2.0 Project with DB connection Project and Entity are created successfully
... ... R-Click on Project and select New > JPA Entities From Tables Generate Custom Entities dialog appears
... ... Select two tables and click on the Next button Table Associations page appear
... ... Click on New Association (+) button and Add a one-to-one association Association appears in Table associations list
... ... Select the added association, Click on button to Select Cascade, Check persist checkbox and click on OK Persist appears for Cascade field
... ... Click on the Select Cascade button again and remove the checkbox from Persist and click on OK Verify the Cascade field is blank and no errors appear
354804 Can't remove @NamedNativeQuery#resultClass field from ui Create JPA project and JPA Entity JPA Project and entity are created successfully
... ... Select the Entity, Expand Queries in JPA Details section, Click on Add button Add Query Dialog appears
... ... Add a Native Named Query Native Named Query is added successfully
... ... Click on Browse button for Result Class and add a Result Class Verify the class source shows the selected Result Class from the JPA Details pane
... ... Remove the Result Class from the text field in JPA Details Verify it is removed from the .java source
357360 Wrong Validation message in NewNameStateObject Download latest version of Dali Latest version is downloaded
... ... Open jpt_common_ui.properties file which resides in org.eclipse.jpt.common.ui jar file in the Plug-ins folder Verify NewNameStateObject_nameAlreadyExists=An object with this name already exists
357954 CCE creating eclipselink-orm.xml file with access type set Create an EclipseLink project Project is created successfully
... ... R-Click on the Project, Select New>EclipseLink ORM Mapping File New EclipseLink Mapping File dialog appears
... ... Click on the Next button, Click on Drop Down for Default Access Verify None, Field and Property appear in the drop down list
... ... Select Property from the drop down list and click on the finish button Verify the EclipseLink ORM Mapping File is created successfully without an error
... ... Remove the EL ORM Mapping file, Create a new one with Field instead of Property for the default access Verify the EclipseLink ORM Mapping File is created successfully withou an error
359585 Missing bundle key in JPQL validation Create JPA Project and JPA Entity and save project JPA Project and Entity are created successfully
... ... Add JPA orm mapping file to the project and add the entity to the orm mapping file Entity is added to orm.xml file successfully
... ... Add a named query via the JPA Details pane Named query is added successfully
... ... Add the following query for the named query in the JPA details pane Select o from Owner o JOIN o.pets and Save the project Query is added successfully and without error
... ... Place the cursor at the end of the query and then hit the backspace key to remove the s from pets and Save Verify the project saved successfully and there is errors
359644 JPQL completion causes tabs and enters to be replaced by \t and \n Create JPA project and JPA Entity with 2 fields and one of them being an ID JPA project and Entity are created successfully
... ... Create JPA ORM Mapping File Mapping File is created successfully
... ... Expand Queries for the orm.xml file in the JPA Details pane and Add a Named Query Named Query is added successfully with error stating you need a Query Statement
... ... Add the following Query statement in the orm.xml editor
   <query> 
       SELECT 
           _testEntity 
       FROM 
           Address _testEntity
       WHERE 
           _testEntity.Address.Id = :ID
   </query>
Verify it appears in the JPA Details pane for Query and the error is removed
... ... Place the cursor behind the d in the JPA Details pane and backspace to remove the d, then use content assist to add the Address.Id back correctly Verify the orm.xml editor remains the same and no \n or \t characters appear in the editor
360554 NPE when changing a class to an enum (or enum to class) Create JPA project and create a class Project and class are created successfully
... ... Open the class in the editor and Change Public class to Public enum Verify class is changed to enum successfully and no errors appear in Error log
... ... Create JAXB project and create a class JAXB Project and class are created successfully
... ... Open the class in the editor and Change Public class to Public enum Verify class is changed to enum successfully and no errors appear in Error log
360583 No JPQL query validation when using undo/redo actions Create JPA Project, Create JPA entity with 1 id field Project and entity are created successfully
... ... Select the entity, expand the Queries section and Add a query Query is added successfully
... ... Enter select e from <entityName> e where into the Query field Query appears in the editor and where clause in Details pane appears with red underline
... ... Select the JPQL identifier where and hit DELETE Verify validation error disappears from the clause in JPA Details pane
... ... Do CTRL-Z for undo Verify the validation error appears in JPA Details pane for where clause
361281 JpaFacetActionPage leaks IFacetedProjectListener (never removed) Select New>Other New wizard dialog appears
... ... Select Web>Dynamic Web Project and click on Next button Dynamic Web Project page appears
... ... Enter a project name (webproject) and click on the Modify button Project Facets dialog appears
... ... Check the JPA checkbox and click on OK button You are returned to the New Dynamic Web Project dialog
... ... Click on the Next button twice JPA Facet page appears for settings
... ... Click Back button twice, Click Modify button, Remove check from JPA checkbox, click on OK button, and click on Next button twice Verify JPA Facet page does not appear and Web Module page appears
... ... Create a Dynamic Web Project with JPA enabled Project is created successfully
... ... R-Click on the project and select Properties Properties dialog appears and the Project Facet JPA is checked
... ... Uncheck the JPA checkbox, Click on Apply, click on JPA Verify text appears stating 'the project facet that this property page belongs is not present in the project.
... ... Click on OK button Verify the JPA Content folder was removed from the project and no errors appear in error log
... ... R-Click on the project and select Properties Verify the JPA < Project Facets page is not present
... ... Check the JPA project Facet checkbox, Click on Further configuration available link, Add the JPA settings, click on OK for JPA Settings, Click on OK to close properties dialog Verify JPA content is added back to project and no errors appear in error log
363306 [EclipseLink] sql-script generation deletes the generated files Create JPA EL project with DB connection Project is created successfully
... ... R-Click on the project, Select JPA Tools>Generate Tables from Entities... Generate Tables from Entites dialog appears with 3 radio buttons and Database is selected by default
... ... Select Sql-script radio button and click on Finish button Generating DDL dialog appears.
... ... Click on No button Verify dialog closes and nothing happens
... ... R-Click on project, select JPA Tools>Generate Tables from Entities..., Select Sql-script radio button, click on Finish button, Click on Yes button Verify Console shows the log of events
... ... Refresh the project Verify createDDL.sql and dropDDL.sql files do not appear under the project
... ... R-Click on project, select JPA Tools>Generate Tables from Entities..., Select Sql-script radio button, click on Finish button, Click on Yes button Verify Console shows the log
... ... Refresh the project Verify createDDL.sql and dropDDL.sql files appear under the project.
... ... Remove the createDDL.sql and dropDDL.sql files under the project Files are removed successfully
... ... R-Click on project, select JPA Tools>Generate Tables from Entities..., Select Both radio button, click on Finish button, Click on Yes button Verify Console shows the log
... ... Refresh the project Verify createDDL.sql and dropDDL.sql files appear under the project.
363378 NPE viewing jaxb project properties when schema has a null namespace Create JAXB project JAXB Project created successfully
... ... Add two schemas to the Project that have namespaces, then generate classes from them Classes were generated successfully
... ... Open project properties and go to JAXB>Schemas Verify both schemas appear without error
... ... Update the schemas to remove the namespaces and Save, re-generate the Classes and open project properties Verify only one schema appears since they both have no namespace
367122 [EclipseLink] Invalid validation for EclipseLink collection mappings Create JPA 2.0 Generic project, Create two Entities with some attributes. Project and entities created successfully
... ... Map an attribute as OneToMany and add the following and Save the project

@OneToMany(mappedBy="b") private TreeSet<Employee> City;

Verify the error 'Target entity for 'City' is not defined
... ... Create JPA 2.0 EL 2.3 project, Create two Entities from Tables Project and entites created successfully
... ... Map an attribute as OneToMany and add the following and Save the project

@OneToMay(mappedBy="b") private TreeSet<Address> managerId;

Verify the error 'Target entity for 'managerId' is not defined
... ... Change TreeSet to Collection in both the EL project and Generic project entities for the attributes Verify no errors appear for the Collection interface
... ... Change Collection to Set in both the EL project and Generic project entities for the attributes Verify no errors appear for the Set interface
... ... Change Set to List in both the EL project and Generic project entities for the attributes Verify no errors appear for the List interface
... ... Change List to Map in both the EL project and Generic project entities for the attributes Verify no errors appear for the Map interface
367593 JPA Problem: The left parenthesis is missing from the IN expression. (but there's NO right either!) Create JPA Project, create JPA Entity, expand Queries section, Click on Add Add Query dialog appears
... ... Enter a name, select Named Query from the drop down and click on OK Query is added successfully
... ... Enter the following query SELECT R FROM ApplicationRole R JOIN R.groupRoles G WHERE

G.id.organizationGroup.name IN :groups

Verify no errors appear in error log and verify the left paran error does not appear