Using Cypress and Postman for Contract Testing with Pactflow

Поделиться
HTML-код
  • Опубликовано: 12 сен 2024
  • Increase the quality outcomes faster and get the whole team can get involved with contract testing using Cypress and Postman.
    As a tester, your role is to ensure quality, shorten feedback loops and promote shift-left testing activities such as contract testing. However, as a white-box testing tool, consumer driven contract testing using the Pact framework requires access to the source code and can hamper adoption if there isn’t the appropriate time and investment in up-skilling.
    Transitioning from separate QA teams and black-box style automation testing to more integrated shift-left approaches can take time, resulting in contract testing landing on the to-do list.
    What's covered:
    In this video, a recording of a live webinar, you'll be able to get up to speed with our new feature-Bi-Directional Contract Testing-enabling new and more accessible approaches to contract testing. Rather than having to rely on developer-led Pact tests in the source code, you can use the tools you’re comfortable with such as Cypress or Postman, or get started easily with plug-and-play adapters for popular tools or write your own.
    Key points:
    - Common blockers to starting and scaling contract testing
    - How Bi-Directional Contract Testing enables QAs to get more involved
    - A demonstration of how to use OpenAPI alongside Cypress and Postman in a contract testing workflow
    - How Pactflow’s unified contract testing platform enables you to choose between consumer-driven and API first approach
    Resources:
    The back story: why we created Bi-Directional Contract Testing blog pactflow.io/bl...
    👀 Check out the Bi-Directional Contract Testing workshops docs.pactflow....
    In-browser Katacoda tutorial - interactive and very easy to start with 🥳
    Mix & match Bi-Directional Consumer & Providers
    🆕 Read the Pact Cypress adapter blog pactflow.io/bl...
    ✍️ View the examples used in the demo:
    - Consumer Cypress example docs.pactflow....
    - Provider Postman example docs.pactflow....
    🏁 Tick off the pre-requisites for getting started docs.pactflow....
    - Create pactflow.io/tr..., ask for an invite to or invite someone else to your Pactflow account docs.pactflow....
    - Create or log in to your GitHub

Комментарии • 5

  • @manpreetsingh4084
    @manpreetsingh4084 8 месяцев назад

    Can we publish contracts for both provider and consumer by using only cypress ?

    • @PactFlow
      @PactFlow  8 месяцев назад

      No, you can only publish consumer contracts this way.

  • @ajinkyasagne6975
    @ajinkyasagne6975 4 месяца назад

    Can we publish contracts for consumer in java even if my consumer logic is in react

    • @fattymellows
      @fattymellows 4 месяца назад

      Yes, publishing a contract is independent of how the contract is generated.

    • @ajinkyasagne6975
      @ajinkyasagne6975 4 месяца назад

      @@fattymellows I mean my consumer logic is written in react . Can I write consumer bi directional test case in java language to generate pact file ?