Cypress Automation Solutions

  In any case, I used the  testFiles  config in  cypress.json  to set the spec file run order:   You can use your file names. Only the files will be shown in cypress runner which you will define here "New_Api" is a Sub-folder in integration folder. All other are spec files. {      "baseUrl" : "https://exapmle.com" , "testFiles" :  [          "New_Api/*" ,          "Add_Product.spec.js" ,          "Add_Client.spec.js" ,          "Seller.spec.js" ,          "Deal_Status.spec.js" ,          "Buyer_Offer.spec.js" ,          "Buyer_2.spec.js" ,          "Deal_Status.spec.js"            ], }

  We like to pretend there are two disjointed end-to-end test types: API and browser automation tests. And that the tools used are very different; the API tests are executed by a CLI test runner, while automation tests all fire up a browser. Yet, a good E2E automation test runner, in my opinion, should be really good at working with a remote server API via HTTP. After all, this is what every useful website does. Every website exchanges data with remote servers through HTTP requests. What if the same tool could do both tasks very well? What if the same tool could exercise the feature of your TodoMVC web application,  and  could test your server’s API to make sure a server-side logical or data error has not crept up undetected? +------------------------------+ | http://.... | |------------------------------| | | | | | | | | | web application <-