Two other consideration to note here is: 1. In some projects developers contribute to the framework development and scripting. Then an agreed upon language between us would be good. 2. We can reuse common POJOs, libraries between Dev and Test automation framework that will avoid a lot of rework.

Thanks for coming up with a dedicated video on this Naveen, will share as much as I can in my network to bust this myth. 😊👍

In org level "cant" word is very tuff to say.what they say we have to do

I'm addicted to your channel. Can't wait for the next upload!

Nice Info Naveen

Most of the companies focus on mono repo. Means your automation script also be there in same repo of development code. In this case if we use different tech stack, then it will create issue in integration. If automation script is maintained in another repo then any tech stack is perfect for automation.

@naveenautomationlabs

3 ай бұрын

So just coz of maintaining the code in the same repo, you will prefer to pick the same tech stack. That's a wrong understanding. In ci cd pipeline, it can be easily integrated with different git repos either it's Jenkins or GitHub actions or git lab etc. Also, most of the companies focus on mono repo, that's a wrong perception once again. It has its own disadvantages. Also would like to know, what kind of integration issues if you use the diff tech stack?

@nityaranjan6714

3 ай бұрын

@@naveenautomationlabs Let's suppose, Company using React, typescript like tech stack for development. Can we use java, selenium, maven in that same development repo? In this case Cypress with typescript would be the best choice right, if we have to maintain automation code in same development repo.

@naveenautomationlabs

3 ай бұрын

@@nityaranjan6714 but what if cypress is not supporting or not the best fit for my application? What if I want to use Selenium with java which is fulfilling all the requirement of test automation of my project? most of the projects are using reactJs, angularJs, vueJs etc with JS/TS for web development. It does not mean that automation tech stack should also be same. Also, why do you want to maintain the automation code in the same dev repo?

@nityaranjan6714

3 ай бұрын

@@naveenautomationlabsUsing Mono Repo, its depend upon Company to Company. In this way, QA can have access to Dev code and can understand the Dev code if he knows atleast basic Typescript. Sometimes we have to implement the configuration files in cypress like same Dev code. In this case it would be better to refer Dev code and make configuration with little change. Mono Repo having its own advantages also.

@naveenautomationlabs

3 ай бұрын

@@nityaranjan6714 If you want to understand and debug the dev code, you can always clone their repo and setup the project in your IDE. What kind of config file we have to maintain in cypress like same dev code? Also how exactly dev code is helping you to make changes in your automation repo. You should not rely on dev code, you should focus upon testability in test automation that how UI/API are working. I am still looking for some really good advantages of having same code repo.

Hello sir, please let me know if figma app and figma plugin can be automated with Selenium. Thanks sir.

Lot of UI focused automation with 60 test steps in a test case is given for Automation. Justification is not working when we say

@naveenautomationlabs

3 ай бұрын

hmmm but writing 60 test steps in single test case also is a bad approach.