Labs/Bespin/TestPlan

From MozillaWiki
< Labs‎ | Bespin
Jump to: navigation, search

Test Plan

The following test plan is designed to exercise any potential area of regression we care about. Feel free to add to it and please cite Bugzilla bugs where helpful to illustrate a past regression.

  • Create a new account.
    • Click through each of the four "Welcome to Bespin" image links and make sure they work
    • Click "Don't Show This Again", log out, then log back in and verify the "Welcome to Bespin" thingie doesn't show up
    • Verify that the initial file is "SampleProject - readme.txt" and that the contents seem sensible

Basic Editor Features

  • Edit the document, verifying that:
    • The cursor is inserted where the mouse is clicked
    • Typing ASCII characters works fine
    • The dash in-between the project name and file name turns into a circle once the first modifications are made, indicating that there are unsaved changes.** Pressing enter in-between characters in a line property splits the line
    • Pressing enter at the end of the line properly creates a new line beneath
    • Pressing enter at the beginning of the line moves the current line down
    • Selecting text and typing clears the selected text and inserts the typing character(s)
    • Tab inserts spaces when not in tab mode
    • Tab inserts tabs when in tab mode
    • Tabs seem to behave properly whilst in tab mode
    • Copy and paste works
    • Double-clicking on a word selects the whole word
      • Punctuation characters are omitted from the selection
    • Triple-clicking on a word selects the entire line
    • Holding the mouse button down allows you to visually adjust the text selection range

Performance

  • Mash on the keys as fast as you can and verify that Bespin keeps up
  • Select a chunk of text and copy/paste it into the editor over and over again to produce a 50,000 line file; verify that Bespin keeps up
  • Mash on the keys again and verify speed

Basic Project Features

  • Create a new project named "foo"
  • Create a new file into the project named "bar.txt"
  • Save the file
    • Verify that the project and file are properly displayed in the file browser
  • Create a file named "files/bar2.txt" and verify it is present in the file browser
  • Verify you can open both files via the file browser

SVN Support

  • Use "vcs checkout" to checkout a read-only SVN project, such as http://jsworker.googlecode.com/svn/trunk/
    • Verify that the checkout completes
    • Verify that all the files were in fact checked out via the file browser
    • Open some of the files and verify they look right

HG Support

Deploy

Collaboration