Dali 3.0 M6

Dali QA Testing

Dali 3.0 M6 Manual Testing

Manual Testing for 3.0 M6 Release

Bug No.	Description	Test Steps	Test Step Results
204132	Validation error needed when the same class is specified twice in the orm.xml	...	...
310464	Validation needed for element collection target class validation for unmapped non-basic types	Create a JPA, Generic project using the defaults	Project is created successfully
...	...	Create a JPA Entity, with the following public class Person { @Id private String ssn; @ElementCollection private Set<?> nickNames; }	Verify the following error appear - Target class "java.lang.Object" is not an embeddable or basic type
319736	Switch to use Iterable instead of Iterator throughout our provisional API	...	...
320032	Re-org JPT project to include JAXB component	...	...
326718	Any/choice content for generic JAXB to support validation	...	...
330503	Add EclipseLink DBWS Builder support to Dali	Create new dynamic web project using all the defaults	Dynamic web project is created successfully.
...	...
331358	JAXB Project Creation wizard - No libraries appear for download	Launch the JAXB Project wizard	New JAXB Project dialog appears
...	...	Enter required project name, leave defaults, Click on Next twice	JAXB Facet page appears
...	...	Click on the Download library button	Download Library dialog appears with the available EclipseLink libraries
332317	Enablement problem and broken warning message in New entity wizard	Create a new JPA Project, Select New>JPA Entity	New JPA Entity dialog appears
...	...	Enter the required items, Check the Add to entity mapping in XML checkbox	Verify the Browse button and text field become enabled and the mapping file label remains enabled.
...	...	Click on the Browse button	Verify Mapping File dialog appears
...	...	Click on the New button	New Mapping File dialog appears
...	...	Click on the Advanced button option, check the Link to file in file system checkbox	Verify the text field, Browse button and Variables button become enabled.
...	...	Click on the Browse button, select an .xml file and click Open.	Verify the selected file (with the path) appear in the text field
...	...	Click on the Finish, and then click OK to choose the mapping XML file	Verify the selected file appears in the Mapping File text field without error.
332827	Store the project properties in the .settings file	Create JPA 2.0 generic 2.0 project	Project is created successfully
...	...	R-Click and select JPA Tools > Open Diagram	Diagram editor opens
...	...	R-Click on the project and select Properties	Properties dialog appears
...	...	Expand JPA, select JPA Diagram Editor	Verify the following defaults, Folder for diagrams: diagrams, Default Java: org.persistence, Default table: T_, Editing checkbox checked, Field-based radio button is selected, java.util.collection radion button selected.
...	...	Change the Default table name prefix, select the java.util.set radio button and click on OK	Verify the org.eclipse.jpt.jpadiagrameditor.ui file is updated under the workspace/project_name/.settings folder
333664	Icons for all of the JAXB attribute mapping are needed	...	...
333728	Inconsistent entity names in the diagram and the java sources	...	...
333730	Compilation error when creating entity attributes of type java.sql.Date and java.util.Date	...	...
333884	EclipseLink JPA downloaded libraries do not work for JAXB	Select New>Other>JAXB>JAXB Project, and click on Next button	New JAXB Project dialog appears
...	...	Enter a name and click on Next twice, Select user library from the Type drop down	Message appears stating - At least one user library must be selected
...	...	Click on the Manage libraries button	Preference library dialog appears
...	...	Add the 2.3 EclispeLink jar files from the MOXY folder, then click on OK, check the checkbox for the library	Verify the message is removed and the Finish button is enabled.
334142	Support visual Definition and Editing of MappedSuperclass	...	...
334144	Support visual Definition and Editing of Embeddable	...	...
334149	Collection Type should be user specifiable	...	...
334152	Refactoring collection type drops Generic from definition and deletes from diagram	...	...
334166	Diagram location in project should not be a src folder	Create a JPA 1.0 Generic 1.0 project	Project is created successfully
...	...	R-Click on the Project, Select JPA Tools>Open Diagram	Diagram opens and verify diagrams folder appears directly under the project folder and the diagram .xmi file appears within the diagrams folder
334168	Don't specify entity name when same as default	...	...
334536	Diagram editor project property page not available for JPA 2.0 projects	...	...
335176	When diagram folder name changed the diagram should be renamed	Create a JPA 1.0, Generic 1.0 project with defaults	Project is created successfully
...	...	R-Click on the newly created project, Select JPA Tools> Open Diagram	JPA Diagram editor opens successfully
...	...	Create a JPA 2.0, EL 2.1.x project with details	Project is created successfully
...	...	R-Click on the newly created JPA2.0 project and Select JPA > Tools >Open Diagram	JPA Support dialog appears stating - JPA Diagram Editor supports JPA 1.0 only. When you use it with JPA 2.0 enabled projects you should visualize JPA 1.0 compliant entities only. Otherwise, the editor behavior will become erratic.
...	...	Click on the OK button	Diagram editor opens successfully
...	...	Open Explorer and go to the workspace folder, open the project folder	Verify the diagrams folder appears directly under the project folder and then the .xmi file appears within the diagrams folder
335343	Convert value lost after changing the focus area	Create a JPA 2.0, EL 2.2.x project with some entities (Address, Employee, Phone)	Project is created successfully
...	...	Open a .java file in the editor (Employee.java), Select an attribute (version), go to the JPA Details section, expand Type, Click on Converted radio button	@Convert appears in the .java editor for the attribute
...	...	Expand Define Converter in JPA Details, click on Custom radio button, Enter testing for the name	@Converter(name = "testing") appears in the .java editor for the attribute
...	...	Select testing from the converter name drop down in the JPA Details	Verify testing appears for @Convert in .java editor for the attribute
...	...	Change the focus from the attribute (click on another attribute)	Verify the @Convert("testing") still remains for the attribute in the .java editor and it still appears in the JPA Details.
...	...	Remove the @Convert and @Converter lines from the editor, add the class to the eclipselinkorm.xml file	Class is added successfully
...	...	Select the attribute and add the attribute to the xml.	Attribute is added to the eclipselinkorm.xml
...	...	Go to the JPA Details section, expand Type, Click on Converted radio button	<convert></convert> appears in the .xml editor (source tab) for the attribute
...	...	Expand Define Converter in JPA Details, click on Custom radio button, Enter testing for the name	<converter name="testing"/> appears in the .java editor for the attribute
...	...	Select testing from the converter name drop down in the JPA Details	Verify testing appears for <convert> in .xml editor for the attribute
...	...	Change the focus from the attribute (click on another attribute)	Verify the <convert>testing</convert> still remains for the attribute in the .java editor and it still appears in the JPA Details.
335594	CCE adding NamedQuery to EclipseLink 2.0 project	Create JPA 2.0 EL 2.0 project, add an entity, and select the entity so it appears in JPA details	Project is created successfully without error.
...	...	Expand Queries section, Click on the Add button	Add Query dialog appears
...	...	Enter a name (Testing), Select NAmed Query for the type, Click on Ok button.	Annotation appears in the .java editor without errors.
...	...	Add another query with the type of Named Native Query.	Verify the annotation appears and not errors appear
...	...	Repeat the test for a JPA 2.0, EL 2.0 and EL 2.1 projects	Verify no errors appear
335667	FileNotFoundException in JPA Diagram editor	...	...
335697	Add support for default XmlElement attribute mappings	...	...
335731	XmlElement, XmlAttribute name/namespace validation and code-assist	...	...
335795	Add new DBWS dependicies to WTP build	...	...
336006	Validation needed for temporal type mappings	...	...
336009	EclipseLink enumerated element is automatically added for id mapping	...	...
336161	XmlElementWrapper validation and code-assit	...	...
336172	Inconsistent error message	Create a JPA 2.0, Generic 2.0 project.	Project is created successfully
...	...	R-Click on the project and select JPA>Create Tables from entities	Verify dialog appears with message stating - Generate Tables from Entities from tables is not supported by the Generic Platform.
336259	Validation for XmlList	...	...
336296	Validation for virtual attributes does not currently work	...	...
336388	Context model support for @XmlTransient on a class	...	...
336540	Update branding plug-ins after recent project re-org	Download the latest wtp which contains the latest Dali build and extract the files	The build is downloaded successfully and extracted.
...	...	Open the eclipse\plugins folder	Verify the org.eclipse.jpt.jpa.eclipselink.branding .jar file exists
...	...	Open the org.eclipse.jpt.jpa.eclipselink.branding .jar file	Verify the components.xml file exists
...	...	Go back to the plugins directory	Verify org.eclipse.jpt.jpa.branding .jpa also exists.
336548	Reorganize docs plug-ins to split into jpa and jaxb	...	...
336549	Update feature plug-ins	Download the latest wtp which contains the latest Dali build and extract the files	The build is downloaded successfully and extracted.
...	...	Open the eclipse\features folder	Verify the org.eclipse.jpt.jpa.eclipselink.feature_3.3.0 file exists, verify org.eclipse.jpt.jpa.feature_3.3.0 file exisits
336553	Cannot add the JPA facet to an imported project that is not in the workspace	...	...
337171	Feature names in feature.xml files need to be updated to match recent feature plug-in renames	Download the latest wtp which contains the latest Dali build and extract the files	The build is downloaded successfully and extracted.
...	...	Open the eclipse\features folder	Verify the org.eclipse.jpt.jpa.feature_3.3.0 folder exists
...	...	Expand the org.eclipse.jpt.jpa.feature_3.3.0 folder and open the feature.properties file	Verify Dali Java Persistence Tools - JPA Support appears for the featureName
...	...	Expand the org.eclipse.jpt.jpa.feature_3.3.0 folder and open the feature.xml file	Verify the id's have been updated from org.eclipse.jpa to org.eclipse.jpt.jpa
337736	Integrate JPA Diagram Editor wiki documentation into the WTP Dali project's web site	Go to WTP Dali's project web site http://www.eclipse.org/webtools/dali/	WTP Dali Java Persistence Tools site appears
...	...	Under the About section click on the About JPA Diagram Editor Project link	Verify you are taken to the JPA Diagram Editor Project
...	...	Go back to the wtp/Dali page and under the Discover Dali section click on the Getting Started with JPA Editor link	Verify you are taken to the JPA Diagram Editor Project Tutorial
...	...	Go back to the wtp/Dali page and under the Demo section click on JPA Diagram Editor	New window is launched and the demo is started in youtube.
...	...	Close the demo window and return to the wtp/Dali page and under the Backgroup Info section click on the Original JPA Diagram Editor Project Proposal link	Verify you are taken to the WTP/JPA Diagram Editor/Proposal
338945	IllegalStateException in structure view when deleting a class	Create a JPA project, Create an Entity	Project with entity is created successfully
...	...	Open the entity in the editor and Open the JPA View so the JPA Structure panel appears	Entity appears in the editor and the JPA Structure pane
...	...	In the Project Explorer pane expand the entity and R-Click on the Class and select Delete	Confirm Delete dialog appears
...	...	Click on the OK button to delete the class	Verify the class is deleted without errors
339098	EclipseLink JAXB naming in UI	Download the latest wtp/Dali build, expand the features folder, expand the org.eclipse.jpt.jaxb.eclipselink.feature folder and open the feature.properties file	Verify Dali Java Persistence Tools - EclipseLink JAXB Support appears in the file
...	...	Select File>New>Other	New Dialog appears
...	...	Select JAXB>JAXB Project and click on NEXT	New JAXB Project dialog appears with cursor defaulting in Project name
...	...	Enter a valid name, leave the defaults, click on Next twice	Verify EclipseLink 2.2.x and EclipseLink 2.3.x appear in the Platform drop down
339428	NPE Setting attribute overrides to an embedded attribute of EclipseLink 2.0 project	Create JPA Project selecting the defaults and a Oracle DB connection	Project is created successfully
...	...	Generate Entities from Tables for Address, Emp and Phone	Entities are created
...	...	Open Employee.java entity editor	Employee information appears in JPA details tab
...	...	Select endDate attribute and change it's mapping to Embedded	Verify Override attributes text box appears
...	...	Add the following to the employee.java editor for the end_date attribute @AttributeOverride(name = "endDate", column = @Column(name = "endDate", table = "Employee"))	Verify Override attributes in JPA details contains endDate(Attribute Override)
...	...	Select the endDate in Attribute Overrides text field in JPA Details	Verify checkbox appears for override default and is checked
...	...	Uncheck override attributes checkbox	Verify the endDate(Attribute Override) is removed from the text field in JPA editor and from the employee.java editor for endDate
...	...	Add @AttributeOverride(name = "endDate", column = @Column(name = "endDate", table = "Employee")) back to employee.java for endDate and then select it in the JPA Details view	Verify checkbox appears for override default and is checked and information appears in JPA Details
339434	CCE adding a Java Entity to a mapping file	Create JPA Project selecting the defaults and a Oracle DB connection	Project is created successfully
...	...	Generate Entities from Tables for Address, Emp and Phone	Entities are created
...	...	Open Employee.java entity editor	Employee information appears in JPA details tab
...	...	Expand the Secondary Table section and click on the Add button	Add Secondary Table dialog appears
...	...	Select Salary from the drop down and click on the OK button.	Dialog closes and @SecondaryTable(name = "SALARY") appears in .java editor
...	...	R-Click on the project and select New>JPA ORM Mapping file	New Mapping File dialog appears with orm.xml for the File name
...	...	Click on Finish	orm.xml file is created successfully and opens in editor without errors
...	...	Add the Employee class to the orm.xml mapping file	Verify Employee class is added and no errors appear