UserTesting

User testing

Packages

• Simple add remove
  • In the tree view, in the context menu of a directory click 'Add to Haskell tools'
  • A notification should appear and the synch icon should mark the folder.
  • If the folder had been already registered, the context menu item should be 'Remove' and should remove the folder from Haskell tools
• Multiple add remove
  • If multiple folders are selected, adding and removing should toggle all folders.
• If the server is killed or restarted, the folders should be loaded again

Refactoring

• Try a simple refactoring that does not receive any input (for example generate signature)
• Try a refactoring that requires a name (rename definition)

Undo refactorings

• Initially the menu item should be disabled
• If a refactoring is performed it should be enabled
• If the refactoring is undone, the original source should be restored, both in opened files and in other files.
• If multiple refactorings where done in sequence, they can all be undone.
• If a file is manually edited and saved, all previous refactorings are permanent.

Tree view operations

• Add file should send the added file to the haskell tools engine
• Delete should send the remove notification to the engine
• Rename should do both the adding and the removing
• Duplicate should work like Add

Marker handling

• Simple error marker
  • Start the server, register a package
  • Create a file with a simple haskell error
  • Save the file
  • Check that the error marker appear in the file and the location of the error is highlighted
  • Check that the markers appear on the tree view on all containing folders
• Simple error marker: remove
  • Start the server, register a package
  • Create a file with a simple haskell error
  • Correct that error
  • All error markers and highlights should be removed
• Multiple editors: new error
  • Start the server, register a package
  • Create a file with a correct module
  • Right click in the editor, split right
  • Create a mistake in one of the files
  • Save
  • The marker should appear in both editors
• Multiple editors: correction
  • Start the server, register a package
  • Create a file with a simple haskell error
  • Right click in the editor, split right
  • Correct the mistake in one of the editors
  • The marker in the other should disappear
• Error marker on tree view: keep if one file contains
  • Start the server, register a package
  • Create two haskell files with a simple haskell error
  • Correct one of them
  • The folder that contains the files should still have the error marker

Tooltips

• Simple tooltip
  • Start the server, register a package
  • Create a file with a simple haskell error
  • Save the file
  • Hover over the error marker in the editor
  • The tooltip should appear
  • Move the mouse out of an error (and the tooltip)
  • The tooltip should disappear
  • Move the mouse over the marker again
  • The tooltip should appear again
• Multiple Tooltips
  • Start the server, register a package
  • Create a file with two simple haskell errors
  • Save the file
  • Hover over the error marker in the editor
  • Move the mouse over the other one
  • The previous marker should immediately disappear
• Tooltips in multiple views
  • Start the server, register a package
  • Create a file with a simple haskell error
  • Save the file
  • Split the view of that file
  • The tooltip should show and disappear normally in both editors