Gist 189433

Gist 155982

This visualization demonstrates a web form interface built with Haml markup that creates a user account through a submit action. The code uses the Haml templating engine, embedded Ruby (ERB) for partial inclusion, and a form helper API that binds to a `@user` object. A JavaScript logo partial defines an integer variable `x` with a value of 755, though the visual output of this variable is not shown in the provided code. The example relies on standard HTML form submission rather than a visualization library, with the layout structured through nested Haml indentation.

67% match

Gist 151492

This example shows a stack trace from a Ruby on Rails test suite failure, where a YAML parsing error prevents fixture loading. The error message indicates that a `NoMethodError` occurs for `abstract_class?` on `Object:Class` while parsing `galleries.yml` in an ActiveRecord fixture. The visualization presents the nested call stack from RSpec and Rails internals, illustrating the sequence of method calls leading to the failure. It highlights the point where indentation issues in the fixture file trigger the parsing error.

62% match

Gist 6b70052296ccf0ebf338143509429d64

This example simulates a simplified Facebook-like social network in Ruby, using a `User` class to model profiles, friendships, and wall posts. The code defines methods for adding friends and posting content to another user’s wall, checking friendship status before allowing a post, and initializing two user objects with sample data. It uses the `pry` debugging library via `binding.pry` to pause execution and allow interactive inspection of the state, with no graphical output or external visualization library.

JJastor11

62% match

Gist 202667

This example shows a Ruby error trace from a failed RSpec test run, specifically a `TypeError` about dumping an anonymous class while using YAML serialization with single-table inheritance subclasses in a `before(:all)` hook. The visualization presents the full stack trace, highlighting the chain of method calls from the test assertion through DataMapper’s YAML adapter, Extlib hooks, and RSpec’s example runner. The code uses standard Ruby libraries (`yaml`, `pathname`) and frameworks like DataMapper, Extlib, and RSpec, revealing how the error propagates across the gem’s internal APIs.

Gist 189415

This example shows a Ruby on Rails controller test that verifies a user can be created via a POST request. It uses RSpec’s `describe`, `before`, and `it` blocks to set up a User instance, delete its `id` attribute, and then assert that the `POST` to the `:users` resource changes the User count by one and returns a successful response. The code relies on the `request` helper and `lambda` to wrap the API call, checking both the database change and the HTTP status.

Gist 850654

This example shows how to test authorization and role-protected attribute updates in a Rails controller using RSpec. It verifies that a user cannot edit another user’s profile, can change their own given name, and cannot modify their role field, with assertions on flash messages, response codes, and assigned attributes. The code uses Devise::TestHelpers to sign in a factory-built user, and RSpec’s `describe`, `context`, and `it` blocks to structure the test cases.

VVortex

Gist 48499

This example shows a Ruby on Rails functional test for a `UsersController` action that finds recently active users. The specification verifies that a request to `/users/find_recent/24` returns a JSON list of users, using RSpec's mocking and expectation framework. The code relies on the `should_receive` method to stub the `User.find_all` call with an argument of 24, and the request helper simulates an HTTP call, comparing the response body against the mocked object’s `to_json` output. The test implicitly checks the controller’s rendering behavior but does not demonstrate any data-visualization or chart-rendering logic.

CCaged

Gist 159860

This example shows a browser-based test suite for a web application, rendering and validating the behavior of game interfaces for character management, chat, combat, inventory, and store features. The page runs JavaScript test specifications using JSpec, a testing framework, and includes jQuery and jQuery UI plugins for DOM manipulation and event handling. It also embeds HTML templates for dynamically displaying equipment, inventory items, and buffs. The code relies on custom application scripts, such as `application.js` and `character.js`, and uses `JSpec.include` to execute multiple test files sequentially, reporting results in the `#jspec` container. The data comes from the application’s live DOM elements and simulated XHR requests.