CODEWITHSUNDEEP
javascripttestingcypresscypress-intercept
Billy Bailey
Billy Bailey

Reputation: 53

Cypress - How to store a value from a request that changes each time to assert on it?

Our company is switching to Cybersource & tokenized credit cards. The token is new each time.

I'm trying to find a way to store the token from the request and reference it to assert it's correct.

Example of the request:

request:
body:
accountRegistrationPreferences: {email: ''}
paymentDetails: Array(1)
0:
billingAddress: {address: {…}, contactInfo: {…}, personalInfo: {…}}
cardId: "eusercc42210010"
tokenDetails:
referenceId: "bcc8c381-79d6-4a83-a10a-d67e2d585268"
token:

"eyJraWQiOiIwOFJORkptMWFIVlhhZUhRaUJrNHZNRFF1MGt3WW9kNCIsImFsZyI6IlJTMjU2In0.eyJkYXRhIjp7ImV4cGlyYXRpb25ZZWFyIjoiMjAzMCIsImV4cGlyYXRpb25Nb250aCI6IjAzIn0sImlzcyI6IkZsZXgvMDgiLCJleHAiOjE2NDQ0MzE2ODQsInR5cGUiOiJtZi0wLjExLjAiLCJpYXQiOjE2NDQ0MzA3ODQsImp0aSI6IjFFNVpSSEQzTFBaUzM0NUdIVVVUUjJQRjdFNzBZSDlKN1dTQjRTWEhTVEJEN08xTFRFUzg2MjA0MDk0NEFBNjIiLCJjb250ZW50Ijp7InBheW1lbnRJbmZvcm1hdGlvbiI6eyJjYXJkIjp7ImV4cGlyYXRpb25ZZWFyIjp7InZhbHVlIjoiMjAzMCJ9LCJzZWN1cml0eUNvZGUiOnt9LCJleHBpcmF0aW9uTW9udGgiOnsidmFsdWUiOiIwMyJ9fX19fQ.bCR73pMD9eXILtZHQRrmqgzcLqI_QCTEVtnQXNPJLOk-RxMUar8LbC1BS59G6FpynCI2rvJVMPixjtes2WRcnM77cjOlTarNM4-VnAJnqKluXy2jx5Hgtn_OrT7aSaS8NOoSyYzwPFlbkqsBMV5oT5kmiHZ8Qn4qBnga8sEYmPFgzoAUUnQ6uWLN1ZkZnKCO8uizZ_HaKUjdUQCyRzgWbtKfTctD9aAi5AcSNgAVbWTV_gt155jFa11v8mLF4iaqA3bLdJfEh4lu9HxB17sOShZBoZvxEQ3fN8gDkk4f56VlswB-aN3J5QFI7me36pgwY5khAhYrFma1o79V-b2KYw"

type: "tokenizedCreditCard"

Here's the Cypress test

  it("User clicks confirm & pay button to complete order", () => {
cy.intercept("/api/checkout/payandcommit?*").as("placeOrder");
cy.placeOrderAndPay();
cy.wait("@placeOrder").then((interception) => {
  console.log(interception);
  // Order status should equal 200
  cy.wrap(interception.response.statusCode).should("eq", 200);
  // Check payment details card type
  cy.wrap(interception.request.body.paymentDetails[0].type).should(
    "include",
    "tokenizedCreditCard"
  );
  cy.wrap(
    interception.request.body.paymentDetails[0].tokenDetails.token
  ).should("include", token);
  // Check request to ensure delivery charge is passed at £0 due to Unlimited membership.
  cy.wrap(
    interception.response.body.response.order.orderPriceInfo.shipping
  ).should("eq", 0);
  // Ensure standard delivery is returned in the order response.
  cy.wrap(
    interception.response.body.response.order.shippingDetails[0]
      .shippingMethod.type
  ).should("include", "standard");
});

});

This is the part I'm struggling with:

cy.wrap(
interception.request.body.paymentDetails[0].tokenDetails.token).should("include", token);

How can I store the token value that's changed each time so I can assert on it?

Is this possible? Any help would be amazing, I'm a bit of a doob and learning.

Upvotes: 0

Views: 823

Answers (1)

Fody
Fody

Reputation: 31944

To test that the response has a token property,

cy.wrap(interception.request.body.paymentDetails[0].tokenDetails)
  .should('have.property', 'token')
//or
cy.wrap(interception.request.body.paymentDetails[0])
  .should('have.deep.property', 'token')  // this assertion searches the object

To store the token an alias might be used

cy.wrap(interception.request.body.paymentDetails[0].tokenDetails.token)
  .as('token')

// Later in test
cy.get('@token').then(token => {
  expect(token).to.eq(expectedToken)
})

The token alias gets a new value every time you use .as('token'), so there's no problem with the changing token value.

Upvotes: 3

Related Questions