Yes, nice. Though for tests like this I prefer to see more than one result making it through the filter and at least one object being filtered out, since then you know that your filter method isn't just returning the first result for some reason and it happens to be what you expected. It would also make sense then to test the value of the answers to make sure they're the ones you expected. You can even replace the current assertion with something like `expect(answers.map(&:value).to eq [40,50]` to kill two birds with one stone.