Dali 3.2 M7

From Eclipsepedia

Jump to: navigation, search

Dali 3.2

Dali 3.2 M7 Release Manual Testing

Manual Testing for 3.2 M7 Release
Bug No. Description Test Steps Test Step Results
322567 JAXB schema generation should open the generated schema Create JAXB project Project is created successfully
... ... Create two Classes(FooA & FooB) in the JAXB Project Classes are created successfully
... ... R-Click on the project and select New>Other New dialog appears
... ... Select JAXB > Schema from JAXB classes and click on Next button, choose the project where classes exist and click on finish button Verify the .xsd schema is created and opened in the editor.
342171 [API] Mapping One to Many - chooses override in Details and receive out-of-bounds error Create JPA 2.0, generic 2.0 project, Create an entity with two attributes Project and entity are created successfully
... ... Map 1st atribute as the Id, Map 2nd as one-to-many and Save Attributes are updated successfully
... ... In details section for 2nd attribute click on join columns override default

checkbox

Verify no errors appear in the error log
... ... Select Entity in JPA Structure, Expand Inheritance in JPA Details, Check the override default checkbox in the Primary Key Join Columns section Verify no errors appear in the error log
... ... Expand Secondary Tables, Add a Secondary Table, Select the table, Check the Override default checkbox in the Primary Key Join Columns Verify no errors appear in the error log
... ... Create JPA ORM Mapping File, Add the Entity to the orm mapping file Verify Entity is added to mapping file successfully
... ... Expand Secondary Table in JPA Details for Entity, Check the Define in XML check box Verify no errors appear in the error log
... ... Highlight the secondary table, uncheck and recheck the Override default checkbox in the Primary Key Join Columns. Verify no errors appear in the error log.
347969 Default discriminator value not displayed correctly Create JPA Project and JPA Entity named Foo Project and Entity named Foo are created successfully
... ... Create JPA Entity Foo1 and extend Foo for this entity Entity is created successfully
... ... Expand Inheritance for Foo1 in JPA Details Verify it shows Default (Foo1) for the Descriptor Value
... ... Expand Inheritance for Foo in JPA Details Verify it shows Default (Foo) for the Descriptor Value
... ... Create JPA Entity Foo2 and extend Foo for this entity Entity is created successfully
... ... Expand Inheritance for Foo2 in JPA Details Verify it shows Default (Foo2) for the Descriptor Value
... ... Look at the other Descriptor Values for Foo and Foo1 Verify they are still Default (Foo) and Default (Foo1)
... ... Change the Descriptor Value for Foo to Foo2 Verify the Descriptor Value for Foo1 is still Foo1
363080 refactoring class reference in xml from the default package causes exception Create JPA Project EclipseLink Project, Create JPA Entity in Default package named Foo Project and entity are created successfully
... ... R-Click on project, Select New > EclipseLink ORM mapping file EclipseLink orm mapping file is created successfully
... ... Enter the following into the EclipseLink orm mapping file and save the file
    <entity class="Foo">
         <customizer class="MyCustomizer"/>
    </entity>
Project is updated successfully
... ... R-Click on the Foo entity, select Refactor>Move Nove dialog appears
... ... Click on Create Package button New Java Package dialog appears
... ... Enter Model for the Name and click on Finish button Verify the model package appears in move dialog and is highlighted
... ... Click on the OK button Verify the EclipseLink-orm.xml is updated to show model.Foo for the entity class and no errors appear
... ... Move the entity back to the default package Verify no errors appears and the eclipselink-orm.xml is updated correctly
371112 EclipseLink converter validation appearing on xml, when converter defined in java Create JPA EclipseLink Project, Create Employee entity with one key attribute (id) JPA Project and Entity are created successfully
... ... Add the following converter annotation to the entity right after the @ID annotation and Save
       @Converter(name = "asdf", converterClass=FooConverter.class)
Converter is added successfully
... ... Add EclipseLink-orm.xml mapping file to the project, Add Employee Entity to the EclipseLink-orm.xml Verify Entity is added successfully to the EclipseLink-orm.xml
... ... Add FooConverter Interface to the JPA project and Save Verify the following error appears in the Problems pane for the Employee.java entity The converter class "FooConverter" does not implement the org.eclipse.persistence.mappings.converters.Converter interface
374379 Once the severity is changed, JPQL queries are no longer validated Create a JPA Project and JPA entity Project and entity are created successfully
... ... Expand Queries for the JPA Entity in the Details pane and click on Add button Add Query dialog appears
... ... Enter 'Testing' for the Name, select Named Query from the Type drop down and click on OK button Error appears stating you need a query
... ... Enter an invalid Query and Save (ex. Select e from ) Error appears for the query in the Problems pane
... ... Select Window > Preferences Preferences dialog appears in the Problems pane
... ... Expand Java Persistence > JPA, select Errors/Warnings, Expand Queries and generators, Select Warning for the Invalid or Incomplete JPQL Queries and then Click on OK button Verify the error for the Query is moved to the Warning section in the problems pane
... ... Expand Java Persistence > JPA, select Errors/Warnings, Expand Queries and generators, Select Info for the Invalid or Incomplete JPQL Queries and then Click on OK button Verify the warning for the Query is moved to the Info section in the problems pane
... ... Expand Java Persistence > JPA, select Errors/Warnings, Expand Queries and generators, Select Ignore for the Invalid or Incomplete JPQL Queries and then Click on OK button Verify the info messages are removed for the query
... ... Expand Java Persistence > JPA, select Errors/Warnings, Expand Queries and generators, Select Error for the Invalid or Incomplete JPQL Queries and then Click on OK button Verify the error for the Query appears in the problems pane
374658 In Package Explorer CCE converting java queries/generators/converters to XML Create JPA 1.0 project using the defaults JPA 1.0 project is created successfully
... ... Change from JPA perspective to Java perspective Verify Project Explorer becomes Package Explorer
... ... R-Click on the JPA 1.0 project and select JPA Tools > Move to XML > Java Queries ... Verify no errors appear in Error log and JPA Metadata Conversion dialog appears
... ... Cancel the JPA Metadata Conversion dialog Dialog closes and no errors appear
... ... R-Click on the JPA 1.0 project and select JPA > Tools > Move to XML > Java Generators... Verify no erros appear in Error Log and JPA Metadata Conversion dialog appears
374661 [EclipseLink] Generate Dynamic entities requires JPA project selection if in a view other than Project Explorer Create 4 projects, two JPA EclipseLink with DB connection, two JPA Generic with DB Connection All projects are created successfully
... ... R-Click on the JPA Generic Projects Verify Generic Dynamic Entities from Tables option does not appear within JPA Tools
... ... R-Click on a JPA EclipseLink Project Verify Generic Dynamic Entities from Tables exists within the JPA Tools
... ... Select JPA Tools > Generate Dyanamic Entities from Tables Verify Generate Dynamic Entites dialog appears with the Select Tables page appearing
... ... Click on Cancel Dialog closes and nothing is generated
... ... Deselect all project and then Select New > Other New dialog appears with Select a wizard page
... ... Select JPA > EclipseLink > Dynamic Entites from Tables and click on Next JPA Project Selection page appears and verify only the JPA EclipseLink projects appear in the list, no JPA Generic projects appear in the list.
374825 infinite update if orm.xml contains incorrect reference to a class in the default package Create JPA project and JPA Entity (in the default package) Project and Entity are created successfully
... ... R-click on the Project and create a new orm.xml mapping file Mapping file is created successfully
... ... Add the entity to the orm.xml mapping file and put a . (period) before the entity name
    Ex. <entity class=".Foo"></entity>
Verify the project is updated and does not stay in an update loop (This can be viewed at the bottom right of the Eclipse app)
374831 NullPointerException: Make changes to target entity of ManyToOne mapping on Generic platform Create JPA Generic project JPA Project is created successfully
... ... Create two entities as follows and Save
   @Entity
   public class Foo2 implements Serializable {
      private statie final long serialVersionUID = 1L;
   
    @Id
    private int id;
   
    @ManyToOne
    private Foo foo;
   }
    @Entity 
    public class Foo implements Serializable {
        private static final long serialVersionUID = 1L;
    @Id
    private int id;
    }
Entities are saved successfully
... ... Make any change to the Foo entity such as click on the Cacheable checkbox in JPA Details tab Verify no errors appear in Error Log and the Foo entity is updated
375216 JAXB Schema generation fails if classes are in default package Create JAXB project and create two classes in a default package Project and classes are created successfully
... ... R-Click on the project and select New > Other > JAXB > Schema from JAXB Classes and click on Next button twice Select Classes to Include page appears
... ... Select the project checkbox and then click on Finish button Verify schema is created and no errors appear
375415 NPEs in JAXB validation Create JAXB Project with EclipseLink 2.1.x JAXB project is created successfully
... ... R-Click on project select New > Other > JAXB > JAXB Classes from schema New JAXB Classes from Schema dialog appears
... ... Select JAXB project and click on NExt button, Select XML Category Entry, Select http://java.sun.com.xml/ns/persistence/orm_2_0.xsd Click on Next button Generate Classes from Schema: persistence 2_0.xsd page appears
... ... Enter a package name, click on Finish button Generating JAXB Classes dialog appears
... ... Click on YES button Verify no NPE errors appear
... ... R-Click on the package and select Validate Verify Validation Results dialog appears and has no errors
375669 using Make Persistent action takes way too long for many entities Create a JPA project with 100 classes in a package (model) Project and classes are created successfully
... ... R-Click on package (model) and select JPA Tools > Make Persistent Make Persistent dialog appears with all 100 classes appearing in list
... ... Make sure Annotate in Java radio button is selected and List in Persistence.xml checkbox is checked and click on the Finish button Verify Progress information dialog appears and it only takes about 10 seconds to make all 100 classes persistent. Also verify project is updated and classes are now entities and they all appear in the persistence.xml file All 100 entities should contain errors since no primary key is defined
... ... Create another JPA Project with 250 classes in a package (model) Project and classes are created successfully
... ... R-Click on package (model) and select JPA Tools > Make Persistent Make Persistent dialog appears with all 250 classes appearing in list
... ... Make sure Annotate in Java radio button is selected and List in Persistence.xml checkbox is checked and click on the Finish button Verify Progress information dialog appears and it only takes about 20 seconds to make all 250 classes persistent. Also verify project is updated and classes are now entities and they all appear in the persistence.xml file All 250 entities should contain errors since no primary key is defined
... ... Create another JPA Project with 250 classes in package (model) Project and classes are created successfully
... ... R-Click on package (model) and select JPA Tools > Make Persistent Make Persistent dialog appears with all 250 classes appearing in list
... ... Select Add to XML mapping file radio button Mapping file does not exist error appears and Finish button is disabled
... ... Click on Browse button, Click on New button, Leave defaults and click on Finish button, then click on OK button Error is removed in the Make Persistent dialog
... ... Click on the Finish button in Make Persistent dialog Verify Progress information dialog appears and it only takes about 20 seconds to add all 250 classes to the orm.xml file as entities. All 250 entities should contain errors since no primary key is defined
375670 NPE with 1.0 orm.xml one-to-many code completion Create JPA 1.0 Generic 1.0 project JPA 1.0 project is created successfully
... ... Create New JPA ORM Mapping File ORM mapping file is created and opened in editor
... ... Enter the xml code from the bug into the orm.xml file and use ctrl + space after you enter the first few characters for code completion The orm.xml file is updated without error. Verify no errors appear when you use code complete for EMPLOYEE_GENERATED_TABLE after you enter generator=""
375841 root structure node leak when removing a class ref from the persistence.xml source Create JPA project, Create JPA Class Project and class are created successfully
... ... Open persistence.xml and Add the class to the managed classes Verify the following appears in the Source Tab for the persistence.xml
    	<persistence-unit name="testing">
            <class>model.ClassA</class>
       </persistence-unit>
... ... Remove the <class>model.ClassA</class> from the source file and save Verify the class is removed from the managed classes in the General Tab
... ... R-Click on the Class and select JPA Tools > Make Persistent Verify it appears in the Make Persistent dialog
377707 Dynamic Entity wizard defaults all eclipselink orm files to version 2.4 Create JPA 2.0 EL 2.3 project with a DB connection JPA project is created successfully
... ... R-click on the project, select JPA Tools > Generate Dynamic Entities from Tables Generate Dynamic Entities dialog appears
... ... Select a Table or two, leave all other defaults and click on Finish button Verify eclipselink-orm.xml file is created and opened in the editor. Verify the version shows 2.3 since it was created in a 2.3 project.
... ... Repeat for a JPA EL2.2 project Verify the eclipselink-orm.xml file is created and shows 2.2 since it was created in a 2.2 project
... ... Repeat for a JPA EL2.4 project Verify the eclipselink-orm.xml file is created and shows 2.4 since it was created in a 2.4 project
377809 JAXB menu appears in right-click of a JPA project package Verify no JAXB projects currently exist and Create a JPA 2.0 Project and then create a package within the project JPA project and package are created successfully
... ... R-Click on the package Verify that the JAXB menu item does not appear in the list of menu items