The following set of scenarios contains all those scenarios that we think are important for the overall perception of text related performance by the users. We distinguish between user's first contact, permanent user activities, and rare user activities. User's first contact describes the setup and the activities that reflect the situation when a user starts the system and pursues certain actions for the fist time during that session. Permanent user activities describes the setup and the activities that reflect the situation that the user faces when continuously working with the system. Rare user activities describe the setup and the activities that reflect the situation that the user faces only infrequently but may hamper the user's trust into the system. The numbers behind the subject indicate the importance of the scenario. E.g., typing speed is more important than speed in which the selection can semantically be expanded.

User's first contact

• Open editor (1)
• Open first text editor in the resource perspective. Measure time until the first user interaction with the newly opened editor is possible.
• Open first Java editor in the Java perspective. Measure time until the first user interaction with the newly opened editor is possible.
• Restart workbench with an open Text editor in the resource perspective.
• Restart workbench with an open Java editor in the Java perspective.
• Open Quick Outline (2)
  • Open Quick Outline for a large Java file for the first time. Measure time until the outline pops up.

Permanent user activities

• Typing (1)
  • Typing speed in the Text editor at the end of a large file.
  • Typing speed in the Java editor at the end of a large file.
  • Smart paste at the end of a large Java file in the middle of a method (default content type)
  • Autoedit when pressing enter after /** right in front of the declaration of a complex method (return value, number of args, thrown exceptions)
• Painting (1)
  • Painting annotations in text with squiggle lines when typing.
    • Measure number of repaints
  • Painting annotations in text with squiggle lines when scrolling with the mouse using the scrollbar. (mouse scrolling depends on bug 72244, current solution uses keyboard events)
    • Measure number of repaints
• Open editor (1)
  • Open Text editor for a large file after a warm-up of opening and closing the same file 10 times.
  • Open Java editor for a large file after a warm-up of opening and closing the same file 10 times.
    • Configurations
      • with/without Outliner as part of the perspective
      • with code folding enabled/disabled
    • Measure time until the first user interaction with the newly opened editor is possible.
    • Measure number of computed TextPresentations.
  • Switching between open editors
• Content assist (2)
  • Request content assist in the middle of a method. Measure time until the popup is visible.
• Save (3)
  • Save a large file in the Text editor.
  • Save a large file in the Java editor.
• Compound changes (4)
  • Format a large compilation unit including Javadoc comments.
  • Revert Text/Java editor with folding enabled/disabled.
  • Undo shifting a large compilation unit to the right.
  • Move a single line in a large compilation unit.
• Navigation (5)
  • In the Java editor, in a method of a large compilation unit, semantically expand selection.
• QuickDiff (6)
  • Measure memory consumption of Quick diff while initializing. The large compilation unit is widely changed compared to the reference.

Rare user actions

• Compound changes (4)
  • Replace all occurrences of a string in a large compilation unit.
  • Convert line delimiter of a project
  • Format a project