Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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 09:49, 7 August 2015 by Haftsteind.gmail.com (Talk | contribs) (Manual Release Tests)

Manual Release Tests

Before starting, the value org.eclipse.epp.logging.aeri.ui/debug in org.eclipse.epp.logging.aeri.ui/.option should be set to true. The application should be started with a debug configuration and tracing enabled with the plugin checked (Debug Configuration - Tracing).

Unknown Host Exception:

  • Start with:
    -Dorg.eclipse.epp.logging.aeri.ui.serverUrl=http://unknown.test/
  • Send error event
  • Verify: Error log contains logged error but no AERI startup failure info.

Socket Connect Exception:

  • Start with:
    -Dorg.eclipse.epp.logging.aeri.ui.serverUrl=http://localhost:9999/
  • Send error event
  • Verify: Error log contains logged error but no AERI startup failure info.

Server Configuration Download

  • Start with default settings
  • Verify: in the workspace: .metadata/.plugins./org.eclipse.epp.logging.aeri.ui/server-config.json is created
  • Restart the instance
  • Verify: Configuration file was not changed

Problems Database Download

  • Start with default settings
  • Verify: in the workspace: .metadata/.plugins./org.eclipse.epp.logging.aeri.ui/remote-index is created after the first ~10 seconds
  • Restart the instance
  • Verify: remote-index folder was not changed

Error Analysis

  • Prepare the LogErrorsAction to log
    log.log(new Status(IStatus.ERROR, "org.eclipse.epp.logging.aeri", "Test Error without exception", new VerifyError("Bad type on operand stack Exception Details: Location: org/eclipse/recommenders/internal/snipmatch/rcp/EclipseGitSnippetRepository.push(Lorg/eclipse/jgit/lib/Repository;Lorg/eclipse/swt/widgets/Shell;)V @47: invokevirtual Reason: Type 'org/eclipse/egit/ui/internal/credentials/EGitCredentialsProvider' (current frame, stack[1]) is not assignable to 'org/eclipse/jgit/transport/CredentialsProvider' Current Frame: bci: @47 flags: { } locals: { 'org/eclipse/recommenders/internal/snipmatch/rcp/EclipseGitSnippetRepository', 'org/eclipse/jgit/lib/Repository', 'org/eclipse/swt/widgets/Shell', 'org/eclipse/jgit/transport/RemoteConfig', integer, 'org/eclipse/egit/core/op/PushOperation' } stack: { 'org/eclipse/egit/core/op/PushOperation', 'org/eclipse/egit/ui/internal/credentials/EGitCredentialsProvider' } Bytecode: 0x0000000: 2bb8 032b 4eb8 0316 b603 1713 0146 b903 0x0000010: 7f02 0036 04bb 016f 592b 2db6 0338 0315 0x0000020: 04b7 0315 3a05 1905 bb01 7359 b703 1db6 0x0000030: 0314 bb01 8459 2ab2 02ec 1905 b703 513a 0x0000040: 0619 062a b402 e2b6 030e 1906 bb01 8559 0x0000050: 2a2c b703 52b6 030d 1906 b603 0cb1")));
  • Start with default settings
  • Log the 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:

Configuration

  • Prepare the LogErrorsAction to log
Throwable t = new RuntimeException();
t.fillInStackTrace();
StackTraceElement[] stackTrace = t.getStackTrace();
tackTrace[1] = new StackTraceElement("any.third.party.Clazz", "thirdPartyMethod", "Clazz.java", 42);
t.setStackTrace(stackTrace);
log.log(new Status(IStatus.ERROR, "org.eclipse.epp.logging.aeri", "Test Error", t));
  • Start with default settings
  • Log the error
  • In the configuration-dialog, enter a name, an email and set both anonymization-settings to checked
  • Open the details-dialog for the error
  • 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
  • Open Preferences - General - Error Reporting
  • Change name and email, deselect skip similar errors and both anonymize fields
  • Log the 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

Back to the top