> For the complete documentation index, see [llms.txt](https://ploegert.gitbook.io/til/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ploegert.gitbook.io/til/programmy/rails/check-specific-attributes-on-activerecord-array.md).

# Check Specific Attributes On ActiveRecord Array

If you're writing a test against a method that returns a collection of ActiveRecord results, it can be tedious to check specific values for each. There are certainly an endless number of ways to approach those assertions.

You can keep your assertion fairly concise by using nested RSpec matchers. There are two in particular that can help with this kind of check:

```ruby
books = get_books_by("David Sedaris")

expect(books).to match_array(
  [
    have_attributes(
      "title" => "Calypso",
      "publication_year" => "2018",
    ),
    have_attributes(
      "title" => "Theft By Finding",
      "publication_year" => "2017",
    ),
  ],
)
```

The outer part of the assertion is `match_array` which checks that the result is an array of a certain size with specific elements. On its own we'd have to spell out all the attributes of each book, including things like `created_at` and `updated_at`. However, by combining it with `have_attributes` matchers, we are able to make the assertion over a subset of each record's attributes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ploegert.gitbook.io/til/programmy/rails/check-specific-attributes-on-activerecord-array.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.