forked from adobe/brackets
-
Notifications
You must be signed in to change notification settings - Fork 0
Brackets Server Smoke Tests
redmunds edited this page Nov 6, 2012
·
42 revisions
This set of Smoke Tests exercise Brackets code that requires a server. As with the main set of Smoke Tests, the intention is to keep it quick--if it takes more than 5 minutes to run the tests on a given platform (not including the initial setup time) then it's too long.
If you have trouble running through it or something is unclear, please post to the brackets-dev mailing list.
You will need an HTTP server for these tests. Options are:
- Setup a local wamp or mamp server.
- Use a remote server on intranet with drive mapped to local machine.
- Future: Use Brackets built-in node server with HTTP plugin
- Follow Setup steps for main set of Smoke Tests.
- Copy server-test folder (TBD) to server root.
- Launch Brackets. Verify that the Brackets "Getting Started" folder is visible in the project panel and its index.html file is opened automatically.
- File > Open Folder... and browse to server root folder.
- Verify that you see (TBD) pathRel.html, pathRoot.html, server.shtml, css and images folders.
- Select File > Project Settings... to invoke Project Settings dialog. If a Base URL is specified, delete it.
- Verify informational text is displayed in empty field. Click OK.
- Open pathRel.html, start Live Preview using File > Live Preview, and verify that page renders correctly in browser.
- Open File menu, verify Live Preview has a check mark next to it, then click it to toggle off Live Preview.
- Open pathRoot.html and click Live Preview (lightning bolt) icon on right side of menu bar.
- Verify that page is opened in browser, but with no CSS or images. Click Live Preview icon to disconnect Live Preview.
- Open server.shtml and start Live Preview. Verify Project Settings dialog is invoked with warning message indicating a Base URL is required.
- Enter the URL that maps to the project on your server (e.g. http://localhost/). Click OK.
- Verify that page renders correctly in browser.
-
open page with site-root relative paths with server
-
edit CSS
-
edit HTML, then Save