# So many Expectations...

Expectations are the heart of RSpec

The main rule is to only have one expectation to each example and the reason for this is that the test suite will stop running if the first expectation fails. If you only have one expectation for every example then the test suites will run independently.

![](/files/-L9hu1QVkT7ahTHemWTp)

Some more examples

![](/files/-L9hu1QqPlNZYca1l_vl)

`eq`

, 

`match`

, 

`be`

 and 

`match_array`

 are the verbs that we have provided and they 

*are*

 the matchers.

The matchers are used as arguments to the `.to` keywords.


---

# Agent Instructions: 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://craftacademy.gitbook.io/coding-as-a-craft-bootcamp-prep-v2-0/week-1-programming-basics-ruby/rspec/so-many-expectations....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.