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

I understand the reasoning behind the documentation for i_suck_and_my_tests_are_order_dependent. However I feel that this method name and its comment are glib and do not provide adequate rationale for why tests should be order independent. Nor does it allow for the possibility that there are a very limited number of legitimate reasons to want tests to be run sequentially, particularly when deali

Hi there,

I think this can be a good issue for a first-time contributor. It would be great if we can increase documentation for the DatabaseCleaner::Configuration API: https://github.com/DatabaseCleaner/database_cleaner/blob/master/lib/database_cleaner/configuration.rb#L56-L72

Even though methods are pretty self-explanatory, I think it is a good idea to maintain a complete documentation for

Detailed Description

Update os_env documentation to state where variables should be set for controls using the os_env resource.

Context

Why is thi

From [this comment][3]:

I looked up the YARD docs for a @param tag and was surprised to see that the order should be: [@param name [Types] description][1]. I noticed that all of the Mocha YARD docs use @param [Types] name description which seems odd. I trawled through the historical YARD documentation, CHANGELOG, and issues and [eventually discovered][2] that although the documented o

Description

After running chefspec, the summary output for tests are no longer displaying the verbs. Is this a recent change to the coding standard and I need to update my tests or a bug with ChefSpec?

e.g.,

Tests

expect(chef_run).to create_directory('/opt/my-folder').with(
  owner: 'root',
  group: 'root',
  mode: '0755',
  )
end

it do
  expect(chef_run).to inst

When using include_examples a new RSpec context is not created, unlike with it_behaves_like. It is a common mistake to write something like:

include_examples 'my thing' do
  let(:a) { 'a')
end

include_examples 'my thing' do
  let(:a) { 'b')
end

And the author of the test might not realize that a will be defined as 'b' in both cases. (NOTE: I'm writing this sa

We can currently create privileged containers but it would be nice to have able to give it limited access as opposed to keys to the kingdom.

Documentation: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities