PCM Development/Palladio Coding Session/Testing Day Release 5.2

Organizational

• Date: TBA
• Location: Virtual
  • Video-Call: TBA

Known Issues

• Palladio-Editors-Sirius:
  • There are errors in 4 test cases.
  • Some connectors present in the model are not displayed in the editor.
• Build does not work with current Maven version.
  • Tycho before version 3.0.0 is not compatible with Maven version 3.9.0 and above.
  • https://github.com/eclipse-tycho/tycho/pull/2093
• ...

Necessary preparations

• Working JIRA account
• Palladio test instance (one of the following is required)
  • Testing Day drop: https://updatesite.palladio-simulator.com/palladio-bench-product/nightly/
  • Testing Day update site
    • Eclipse Modeling Edition 2022-12
    • Palladio Nightly Update Site
      • Use Java 17
      • Select all categories/features except for deprecated features
      • Check "Contact all update sites during install to find required software"
      • Accept all licenses

Agenda

Testing of current nightly builds

• We test in Eclipse 2022-12, not in any previous versions
• We test the Sirius editors, not the GMF editors

Necessary preparations

• Working JIRA account
• Palladio test instance (one of the following is required)
  • Testing Day drop: https://updatesite.palladio-simulator.com/palladio-bench-product/nightly/
  • Testing Day update site
    • Eclipse Modeling Edition 2022-12
    • Palladio Nightly Update Site
      • Use Java 17
      • Select all categories/features except for deprecated features
      • Check "Contact all update sites during install to find required software"
      • Accept all licenses

Acceptance tests

• The following manual test cases shall be executed
  • General Overview on Test Cases
  • PALLADIO Tests
  • EDITORS Tests
  • SIMULIZAR Tests
    • If you encounter a test project which does not have a SimuLizar launch configuration yet, simply create it. There is no need for creating a monitor repository anymore.
  • RELIABILITY Tests
• Test case assignment and test execution
  • assign the test case to yourself
  • document errors in execution in the comment section
  • set the test status to succeeded or failed