Skip to content

EPP Modeling testing #369

@rschnekenbu

Description

@rschnekenbu

Steps I have been running these last years to test Eclipse Modeling Package:

  • Checkout the documentation tab opens and do not display missing entries or invalid entries (EMF, OCL, etc)
  • Open the workspace from last version to test that I can still open previous version
  • Create a new Ecore modeling project
    • create a series of EClasses (abstract or not) with ecore diagram editor
    • create some links between the classes (super-type and reference)
    • create some attributes within the classes (in abstract super classes and the concrete ones). Check here that the parsers for text edition work fine. Good spot here to test guava inconsistencies, proved to be a good test when this dependency was failing) by:
      • create a EString typed attribute
      • create a EInt one
      • create an attribute with wrong type
  • Generate the code for the given ecore model for model, edit, editor and tests
  • Create a copy of the .ecore model file.
  • Change some attributes or links
  • Regenerate and assess the new code
  • Compare the 2 ecore files to check for EMF Compare feature. Check that the diff opens and that we can see the differences (for example, the rename of an attribute or a deletion)
  • Run a debug session and create new model compliant with this ecore model
  • Check again the error log

I used also to import the OCL examples and test them sometimes. I have not done this for quite a while.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions