expect() for BDD assertions in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ assertion

intermediate

Check if element contains exact text using expect()

You want to verify that a button with id #submitBtn contains the exact text Submit. Which assertion using expect() is correct?

Cypress

cy.get('#submitBtn').then(($btn) => {
  const text = $btn.text();
  // Which expect assertion is correct?
});

A expect(text).to.include('Submit')

B expect(text).to.contain('submit')

C expect(text).to.equal('Submit')

D expect(text).to.have.text('Submit')

💡 Hint

Use to.equal() for exact match of strings.

to.equal() checks for exact equality. to.include() and to.contain() check for substring presence. to.have.text() is not a valid Chai assertion.

❓ Predict Output

intermediate

Output of expect() assertion on array length

What is the result of this Cypress test snippet?

const items = ['apple', 'banana', 'cherry'];
expect(items).to.have.length(3);

Cypress

const items = ['apple', 'banana', 'cherry'];
expect(items).to.have.length(3);

A Test fails with length mismatch error

B Test passes successfully

C SyntaxError due to wrong assertion syntax

D TypeError because items is not a DOM element

💡 Hint

Arrays have a length property that can be asserted.

The assertion to.have.length(3) correctly checks the array length. No errors occur.

🔧 Debug

advanced

Identify the error in this expect() assertion

What error will this Cypress assertion produce?

cy.get('.alert').then(($el) => {
  expect($el.textContent).to.include('Error');
});

Cypress

cy.get('.alert').then(($el) => {
  expect($el.textContent).to.include('Error');
});

A Test passes successfully

B AssertionError: text does not include 'Error'

C SyntaxError due to missing parentheses

D TypeError: $el.textContent is not a function or property

💡 Hint

Check how to get text content from a jQuery element.

$el.textContent does not exist on a jQuery object (use $el.text()). It is undefined, causing a TypeError.

🧠 Conceptual

advanced

Understanding chaining with expect() in Cypress

Which statement about chaining assertions with expect() in Cypress is correct?

A You can chain multiple assertions like <code>expect(value).to.be.a('string').and.to.include('test')</code>

B You must use separate <code>expect()</code> calls for each assertion

C Chaining multiple <code>expect()</code> calls on the same value is not allowed

D Chaining works only with <code>should()</code>, not with <code>expect()</code>

💡 Hint

Chai assertions support chaining with and.

expect() returns an assertion object that supports chaining with and for multiple checks on the same value.

❓ framework

expert

Best practice for asynchronous expect() assertions in Cypress

Consider this Cypress test:

cy.get('#status').then(($el) => {
  expect($el.text()).to.equal('Loaded');
});

What is the best practice to ensure the assertion waits for the element text to become 'Loaded' before checking?

A Use <code>cy.get('#status').should('have.text', 'Loaded')</code> instead of <code>expect()</code> inside <code>then()</code>

B Add a <code>cy.wait(5000)</code> before the <code>expect()</code> call

C Use <code>expect()</code> inside <code>then()</code> without changes; Cypress handles waiting automatically

D Wrap the <code>expect()</code> call inside a <code>setTimeout</code> with delay

💡 Hint

Use Cypress built-in retry-ability for assertions.

should() retries the assertion until it passes or times out, making tests more reliable. Using expect() inside then() runs only once and may fail if the text is not ready.