Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NEW: Allow SapphireTest::objFromFixture() to accept either table or class #6872

Merged
merged 1 commit into from May 5, 2017
Merged

NEW: Allow SapphireTest::objFromFixture() to accept either table or class #6872

merged 1 commit into from May 5, 2017

Commits on May 4, 2017

  1. NEW: Allow SapphireTest::objFromFixture() to accept either table or c… 

    …lass

Right now SapphireTest::objFromFixture() requires a class as the first
argument. This is fine when your fixture file uses classes as the keys,
but if populating a fixture via tables, objFromFixture() won’t work.

This patch lets you specify either the table name or the class name as
the key.

The benefit here is that you can build fixtures as raw inserts, which is
substantially quicker, and is likely to be a useful tool in building
more efficient test suites.
    Sam Minnee committed May 4, 2017
    Copy the full SHA
    1691e90 View commit details
    Browse the repository at this point in the history