forked from adobe/brackets
-
Notifications
You must be signed in to change notification settings - Fork 0
Brackets Smoke Tests
njx edited this page May 4, 2012
·
55 revisions
EARLY DRAFT--not ready for review yet
Brackets has a pretty good unit test suite that you can run from Debug > Run Unit Tests, but that doesn't always cover issues with the overall UI and integrated functionality, or visual/layout issues that are only obvious if you're actually looking at the product. This is a set of manual tests intended to make sure we haven't broken the basic overall workflows of the product. The intention is to keep it quick--if it takes more than 5 minutes on a given platform it's too long :)
(TODO: setup step--get the sample app)
- Quit and relaunch Chrome (so it's not in debug mode).
- Launch Brackets.
- Open the main brackets source folder if it isn't open already.
- Expand some folders in the brackets project, enough that it has to scroll.
- Scroll around in the folder area. Verify that the shadows look right and there are no visual glitches.
- File > Open Folder and browse to the sample app folder. Verify that its contents look correct, and expand some folders to look inside them.
- Click on index.html. Verify that the selection in the project panel draws properly.
- Double-click on index.html. Verify that it's added to the working set and the selection draws properly.
- Resize the window. Verify that the editor resizes properly and the title bar wraps appropriately.
- Set the cursor in the tag.
- Hit Cmd-E. Verify that it shows a single body rule and that everything is laid out properly
- Click the lightning bolt in the upper right. You should get the dialog saying you need to relaunch Chrome.
- Click "Relaunch". Chrome should relaunch and open the page.
- Back in Brackets, edit the background color for the tag in the inline editor (#D90 is a nice color). Verify that the color changes in Chrome as you type. Also verify that the CSS file is added to the working set with the dirty bit.
- Hit Cmd-E. Verify that the inline editor closes.
- Put the cursor immediately after the "<a" in one of the tags in the navbar.
- Hit Cmd-E. Verify that the inline editor opens and that you see a number of rules in the list on the right.
- Scroll up and down in the outer editor. Verify that the inline editor scrolls properly with the editor.
- Resize the window. Verify that the rule list moves properly and there are no visual glitches.
- Click on a list in the rule list. Verify that the editor shows the correct rule.
TODO
- Edit > Find...
- Edit > Find in Files...
- Navigate > Quick Open...
- Project tree - appearance, handling of folders with spaces
- Working set - selection appearance
- File tree - scrolling and selection appearance
- Title bar - resize
- In-browser menu - appearance, Z-order
- Inline editor - open CSS
- Inline editor - resize/scroll behavior
- Inline editor - rule list
- Live development - launch
- Live development - edit CSS
- Find/Replace - appearance/behavior of semimodal dialog
- Find in Files - appearance/behavior of semimodal dialog, panel
- Quick Open - appearance/behavior of semimodal dialog, popup
- Quit the app and restart - project properly restored