Dali 3.3 M5 Release

Dali 3.3

Dali 3.3 M5 Release Manual Testing

Manual Testing for 3.3 M5 Release

Bug No.	Description	Test Steps	Test Step Results
381112	NPE generating entities for table with multiple primary keys and non-foreign key relationship	Use the sql script from the bug and create two tables in any database that match the sql script	Tables are created successfully per the sql script
...	...	Create a JPA project with a connection to the database that has the created tables	JPA project is created successfully
...	...	R-Click on the project and select Generate Entities from Tables	Generate Entities from Tables dialog appears
...	...	Select the two tables PEOPLE and SOMETHING. Add an association choosing simple association, table 1 = PEOPLE table 2= SOMETHING. Add a join column PEOPLE.CODE to SOMETHING.PEOPLE_CODE. Select one-to-many. Complete the generation.	Verify the entities are created successfully and no error appears in the error log.
390616	cannot select static inner class in the JPA structure view	Create JPA project	Project is created successfully
...	...	Create the following entity @Entity public class Foo { @Id private int id; @Entity public static class Bar { @Id private int id; private String name; } }	Entity is created successfully
...	...	Select Bar in the JPA Structure pane	Verify Bar stays selected and appears in the JPA Details pane
...	...	Select Foo in the editor pane	Verify Foo is selected in the JPA Structure pane and appears in the JPA Details pane
...	...	Select the attributes under Bar in the editor pane	Verify they are selected in the JPA Structure pane and appear in the JPA Details pane
395831	Missing classes in JPA WTP 3.5 code	Download latest Dali build, Open org.eclipse.jpt.jpa.core	Verify the class org.eclipse.jpt.jpa.core.context.java.JavaMultiRelationshipMapping does not exist in the .jar file and Verify http://wiki.eclipse.org/New_Help_for_Old_Friends_VIII was updated to state that this was removed.
...	...	Open org.eclipse.jpt.jpa.core file	Verify the class org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource does not exist in the .jar file
...	...	Open the org.eclipse.jpt.common.core file	Verify the class org.eclipse.jpt.common.core.resource.xml.JpaXmlResource.class file was renamed to JptXmlResource.class
...	...	Open org.eclipse.jpt.common.utility file	Verify the class org.eclipse.jpt.common.utility.internal.CollectionTools does not exist in the .jar file
...	...	Open org.eclipse.jpt.common.ui file	Verify the class org.eclipse.jpt.common.ui.internal.widgets.PropertySheetWidgetFactory does not exist in the .jar file
...	...	Open org.eclipse.jpt.jpa.ui file	Verify he class org.eclipse.jpt.jpa.ui.internal.platform.JpaPlatformUiRegistry was renamed to InternalJpaPlatformUiManager.
396954	renaming Java Entity open in the jpa views causes a ResourceNotFoundException	Create JPA Project and Entity (Address) in JPA view	JPA project and entity are created successfully
...	...	Open Entity in editor	Entity appears in Structure and Details pane in the JPA view
...	...	In editor change the name (ex. public class Address to public class Location) and place mouse over Location	2 quick fix options appear in popup box
...	...	Select Rename Type to Address	Verify name is updated back to Address and no errors appear for project or in error log
...	...	In editor change the name (ex. public class Address to public class Location) and place mouse over Location	2 quick fix options appear in popup box
...	...	Select Rename Compilation unit to Location	Verify name is updated but errors still appear in problems pane but not error log
...	...	Update the public Address() to public Location()	Errors still remain in problem pane but not error log
...	...	Go to persistence.xml editor and update Address to Location on Source Tab and Save	Verify all errors are gone and no errors appear in Error log
...	...	R-click on the entity (Location.java) in Explorer pane and select Refactor > Rename	Rename Compilation Unit dialog appears
...	...	Change the name (ex. Address) and click on the Finish button	Verify name is updated in all locations (persistence.xml) and no errors appear in error log
397412	JAXB Schemas Properties Page: Cannot be opened	Create JAXB 2.1 project	JAXB Project is created successfully
...	...	R-Click on JAXB Project and select Properties	Properties for JAXB dialog appears
...	...	Select JAXB > Schemas	Verify Schemas page appears
397415	ClassCastException: JavaEclipseLinkManyToOneMapping cannot be cast to EclipseLinkManyToOneMapping2_0	Create JPA EclipseLink project and JPA entity with the following mappings @Id private int id; private Owner owner;	JPA project and entity are created successfully
...	...	Select owner attribute in JPA struction tab and then change the mapping to Many to One in the JPA Details tab	Verify mapping is updated and no errors appear in Error log
...	...	R-click on project, select New > EclipseLink ORM Mapping File	eclipselink-orm.xml is opened in editor
...	...	Add the created entity to the Entity Mappings, R-Click on the owner attribute in JPA Structure pane, Select Add Attribute to XML and Map...	Add Attribute dialog appears
...	...	Select Many to One from the Map as drop down and click on OK button	Verify attribute is added to eclipselink-orm.xml and no errors appear in Error Log
...	...	Click on Many to One link in JPA Details and change mapping to One to One	Verify mapping is updated to One to One and no errors appear in Error log
397454	NPE with EclipseLink converters, switching mappings in the JPA Structure view	Create JPA 2.0 EclipseLink project	Project is created successfully
...	...	Create the following JPA entity @Entity public class MyEntity { @Id private int id; @Basic private String name; }	Entity is created successfully
...	...	R-Click on the project and select New > EclipseLink ORM Mapping File	eclipselink-orm.xml opens in editor
...	...	R-Click on Entity Mappings in the JPA Structure tab	Add Class dialog appears
...	...	Select the MyEntity entity and click on OK	MyEntity is added to eclipselink-orm mapping file
...	...	Select name attribute from MyEntity in the JPA Structure and Expand Converters in the JPA Details view	Verify everything is disabled for Converters
...	...	Expand Type in the JPA Details view	Verify everything is disabled for Type
...	...	Select id attribute in JPA Structure view	Verify that id appears in JPA Details view
397800	Profiler hyperlink opens new class wizard for user defined classes	Create JPA project and JPA Class and/or Entity	JPA Project and Class and/or Entity are created successfully
...	...	Open persistence.xml in editor, select customization tab and click on Browse button for Profiler	Class Selection dialog appears
...	...	Select the JPA user created class and/or entity and click on OK button	The class and/or entity appears for Profiler
...	...	Click on Profiler link	Verify the class and/or entity appears in the editor
398218	Receive Index out of bounds error when changing mapping via Structure view	Create JPA EclipseLink project and JPA entity with the following mappings @Id private int id; private Owner owner;	JPA project and entity are created successfully
...	...	Select owner attribute in JPA struction tab and then change the mapping to Many to One in the JPA Details tab	Verify mapping is updated and no errors appear in Error log
...	...	R-click on project, select New > EclipseLink ORM Mapping File	eclipselink-orm.xml is opened in editor
...	...	Add the created entity to the Entity Mappings, R-Click on the owner attribute in JPA Structure pane, Select Add Attribute to XML and Map...	Add Attribute dialog appears
...	...	Select Many to One from the Map as drop down and click on OK button	Verify attribute is added to eclipselink-orm.xml and no errors appear in Error Log
...	...	Click on Many to One link in JPA Details and change mapping to One to One	Verify mapping is updated to One to One and no errors appear in Error log
...	...	R-Click on owner in Structure View and select Map As > Many to One	Verify mapping is updated and no errors appear in Error Log
...	...	R-Click on owner in Structure View and select Map As > One to One	Verify mapping is updated and no errors appear in Error Log