Ruby Basic Acceptance Tests

From Aptana Development

Contents

Installation

  1. Install the plugin into Aptana standalone using the Aptana Start page.
  2. Install the plugin into Aptana standalone using the plugin manager inside Aptana.
  3. Install the plugin into Eclipse 3.2 using the update site
  4. Install the plugin into Eclipse 3.3 using the update site

Rails Project Creation

  1. Right-click in Rails Navigator and choose New > Rails project.
  2. Generate a project named "test" with default settings
  3. Confirm that project is created, and console creates linked list of files generated

Ruby Editor

  1. Choose the C+ "New Ruby Class" wizard icon from toolbar. (Must be in Ruby perspective)
  2. Generate class named "Test".
  3. Verify test.rb is created and opened in Ruby Editor; and that Test class stub is generated.

Open Type Dialog / Code Resolution

  1. Hit Ctrl+Shift+T to open the Open Type dialog
  2. Enter "SE" and confirm that CamelCase results like "StandardError" are shown.
  3. Enter "ModuleDef", select it in the list and confirm that the full name shown is "ModuleDef - XSD::CodeGen"
  4. Double click the listing and confirm that the source file is opened in a Ruby editor and the class definition for ModuleDef is highlighted.
  5. Highlight "GenSupport" on the next line, hit F3 and confirm that an editor is opened on the module GenSupport.

RHTML Editor

  1. Open generated .rhtml file and verify that it is colored properly.

YML Editor

  1. Open generated database.yml file and verify that it is colored properly.
  2. Type a YAML document with the following text and assure that it's created properly
 radrails:
   yml: "<%="#{looks(GOOD)[0].to_go}"%>"

Rubygems View

  1. Open the Rubygems view, verify that after startup it is populated with entries for locally installed gems
  2. Click the green plus "Install" icon and ensure there is a large listing of remote gems
  3. Enter "p" in the field and ensure that it narrows the listing to gems whose names begin with "p". Pay special attention that the filtering is quick and not jumpy!
  4. Enter "mongrel" in the field
  5. Select the "mongrel" gem, and install the latest version (1.0.1)
  6. Repeat the above steps to install the latest "ruby-debug-ide" gem
  7. Repeat the above steps to install the "progressbar" gem
  8. Select the installed "progressbar" gem from the table listing, and click the red minus "remove" icon to uninstall it
  9. Install an older version of a gem
  10. Select the gem from the local install list and click the "Upgrade" gems icon, verify that both new and old show up in local listing afterwards
  11. Install another old version of a different gem
  12. Click the "upgrade all" icon in the Gems View, make sure all old gems are upgraded

Rails Servers

  1. Switch to the Servers view
  2. Click the "Add" (server with a plus) icon to add a new Webrick server to the generated project.
  3. Select the added server, click the green arrow "Start" icon to launch the server
  4. Open a browser for the launched server by clicking the world "Launch Server" icon in the Servers view
  5. Stop the server by selecting the launched server in the list and clicking the red block "Stop" icon
  6. Select the server in teh list, and click the page "Edit" icon to edit the server.
  7. Change the server type to Mongrel
  8. Open a browser for the server via the world icon (while it is not launched), verify RadRails asks if you'd like server started
  9. Select the server from the list and click the red X "Remove" icon to delete the server, verify it stops and then removes the server

Ruby Debugger

  1. Create a new file with a simple "puts 'hello' line"
  2. Double-click the left hand ruler on that line to set a breakpoint
  3. Right click the ruby file and choose "Debug as Ruby Application"
  4. Verify that debugger stops at the breakpoint
  5. Add additional puts statements and verify step over, step into
  6. Open Display view and enter arbitrary code to be evaluated
  7. Evaluate code using button in Display view
  8. Remove breakpoint and re-launch, verify that debugger doesn't stop