Jump to: navigation, search

Dali 3.3 M3 Release

Dali 3.3

Dali 3.3 M3 Release Manual Testing

Manual Testing for 3.3 M3 Release
Bug No. Description Test Steps Test Step Results
231872 structure view collapses when removing attribute mapping annotation Create JPA Project, Create Entity with 2 attributes like the one listed in the bug (with one attribute with the Id mapping type) JPA Project and entity are created successfully
... ... Open Entity in editor Verify it appears in JPA Structure
... ... Select the attribute that has the mapping type of Id, then remove the @Id annotation in the .java editor for the entity Verify the focus goes to the entity in the JPA Structure pane, but the structure view is not collapsed and you can still see the attributes
... ... Add @Id annotation back into the .java editor for the attribute Verify JPA Structure pane is updated, focus is on the attribute and the icon is updated to an mapping type id icon
278049 Entities from Tables wizard does not indicate that it will ad Serializable interface Create JPA project connected to database JPA project is created successfully
... ...
278838 Delete primary type and structure view stays populated Create JPA Project, Create entity with 1 attribute like the one listed in the bug Verify project and entity are created successfully
... ... Open Entity in Editor pane, then expand entity in JPA Structure Verify JPA Structure shows entity and attribute(s)
... ... Remove all contents from the .java editor except for the package name; Verify the entity and attribute(s) are removed from the JPA Structure
... ... Add the contents back into the .java editor and place the cursor onto an attribute Verify entity and attribute(s) appear in JPA Structure and focus is on the attribute
311638 persistence.xml editor remains open after JPA facet is removed from project Create Java project, R-Click and select Configure > Convert to JPA project... Modified Faceted Project dialog appears
... ... Select JPA 2.0 for the facet, Select EL 2.4.x for the platform, select the correct library and click on Finish Project is converted to JPA
... ... Open the persistence.xml in the editor persistence.xml appears in the editor and the General Tab is the focus
... ... R-click on the project and select Properties Properties for the project dialog appears
... ... Uncheck JPA for the Project facet and click on OK Verify persistence.xml is updated in the editor and the only tab that appears is the source tab
... ... R-click on the project and select Properties Properties for the project dialog appears
... ... Select JPA 2.0 for the facet, EL 2.4.x for the Platform, select the proper library and click on OK for the properties dialog Verify persistence.xml is updated in the editor and the other tabs appear.
359664 Add support for ctrl+click navigation in JPQL content assist Create JPA project, with DB connection, and create a few entities from tables Project is created successfully
... ... Open an entity in the editor and expand Queries section in JPA Details for the entity, click on Add button Add Query dialog appears
... ... Enter name (Example1) and select Named Query from drop down and click on OK Verify query is created
... ... Enter the following into the Query SELECT e FROM Employee e WHERE e.fName = 'JPQL', then hit Ctrl + and go over Employee and fName Verify they become links
... ... Click on the Employee link Verify Employee entity is opened in the editor
... ... Close the Employee entity and then go back and click on the fName > Open Declaration Verify Employee entity opens in editor and fName is selected
... ... Close the employee entity and then go back and click on the fName > Open Declared Type String.class is opened in editor
... ... Close the String.class editor, Go back and click on Add for Query Add Query dialgo appears
... ... Enter name (Example2) and select Named Query from drop down and click on OK Verify query is created
... ... Enter the following into the Query UPDATE Employee e SET e.fName = 'JPQL'

WHERE (SELECT a FROM address a) IS NOT NULL, then hit Ctrl + and go over Employee and address

Verify they become links
... ... Click on the Employee link Verify Employee entity is opened in the editor
... ... Close the Employee entity and then go back and click on the address > Open Declaration Verify Employee entity opens in editor and address is selected
... ... Close the employee entity and then go back and click on the address > Open Declared Type Address is selected in the open entity editor
... ... Close the Employee entity and go back and click on the fName > Open Declaration Verify Employee entity opens in editor and fName is selected
... ... Close the employee entity and then go back and click on the fName > Open Declared Type String.class is opened in editor
... ... Update the query to an unqualified path UPDATE Employee SET fName = 'JPQL'

WHERE (SELECT a FROM address a) IS NOT NULL

Verify employee, fName and address links all still work
... ... Close the String.class editor, Go back and click on Add for Query Add Query dialog appears
... ... Enter name (Example3) and select Named Query from drop down and click on OK Verify query is created
... ... Enter the following into the Query SELECT e FROM model.Employee e

, then hit Ctrl + and go over Employee

Verify it becomes a link
... ... Click the model.employee link Verify Employee entity is opened in editor and Employee Class name is highlighted
... ... Close Employee entity, Go back and click on Add Query Add Query dialog appears
... ... Enter name (Example4) and select Named Query from drop down and click on OK button Verify query is created
... ... Enter the following into the Query SELECT new java.lang.String(e.fName) FROM Employee e, then hit Ctrl + and hover over java.lang.String, fName and Employee Verify they become links
... ... Click on java.lang.String link Verify String.class opens in editor
... ... Close String.class editor, Go back and click on Employee link Verify Employee entity is opened in editor and Employee Class name is highlighted
... ... Close Employee entity, Go back and select fName > Open declaration Verify Employee entity opens and fName is highlighted
... ... Close Employee entity, go back and select fName > Open Declared Type Verify String.class opens in editor, String is highlighted
... ... Close String.class editor, Go back and Click on Add button Add Query dialog appears
... ... Enter name (Example5) and select Named Query from drop down and click on OK button Verify query is created
... ... Enter the following into the Query SELECT e FROM Employee e WHERE e IN (Employee, Address), then hit Ctrl + and hover over Employee (both places) and Address Verify they become links
... ... Click on either of the Employee links Verify Employee entity opens in editor
... ... Close Employee editor, Go back and click on Address link Verify Address entity is the focus and Address class is highlighted
... ... Go back and Click on Add query button Add Query dialog appears
... ... Enter name (Example6) and select Named Query from drop down and click on OK button Verify query is created
... ... Prior to entering the next Query, I had to make gender an access type mapping in the Employee entity by adding @Access(AccessType.FIELD) prior to private String gender; in the editor, the Go back and Enter the following into the Query SELECT e FROM Employee e WHERE e.gender = javax.persistence.AccessType.FIELD, then hit Ctrl + and hover over Employee, gender, javax.persistence.AccessType and FIELD Verify they become links
... ... Click on Employee link Verify Employee entity opens in editor
... ... Close Employee editor, go back and click on gender > Open Declaration Verify Employee entity opens in editor and gender is highlighed
... ... Close Employee editor, go back and click on gender > Open Declared Type Verify String.class opens in editor, String is highlighted
... ... Close String.class editor, Go back and click on javax.persistence.AccessType AccessType.class opens in editor
... ... Close AccessType.class editor, Go back and click on FIELD AccessType.class opens in editor
375467 Open eclipse with persistence.xml open and Persistence editor not displayed Create JPA EclipseLink project and open persistence.xml in the editor Persistence.xml opens in editor with 9 available tabs
... ... Close eclipse without closing the persistence.xml open in the editor and then re-launch eclipse Verify persistence.xml file is still open in the editor and all tabs still appear.
... ... R-Click on the project, select properties Properties dialog appears
... ... Remove the JPA facet (uncheck JPA) and click on OK button Verify persistence.xml still appears in the editor and the source tab is the only available tab
... ... R-Click on the project, select properties Properties dialog appears
... ... Select JPA 2.0 for the Project Facet, Generic for the platform, Click on OK button to apply the changes Verify persistence.xml is updated and contains 5 tabs (General, Connection, Options, Properties, & Source)
... ... R-Click on project and update properties to have EclipseLink for the platform and click on OK Verify persistence.xml is updated and contains 7 tabs (General, Connection, Customization, Cache, Options, Properties, & Source)
378370 unregistered listener exception removing JoinColumn from java source 1-m Download and import OneToMany project JPA project is imported successfully
... ... Open Properties for the project and add needed library and runtime Verify any and all errors are removed for project
... ... Open Employee.java in the editor, Remove @JoinColumn annotation for the OneToMany mapping Verify unregistered listener exception does not occur in Error log and a warning appears in Problems tab
... ... Add the @JoinColumn annotation back into the Employee.java editor for the OneToMany mapping Verify warning is removed from problems tab and no errors appear in error log
386416 query text area in JPA Details View should be larger Create JPA Project and JPA Entity JPA Project and Entity are created successfully
... ... Select the entity in JPA Structure, Expand Query section in JPA Details, Add a Named Query Verify the query text area is large enough for 5 lines of sql query code.
... ... Select Window > Preferences Preferences dialog opens
... ... Select Java Persistence > JPA Verify Size of JPQL text editing area in lines shows 5 for the default
... ... Change the 5 to a 7 and click on Apply, go back to the Query section in JPA Details for the Entity Verify the query text area is increased to 7 lines.
... ... Update the 7 to a 4 for the JPQL text editing area and then go back to the JPA Details query section Verify the query text area is decreased to 4 lines.
386486 org.eclipse.jpt.jpa.feature wraps "old" org.apache.commons.lang Download latest Kepler build Build is downloaded successfully
... ... Open feature.xml file from within eclipse\features\org.eclipse.jpt.jpa.feature folder Verify the org.apache.commons.lang plugin for this build has been updated to <plugin id="org.apache.commons.lang" download-size="0" install-size="0" version="2.6.0.v201205030909" unpack="false" />
... ... Also open the eclipse\plugins folder Verify the org.apache.commons.lang. jar file is the updated version that was in the feature.xml file
387420 Closing a JPA project causes a ResourceException related to the connection profile Create JPA project with a DB connection connected to a valid db and schema/catalog Project is created successfully and connected to db
... ... R-Click on the project and select Close Project Verify project is closed and no Errors appear in error log
... ... R-click on the project and select Open Project Verify project is opened without errors in error log
... ... R-click on project and select Properties Properties dialog appears
... ... Select JPA Verify Connection still contains the db connection and schema/catalog
... ... Close properties dialog, Select File > Switch Workspace > Other Workspace Launcher dialog appears
... ... Select another workspace and click on OK Verify Eclipse is relaunched and new workspace appears
... ... Select File > Switch Workspace > previous workspace Verify Eclipse is relaunched and the previous workspace appears
... ... R-Click on the JPA project and select properties Properties dialog appears
... ... Select JPA Verify that Connection still contains the db connection name
... ... Click on Connect link Verify schema/catalog appears correctly
... ... Select Project > Clean Clean dialog appears
... ... Select the JPA project and click on properties, then JPA in Properties dialog Verify default db connection, default schema/catalog are all correct and no errors appear in error log.
388602 JAXB_VALIDATION.PROPERTIES: Found 2 consecutive single quotes in text not handled by Java MessageFormat class Download latest wtp Dali build, open jaxb_validation.properties in eclipse\plugins\org.eclise.jpt.jaxb.core jar file. Verify the following 2 consective single quotes were changed to single quotes 'javax.xml.bind.JAXBElement', 'java.lang.Object', 'java.lang.String', 'type', 'type'
388603 EL_JAXB_VALIDATION.PROPERTIES: Found 2 consecutive single quotes in text not handled by Java MessageFormat class Download latest wtp Dali build, open el_jaxb_validation.properties in eclipse\plugins\org.eclise.jpt.jaxb.eclipselik.core jar file. Verify the following 2 consective single quotes were changed to single quotes 'javax.xml.bind.JAXBElement'
388604 Errors in JPA properties files Download latest wtp Dali build, open jpa_jpql_validation.properties in eclipse\plugins\org.eclipse.jpt.jpa.core jar file Verify the ABSTRACT_FROM_CLAUSE_INVALID_FIRST_IDENTIFICATION_VARIABLE_DECLARATION = '{0}' was updated with ABSTRACT_FROM_CLAUSE_INVALID_FIRST_IDENTIFICATION_VARIABLE_DECLARATION = {0}
... ... Open jpa_validation.properties in eclipse\plugins\org.eclipse.jpt.jpa.core jar file Verify VIRTUAL_ATTRIBUTE_ELEMENT_COLLECTION_CONTAINS_EMBEDDABLE_WITH_ELEMENT_COLLECTION_MAPPING =In implied attribute \"{0}"\, mapping ... was updated with \"{0}\", Also verify VIRTUAL_ATTRIBUTE_ELEMENT_COLLECTION_CONTAINS_EMBEDDABLE_WITH_PROHIBITED_RELATIONSHIP_MAPPING=In implied attribute \"{0}"\, mapping ... was updated with \"{0}\",
388609 JPA_JPQL_VALIDATION.PROPERTIES: '{0}' will be resolved to the literal text: {0} Download latest wtp Dali build, open jpa_jpql_validation.properties in eclipse\plugins\org.eclipse.persistence.jpa.jpql jar file Verify ABSTRACT_FROM_CLAUSE_INVALID_FIRST_IDENTIFICATION_VARIABLE_DECLARATION = '{0}' was updated with {0}
389943 need to update eclipselink-downloadable-libs.xml for 2.3.3 Select File > New > JPA Project New JPA Project dialog appears
... ... Enter project name, click on Next button twice, Click on Download Library button Download Library dialog appears, Verify EclipseLink 2.3.3 - Indigo & EclipseLink 2.4.1 - Juno appear in the list of libraries
390047 NullPointerException: Click Browse or hyperlink for persistence eclipselink.profiler property Create JPA Project JPA Project is created successfully
... ... Open Persistence.xml in editor and select Customization tab Verify persistence.xml is opened in editor with Customization tab as the focus
... ... Click on Profiler hyperlink Verify New Java Class dialog appears and no errors appear in error log
... ... Close the dialog Focus returns to the Customization tab for persistence.xml in editor
... ... Click on Browse button for Profiler Verify Class Selection dialog appears and no errors appear in error log
... ... Select a class and click OK button Verify the selected class appears for the Profiler and no errors appear in the error log
... ... Click on the drop down for Profiler and select Query Monitor Verify Query Monitor appears for Profiler and no errors appear
390580 reference eclipselink_oxm_2_5.xsd and copy 2.4 schema into o.e.jpt.common.eclipselink.core Download latest Dali build and open plugin.xml file from eclipse\plugins\org.eclipse.jpt.common.eclipselink.core jar file Verify the following appears in the plugin.xml file <uri name="http://www.eclipse.org/eclipselink/xsds/eclipselink_oxm_2_5.xsd" uri="platform:/plugin/org.eclipse.persistence.moxy/org/eclipse/persistence/jaxb/eclipselink_oxm_2_5.xsd" />
390871 ClassCastException: open "JAXB Classes from Schema" wizard through Quick Access Create JAXB project JAXB Project is created successfully
... ... Enter JAXB into quick access field Verify JAXB items appear
... ... Within New, select JAXB Classes from Schema - Generate JAXB classes from a schema Verify New JAXB Classes from schema dialog appears without any error
390872 NPE doing code completion in the persistence.xml file Create JPA Project and JPA Entity JPA Project and Entity are created successfully
... ... Open persistence.xml file in the editor and select source tab persistence.xml file is opened successfully
... ... Place cursor in persistence.xml source in between the persistence-unit lines, then enter <share and hit ctrl+space and enter. Verify <<shared-cache-mode></shared-cache-mode> appears in persistence.xml editor
... ... Place cursor between ...mode> put cursor here</shar... then enter N and hit ctrl+space Verify all code completion items appear in drop down and no NPE errors appear in error log
... ... Select an item from the drop down list Verify selection appaers without error
390873 AssertionFailedException: Run "Convert to JPA Project..." command w/o selecting any project Without any project selected convert in the Quick Access field Verify Convert to JPA project... does not appear
... ... Create a Java project, but keep the JPA perspective Java project is created successfully
... ... Select the Java Project and enter Convert in the quick access field Verify Convert to JPA project... appears in the list of items.
... ... Select Convert to JPA project... Verify Modify Faceted Project dialog appears and no errors appear
... ... Finish the conversion Verify the project was converted successfully without error
391017 orm.xml implied attribute validation errors appearing in the wrong location Launch Kepler Dali release, Create JPA eclipselink project and then add the JPA Entity per the bug Project and Entity are created successfully
... ... R-click on the project and select New > JPA ORM Mapping file Verify orm.xml was added and appears in editor
... ... Add the entity to the orm.xml file Verify the correct location appears in the problems file for the error In implied attribute "foo", target class is not defined It should show line 3 which is the line in the orm.xml resource
... ... Remove the orm.xml file from the project and add the eclipselink-orm.xml mapping file to the project Verify the eclipselink-orm.xml file was added and appears in the editor
... ... Add the entity to the eclipselink-orm.xml file Verify the correct location appears in the problems file for the error In implied attribute "foo", target class is not defined It should show line 3 which is the line in the eclipselink-orm.xml resource
391462 Add annotation @OrderColumn(name="testing") receive NPE error Create JPA Project JPA Project is created successfully
... ... Create an entity like the one in the bug with 2 attributes and then add one to many mapping and Order information like in the bug, Then Save the entity. Verify no NPE errors appear, an error can appear in the Problems pane but not in the Errors pane
392584 JAXB project creation gives BackingStoreException Create New JAXB project Verify no errors appear in the error log during creation of the JAXB project and verify it is created successfully