NAME

Interchange6::Test::Role::Fixtures

ATTRIBUTES

Fixtures are not installed in the database until the attribute is called. This is achieved by all accessors being lazy and so builders exist for each accessor to install the fixtures on demand.

    [qw( username email password nickname )],
    [ 'customer1', 'customer1@example.com', 'c1passwd', 'Cust1' ],
    [ 'customer2', 'customer2@example.com', 'c1passwd', 'Cust2' ],
    [ 'customer3', 'customer3@example.com', 'c1passwd', 'Cust3' ],
    [ 'admin1',    'admin1@example.com',    'a1passwd', 'Deity1' ],
    [ 'admin2',    'admin2@example.com',    'a2passwd', 'Deity2' ],

METHODS

All attributes have a corresponding "clear_$attribute" method which deletes all rows from the corresponding table and clears the accessor. Each also has a "has_$attribute" accessor which returns true if the accessor has been set and false otherwise. All attributes are created lazy and are set on access. The full list of clear/has methods are:

• clear_addresses
• clear_attributes
• clear_countries
• clear_inventory
• clear_media
• clear_message_types
• clear_navigation
• clear_orders
• clear_price_modifiers
• clear_products
• clear_roles
• clear_shipment_carriers
• clear_shipment_rates
• clear_states
• clear_taxes
• clear_users
• clear_uri_redirects
• clear_zones
• has_addresses
• has_attributes
• has_countries
• has_inventory
• has_media
• has_message_types
• has_navigation
• has_orders
• has_price_modifiers
• has_products
• has_roles
• has_shipment_carriers
• has_shipment_rates
• has_states
• has_taxes
• has_users
• has_uri_redirects
• has_zones