fixtures

I heard this term many times before (when talking about programming) but couldn't find any explanation what does it mean. Any good articles or explanations? I didn't find anything worth mentioning. m01 I think you're referring to test fixtures : The purpose of a test fixture is to ensure that there is a well known and fixed environment in which tests are run so that results are repeatable. Some people call this the test context. Examples of fixtures: - Loading a database with a specific, known set of data - Erasing a hard disk and installing a known clean operating system installation -

I am using Symfony 3.4.0, I try to load fixtures with: php bin/console doctrine:fixtures:load An error occurred while creating the data, what's wrong? This command looks for all services tagged with doctrine.fixture.orm . There is two ways to fix this problem. First one: any class that implements ORMFixtureInterface will automatically be registered with this tag. <?php namespace AppBundle\DataFixtures\ORM; use Doctrine\Bundle\FixturesBundle\ORMFixtureInterface; use Doctrine\Common\Persistence\ObjectManager; class LoadFixtures implements ORMFixtureInterface { public function load(ObjectManager

I'm reading about Rails fixtures in this guide (thanks, trevorturk). It appears you define classes in a Yaml file and they're automatically loaded into the test DB -- cool. But if you want to specify that this recipe belongs to that cookbook (or whatever) how do you do that? Are you supposed to specify the values for cookbook.id and recipe.cookbook_id by hand in the Yaml code? (Just a guess -- the guide doesn't show anything like that.) Or is there a more suitable way? You should use named fixtures, which automatically generate an id number for you where you don't provide one. These id numbers

Is there a way to load Rails fixtures in a specific order while running tests? For example, take the following classes... class User < ActiveRecord::Base has_many :memberships has_many :groups, through: :memberships end class Group < ActiveRecord::Base has_many :memberships has_many :users, through: :memberships end class Membership < ActiveRecord::Base belongs_to :user belongs_to :group end Memberships have a database level foreign key constraint requiring Users and Groups to be present before they can be created. However, because Rails loads fixture alphabetically, Memberships are loaded

So, I'm trying to learn the rspec BDD testing framework in the context of a rails project. The problem I'm having is that I can't, for the life of me, get my fixtures to load properly in rspec descriptions. Disclaimer: Yes, there are better things than fixtures to use. I'm trying to learn one thing at a time, here (specifically rspec) before I go play with associated tools like factory-girl, mocha, auto-test, etc. As such, I'm trying to get the dead-simple, if clunky, fixtures working. Anyway, here's the code: /test/fixtures/users.yml - # password: "secret" foo: username: foo email: foo

Does anyone knows how to load initial data for auth.User using sql fixtures? For my models, I just got have a < modelname >.sql file in a folder named sql that syncdb does it's job beautifully. But I have no clue how to do it for the auth.User model. I've googled it, but with no success. Thanks in advance, Aldo For SQL fixtures, you'd have to specifically have insert statements for the auth tables. You can find the schema of the auth tables with the command python manage.py sql auth . The much easier and database-independent way (unless you have some additional SQL magic you want to run), is