Skip to main content

Posts

Role of Software Development Engineers in Test (SDETs)

Introduction In the ever-evolving landscape of software development, the role of Software Development Engineer in Test (SDET) has risen to prominence. These professionals combine their expertise in both software development and quality assurance to ensure the delivery of reliable, high-quality software products. In this article, we will delve deep into the responsibilities of SDETs and emphasize their indispensable contributions to the software development process. Building Test Automation Frameworks One of the foremost responsibilities of SDETs is the design and development of test automation frameworks. These frameworks serve as the backbone of efficient and scalable testing processes. SDETs leverage their programming skills and knowledge of testing frameworks and tools to create reusable test scripts and libraries. They design these frameworks in a modular and maintainable manner, emphasizing flexibility and reusability across different projects. By constructing robust automation fr
Recent posts

What is Softans?

Softans: Softans is an emerging Platform to to ask/post your questions. You can also create polls here. You will get results more quickly than other platforms. It is user friendly platform to ask questions. Join Softans  community and earn points. If you refer someone , You will get extra points which will be displayed on your profile. 

Test files sequence in Cypress Or Test file Order in Cypress

  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"            ], }

How to Add GUI to your E2E API tests ?

  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 <-