Gist 166095

100%

✓ Published0🌍 Public

Last edited Aug 11, 2009

Created on Aug 11, 2009

This example demonstrates the Forgery Ruby gem’s ability to generate placeholder data, showing repeated outputs for Lorem Ipsum text, paragraphs, and U.S. city names. The code uses `LoremIpsumForgery.text`, `.paragraph`, and `.paragraphs` to produce dummy prose, while `AddressForgery.city` returns sample city names like “South El Monte” and “Winters.” The interaction occurs in an IRB session, where each call returns consistent, reproducible fake data, highlighting the gem’s utility for seeding test datasets without a visualization layer or external data source.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 189433

This visualization shows a Ruby data fixture that defines user account attributes for a test suite. It uses the Machinist library’s `User.fix` block to generate randomized login names, emails, and passwords via regex-based `unique` generators, along with nested `Character.make` factories. The code specifies constraints like password confirmation, character count limits, and a boolean agreement flag, demonstrating how to construct realistic test data without a rendering API.

XXXX

60% match

Loading thumbnail…

Gist e1458497b7415589b8b144e03e5f918d

This example demonstrates a JavaScript module that generates deterministic lorem ipsum text using a seeded pseudo-random number generator, with the ability to customize word counts, sentence lengths, and paragraph structure. It is implemented as an Angular factory service named `lorem`, built on top of the `angular.module` API. The code adapts the `loremIpsum` function from the knicklabs/lorem-ipsum.js library, replacing the default `Math.random` with a custom sinusoidal seed-based generator, and supports plain or HTML output formats for generating placeholder content.

MMcNull

59% match

Loading thumbnail…

Gist 155450

This example demonstrates how a Ruby web application can dynamically render page fragments by combining HAML templates with a randomized helper method. It shows a structured layout where the `.foo` and `.bar` sections incorporate a partial template (`_my_header.html.haml`) and a form builder for user data. The helper `my_helper` generates a different partial path each time by appending a random integer (0, 1, or 2) to the string `"some/partial_"`. The code uses HAML’s partial rendering and the `form_for` helper from Rails’ form builder API, though it does not specify the actual data source or visual output.

XXXX

58% match

Loading thumbnail…

Gist 578871

This example shows a Gist titled "Gist 578871" that integrates RSpec mocking and Authlogic into a Cucumber testing environment. It demonstrates how to configure RSpec's mock framework within Cucumber steps by explicitly setting up and tearing down mocks around each scenario. The code loads supporting files like `support.rb`, which requires `cucumber/rspec/doubles` and `rspec/core`, and uses `RSpec::Mocks::setup`, `verify`, and `teardown` in `Before` and `After` hooks. It also activates Authlogic’s test mode and resets `Sham` data. The rendering approach is code-based, not visual, focusing on test configuration.

DDylanFM

54% match

Loading thumbnail…

Gist 155911

The example demonstrates a user-creation form rendered with a dynamic Processing sketch embedded in the page header. The layout uses HAML with a Sinatra-style `form_for` helper, while the header includes a random selection between two Processing logo sketches via `partial "logos/logo_#{rand(2) + 3}"`. The Processing code initializes either an `x_axis` or `y_axis` variable, but no drawing or interaction is defined, so the sketch remains static and incomplete. The data source is the embedded Processing script, served through the Haml template’s partial mechanism.

XXXX

54% match

Loading thumbnail…

Gist 189418

This example captures a runtime error trace from a Ruby on Rails application using DataMapper and SQLite. The visualization maps the call stack of a failed database INSERT operation, showing the sequence of method calls from the SQL adapter through the ORM to the controller and test framework. It highlights the datatype mismatch that occurs when inserting a record into the "locations" table, with the error propagating through the Merb framework and RSpec test suite. The gist documents the exact code path and failure point for debugging.

XXXX

53% match

Loading thumbnail…

Gist 152205

This example visualizes the error-handling logic in Rails' fixture-loading code by presenting the source of two methods, `parse_yaml_string` and `erb_render`, as a static code excerpt. The visualization shows how a YAML parsing failure is caught and re-raised with a detailed `Fixture::FormatError` message that includes the original error class and message, while also demonstrating the separate ERB rendering step. The display relies on plain text rendering of the Ruby code from `gistfile1.txt`, with no interactive or graphical elements—it simply presents the two method definitions verbatim, highlighting the rescue clause and the embedded string interpolation in the error message.

XXXX

52% match

Loading thumbnail…

Gist 206559

This example demonstrates a subtle bug in DataMapper, a Ruby ORM, where defining a custom `foo` method and `foo=` setter on a resource class shadows the association defined by `belongs_to`. The code creates a `Foo` and a `Bar`, then assigns the string `'boom'` to `bar.foo` and reads it back, showing that the custom setter and getter are invoked instead of the association. It uses DataMapper’s `Resource` module, `has n` and `belongs_to` macros, and `DataMapper.setup` with an in-memory SQLite database via `sqlite3::memory:`. The output is a simple string assignment and retrieval, illustrating the override behavior.

XXXX

52% match