I have searched the issue list for something similar, but I have not found the exact same issue.

The problem is that, given these two models:

factory :employee do
  # various attributes
end

factory :job do
  association :employee, strategy: :build
end

attributes_for ignores any explicit employee assignments:

attributes_for(:job, employee: some_other_em

Hello,

https://github.com/nelmio/alice/blob/v3.5.8/doc/advanced-guide.md#references

@user_{alice, bob} => @user_alice or @user_bob

If i:

client_type:

AppBundle\Entity\ClientType:
    client_type_{1..10}:
        name: '<name()>'

include:
    - client_type.yaml

AppBundle\Entity\Client:
    client_{1..20}:
        name: '<name()>'
        client_type: '@cl

Create an admin action (http://docs.djangoproject.com/en/1.1/ref/contrib/admin/actions/#ref-contrib-admin-actions) to allow one or more model objects to be selected and exported.

This was quite the challenge to debug so I'm just putting it here, at least for Google to find. It's very simple and perfectly uinderstandable if you know about it.

TLDR If you're persisting fixtures for use in tests, note that some Doctrine's lifecycle events such as postLoad will not fire if you're testing loading those items (or have custom handlers).

Reason is simple: you're fetchi

В readme в примере допущена ошибка
Example:

  ...
  mocks:
    service1:
      requestConstraints:
        # this check will demand that the request contains key1 и key2
        # and the values are key1=value1, key1=value11 и key2=value2. 
        # Keys not mentioned here are omitted while running the check.
        - kind: expectedQuery
          query:  key1=value1&key2=

The nu HTML validator has a respectable embedded HTML validation library.

This can be made into an inline Browser Test command:

|validate page source |

or

|validate page source | ignoring_errors_map | 

Or it could be made into a completely different Fixture that 'knows' where savePageSource() saves its files, or even can decompose the link returned by savePageSource() to han

If I want to insert faker data to database, what should I do?
I add the following code in my application configuration (console.php):

'controllerMap' => [
    'fixture' => [
        'class' => '@tests\faker\FixtureController',
    ],
],

And I rewrite the actionGenerate in @tests\faker\FixtureController. Is it right?

I am using this approach in some of my fixtures:

@pytest.fixture()
def async_wrapper():
    """Fixture to convert all regular functions into async ones."""
    def factory(template: str) -> str:
        return template.replace(
            'def ', 'async def ',
        ).replace(
            'with ', 'async with ',
        ).replace(
            'for ', 'async for ',
      

I'm testing the js on a page generated by a rails controller.

MagicLamp loads the page (it seems, correct me if I'm wrong) into a wrapper page of its own. This seems reasonable.

However by using this technique, the stylesheets from my page are loaded after the browser declares "document ready". Whereas in normal operation, stylesheets are loaded before document ready if there is javascript

The first author of an OFL fixture (i.e. the first in the authors array) should, in my opinion, be the person who is most response for this fixture.

When importing fixtures, this should be the importer and not the author of the original fixture file. As QLC+ is the only import plugin that supports authors, we should append the import's name as first author (instead of appending it as last aut