Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

EPP/Obsolete/Logging/Testplan

< EPP‎ | Obsolete/Logging
Revision as of 05:09, 16 September 2015 by Unnamed Poltroon (Talk) (smaller updates and new testcase for ui deadlock)

Manual Release Tests

Before starting, the value org.eclipse.epp.logging.aeri.ui/debug in org.eclipse.epp.logging.aeri.ui/.options should be set to true. The application should be started with a debug configuration and tracing enabled with the plugin checked (Debug Configuration - Tracing). Please ensure that the org.eclipse.epp.logging.aeri.ui.tests-plugin is enabled. The workspace should be cleared before each test. The tests-plugin will contribute a Test Errors dropdown to the toolbar. The menu is used to trigger various test-errors which are referred as underlined in the next steps. If a testcase contains no instructions for the configuration dialog, the dialog can be skipped with 'Enable' and default settings.

Remote Data Download

  • Start with default settings
  • Wait for the Updating Error Reports Database-job to finish
  • Verify: in the runtime-workspace: .metadata/.plugins./org.eclipse.epp.logging.aeri.ui/remote-index/ exists
  • Verify: in the runtime-workspace: .metadata/.plugins./org.eclipse.epp.logging.aeri.ui/server-config.json exists
  • Restart the instance
  • Verify: remote-index folder was not changed

Configuration

  • Start with default settings
  • Log Error
  • Open configuration-dialog from popup link ('Enable')
  • In the configuration-dialog, enter a name, an email and set both anonymization-settings to checked
  • Open the details-dialog for the error in the upcoming popup ('View Details')
  • Verify: name end email of REPORT are the same as configured
  • Verify: Status and Exception messages are replaced by HIDDEN
  • Verify: second stackframe anonymized to
    at HIDDEN.HIDDEN(HIDDEN:-1)
  • Cancel sending ('Don't send')
  • Open Preferences - General - Error Reporting
  • Change name and email, deselect skip similar errors and both anonymize fields
  • Log error again and open details view
  • Verify: name end email of REPORT are the new configured values
  • Verify: No messages replaced by HIDDEN
  • Verify: second stackframe
    at any.third.party.Clazz.thirdPartyMethod(Clazz.java:42)
    is not anonymized

Error Analysis

  • Start with default settings
  • Log Verify Error
  • Verify: In the report details dialog, the comment field should contain a generated comment like:
The problematic package 'org.eclipse.egit.ui.internal.credentials' may originate in the following bundles:
  The problematic package 'org.eclipse.jgit.transport' may originate in the following bundles:
  The problematic package 'org.eclipse.recommenders.internal.snipmatch.rcp' may originate in the following bundles:
  The problematic package 'org.eclipse.jgit.lib' may originate in the following bundles:
  The problematic package 'org.eclipse.swt.widgets' may originate in the following bundles:
  org.eclipse.swt 3.104.0.v20150528-0211, from which the following bundles present on the stack trace import it:
    org.eclipse.epp.logging.aeri.ui 1.0.0.qualifier
  The problematic package 'org.eclipse.egit.core.op' may originate in the following bundles:

Disable

  • Start with default settings
  • Log Error
  • Click disable in upcoming popup
  • Log Error again
  • Verify: No popup
  • Verify: Both errors in the error log, info log for second one:
    Debug: predicate ReporterNotDisabledPredicate filtered status: Test Error

Disable by system parameter

  • Start with
    ‑Dorg.eclipse.epp.logging.aeri.ui.skipReports=true
  • Verify: No startup-progress and download job visible in progress view
  • Log Error
  • Verify: No upcoming error popups
  • Verify: Error log contains only the error but no predicate debug output

Multistatus Handling

  • Start with default settings
  • Log MS Error
  • Open the details-dialog for the error
  • Verify: 4 status objects logged, each with a different message

UI Freeze

  • Start with default settings
  • In Preferences-General-UI Responsiveness check the Detect periods of unresponsive UI checkbox and save the settings
  • Log UI Freeze
  • Open the details view
  • Verify: Multiple status objects, message of the first one has suffix [n child-status duplicates removed by Error Reporting]

CoreException Handling

  • Start with default settings
  • Log CE Error
  • Open the details view
  • Verify: First status with message: Core-Exception outer status
  • Verify: Second status with message: Core-Exception inner status [detached from CoreException of Status 'Core-Exception outer status' by Error Reporting]

No UI Deadlock

  • Start with default settings
  • Log Error and configure system, close error popup
  • Test UI Deadlock
  • Confirm first dialog ('Test lock')
  • Verify: Second dialog opens ('No lock')
  • Verify: Error popup shows up
  • Verify: Eclipse interface still responsive

logMessage / ignoreSimilar

  • Start with default settings
  • Log Error
  • Open the details view
  • Verify: logMessage and ignoreSimilar are false
  • Check and uncheck the Mark this event as 'not a bug' combobox
  • Verify: logMessage reflects the setting of the combobox (true/false)
  • Check and uncheck the Skip similar errors in the future combobox
  • Verify: ignoreSimilar reflects the setting of the combobox (true/false)

Unknown Host Exception:

  • Disable debug output for this test
  • Start with:
    -Dorg.eclipse.epp.logging.aeri.ui.serverUrl=http://unknown.test/
  • Log Error
  • Verify: Error log contains logged error but no AERI startup failure warning or predicate output.

Socket Connect Exception:

  • Disable debug output for this test
  • Start with:
    -Dorg.eclipse.epp.logging.aeri.ui.serverUrl=http://localhost:9999/
  • Log Error
  • Verify: Error log contains logged error but no AERI startup failure warning or predicate output.

Back to the top