Capybara is not waiting for ajax to finish

Question

I'm working on a application which consist of a EmberJS frontend, which talk to a Rails server via REST. In my application goes through a wizard to create a job, so i would like to test if that job is created, this is my test. ``` feature 'Processing step three', :js => true do background do to_step_2 to_step_3 end scenario 'Creating job', js: true do within '#login' do fill_in 'Email', with: @customer.email fill_in 'Password', with: @customer.password click_button 'Login' end expect { click_link 'Create job' }.to change(Job, :count).by(1) end end ``` So when the user has filled in everything, lastly they click on create job, just like my test describes. This works fine when i do it manually, but when i run my spec i get. ``` 1) Creating a new job Processing step three Creating job Failure/Error: expect { click_link 'Create job' }.to change(Job, :count).by(1) count should have been changed by 1, but was changed by 0 # ./spec/features/creating_a_new_job_spec.rb:103:in `block (3 levels)…

Accepted Answer

The main problem, as you said, it's Capybara didn't wait. But the main reason is the test doesn't use a consistent style.

If using Capybara, the test acts like a real user, and you should expect some UI change instead of database change, for real user can't see what happens in db.

In this test, the db assertion is executed right away, even faster than the browser driver sending data to server, so the data is nil.

To fix,

Remove the `within` block at first. This seems unimportant. If I remembered correctly, the expectation should better not in different block of the action. So do it for safety.

Add UI expectation. Then Capybara will wait until the effect appears.

So,

```
scenario 'Creating job', js: true do
  fill_in 'Email', with: @customer.email
  fill_in 'Password', with: @customer.password
  click_button 'Login'
  # Assume your page will show user name after signing in
  expect(page).to have_content(@customer.name)
end
```

If you really want to test db change, you can add that expectation after UI expectation, but I don't recommend that.

Capybara is not waiting for ajax to finish

Solution

Problem