Labs/Bespin/Testing/TestPlan
From MozillaWiki
Test Plan
To start with, this is a set of tests to run to check if Bespin is running OK after a change:
Simple Loading
- Start up your server (e.g. paver start)
- Access home page (e.g. http://localhost:8080/)
- Make sure to logout
- Re-login
- Access Dashboard
- Check the various panes, move them around, and see if there are errors in the console/Firebug
- Access Editor
- Click on a file from the dashboard so the editor is opened
- Make sure the project label looks ok in the top left
- Make sure that content is showing up in the editor
- Check for errors in the console/Firebug
- Check Editor Component
- Visit http://localhost:8080/tests/editor/singleeditor.html
- Make sure that the editor component loads up and content is shown, syntax highlighted
- Change a setting in the debug info below
Dashboard Details
- Fill out
- Command line
- Type help and see which commands are shown and try some
Editor Details
- Responsiveness
- Hammer on the keyboard and see if it keeps up
- Make sure to load up a large file (select all and paste a lot) and repeat the hammer
- Hold down an arrow key and record the time it takes to scroll through a 100 line file
- NOTE: We want to setup an automated test that will time the paint() method and aggregate it so we can see how it is affected.
- Settings
- set strictlines off: check to see if you can get into virtual space
- set tabmode on: check tabs
- set tabarrow on: this will help you see
- Command line
- Type help and see if you get commands listed
- status