Studio Smoke Tests

From Aptana Development

  • Installation/update
    • Verify studio installation (Windows, Linux, Mac)
    • Verify studio update (Windows, Linux, Mac)
    • Verify studio installation as a plug-in to eclipse
    • Verify studio update when it is installed as a plug-in to eclipse
    • Verify studio update using archive file
    • Verify that studio is correct after each task that is listed above
  • Editors
    • Verify auto completion for all editors
    • Verify code colorization for all editors
    • Verify code formatting for all editors
    • Verify content assistance appearance for editors where it is available
    • Verify JavaScript background color with different runat values
    • Verify ON/OFF piano key
  • Outline view
    • Check outline view for HTML code
    • Check outline view for JavaScript code
    • Check outline view for mix of HTML/JavaScript
    • Check outline view for server/client/both blocks
  • File System view
    • Verify that directories/files are viewable from the view
    • Creating new directories/files from file system view
    • Delete/rename directories/files from the system view
    • Open/modify/save files from the system view
  • Project view
    • Create new project (Aptana default and Web)
    • Promoting directory to a project
    • Add/modify/remove directories/file to a project
    • Random testing of project properties
  • Preview
    • Preview HTML file from file system (IE, Firefox, Safari, iPhone)
    • Preview HTML file from Project (IE, Firefox, Safari, iPhone)
    • Preview mixed HTML/JavaScript file
    • Add/modify/refresh/delete preview
    • If page is previewed against jaxer and there is at least on server side block, make sure preview tab contains orange indicator (currently it doesn’t work on Linux)
  • FTP/SFTP/FTPS (for smoke test at least one of the connections)
    • Create FTP/SFTP/FTPS connection
    • Add/view/modify/delete directories/files from remote site
    • Upload/download files
    • Synchronize both directions
  • Debugging
    • Inserting break points
    • Verify execution suspending on break point
    • Check “Step into”, “Step Over”, “Step return” options
    • Verify break points removing
    • Verify break points disabling
    • Verify “Add Watch” and Expressions watching
    • Make sure debugging is tested with both IE and Firefox
  • Validation
    • Check validation for HTML, CSS, JavaScript
    • Check validation for PHP if it is installed
    • Verify that error indication automatically disappears after error correction
    • Verify validation entry appearance/disappearance in the validation view
  • Scripts/Snippets
    • Test few random scripts
    • Test few random snippets
  • Search
    • Test searching for file(s)
    • Test finding text
  • Servers view
    • Verify adding servers to the view
    • Verify adding/removing Jaxer/Jaxer with Apache package to the view
    • Managing servers in the view (stop, start, restart)
    • Modifying servers (built-in, external) in the view (change server parameters)
    • Make sure that built-in Jaxer has expected version
  • Tail view
    • Test adding/removing log files
    • Test output messages for built-in/external Jaxer
    • Create/modify/remove tail view colorization rules
    • Erasing log from view/disk
  • Jaxer Shell
    • Run default sample/custom against build-in and external Jaxer
    • Run default sample/custom against both Jaxers
    • Run only selected code
    • Verify history appearance
    • Clear history
  • Jaxer Activity Monitor view
    • Currently only for internal Jaxer