Hi Raghav, it was really good explanation. I have few doubts, it will be really helpful if you please clear them 1. Devloper after building the application in dev env, does a CI for dev env, where he builds his application and performs unit testing against the same. And then he deploys the application to Test environment. 2. In Test env, test team perform CI for the application where they perform automation testing against the application deployed. Once , the CI is successful and with no issues, Dev deploy the application to staging (Pre prod) env. 3. Code written by automation team then runs in Pre prod env. Also, acceptance testing is done. 4. If this is successful then it is deployed to prod env, and given to customer. 5. Then application is monitored and given is looked for the changes, if there are changes then it is taken care in next release. And cycle continues. Please let me know if my understanding is correct. If not let me know correct behaviour. Thank u 😊
Hi Sir, What is role of QA in in CI? Run sanity pack right. Means unit n code integration test will be done by dev team. QA can run sanity script after above dev work is completed?
Hi Rushikesh, yes so not just Sanity, we can run all functional, regression tests that are automation, performance, security etc can also be a part of CI CD, So just think like this, all the stages required to certify a build ready for production deployment
Excellent, many thanks for this series. Please, explain topics like REST API, Microserices Architecture, DOCKER, Kubernetes with interview point of view.. same like this vdo. You may also explain one or two commonly asked questions on these topics during interview for experienced candidates. Thanks again.
Here I am having a doubt Raghav. I got clear CI part. But after that how continuously we test the new build all of sudden in automated wY. As devloper newly release the new build, we dont have any automation code ready to check the new functionality in automated way(like in selenium) . So how we can achieve continuous testing for new builds here??
Hi Nitya, for planned changes we have a process, as the dev team is coding, the test team creates functional tests, When the new code is released, if the new tests are ready, they are executed, else the set of regression tests are executed and the new tests are added later and tested
@@RaghavPal Still its unclear for me. Let take an example : In a application dev team is added a newly functionality lets suppose added phonepay option for payment which was not there previously. So for this functionality Automation testers dont have any code for testing it through automation. I am not telling about functional testers. How we can achieve a pipeline here to test this functionality when a developer commits that change in code??
@@RaghavPal If for new changes in Automation testing we add that in next sprint. Then here we are not achieving continuous testing right. As continuously it is not tested the new functionality when devloper changes the code. You got my point right? I just wanted to ask where we are achieving continuous testing for new functionality in a pipeline?
Thanks for coming up with this School of Basics series. This is really very helpful. I would vote for RPA- Robotic Process Automation as the topic for the next episode. Would like to know how it is different from the normal test automation.
Hi Raghav, Thanks for sharing this. I have 1 basic question..When a new feature is developed, unit test cases will be triggered as a part of CI, but the Test Automation script is not ready. Will it be a stable set of Regression Test cases that will run in the 1st iteration iteration and from next cycle we will make sure we have added the test script in our existing Regression pack? Is there a risk as the functionality has not been properly tested and signed off, before moving to the next stage?
Our company as well moved to CI /CD process every Friday we're releasing on production, the drawback of CI/CD is intense work pressure on automation QA, Maintenance now is more tedious and time-consuming.
Hi Ravi, we need to have all our processes and apps to be mature and ready for CI CD. So that a continuous and smooth pipeline can be created. If any process or step in the pipeline is not ready, it can impact the complete ci cd process. I will plan to create a session on how to make your processes ready for CI CD
Really a great explanation. Thanks a lot. So basically this CI/CD process works fully automatically if there is no manual testing involved right ? If not after the delivery there is a testing phase by QA team with manual tests and the process will continue from then onward again. Is it ? So in real world can we have the 100% Continuous Delivery ?
Manual Testing will be needed in different scenarios and ways, sometimes on new changes, we first need to write test cases and test them and automate them in the next release cycle or sprint
Excellent and well done video to explain in pure and simple english these complex IT definitions. Appreciate it and you saved me reading many online wasted tutorials! Thanks a lot. Mohee from Doha @ 45C
Hi Raghav this is Kishore Kumar I have a question for you will give a class on AWS & AZURE Security comparison important thing as you know that? Thank you 👍.
Thanks for explaining this. Irritated by seeing this in job roles and resumes. So came here to end it once for all. Thanks bro. Very clearly explained.
@@MAli-vf6cf No Bro, I am not looking for cloud roles. But wanted to learn things generally. Also make sure your resume contains keywords of cloud, Update naukri, update Linkedin, grow your linkedin network, apply for jobs taking help of referrals etc… I am sure done right, you will be able to get a job. Now market is hot
Very concise and informative. Can you please provide some guidance on what categories of tests will be executed in each env and how frequently it should be run? For (e.g) if we have to release to prod after every 2 week sprint, how frequently do we have to deploy to test env? When during the sprint will we have to deploy to stage? Thanks in advance!
Hi Raghav, for Continous delivery is a kind of manual deployment like It manager approval is needed to deploy to prod where as continous deployment is a auto deployment where in the approvals are not needed to deploy to prod .. Am i correct Not sure on this can you please reply back .. Thanks in advance
Hi Nitik, Env is the hardware and software configuration (setup) needed to run the application/project Stages are the phases of the project/app like Dev Test Deployment Release
when coming to Continuous Deployment You said that the every release that passes through automated tests will directly deployed to prod environment right. These changes will go from CI stage till Continuous Deployment stage or just after automated tests deployed directly to prod?
Hi Akhila, the build or release that is tested completely at all stages goes to production, Now based on the needs and the process, some org can deploy after successful automation testing, some may have other tests involved, like performance, security, compatibility etc
These topics are so helpful, thank you!! Do you know if there is a test automation tool that can be used with Windows based applications (.Net) thanks!!
Hi There are tools for desktop applications like TestComplete, Katalon studio etc Can check this too - ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-hzzGzZRj9XI.html
@@RaghavPal One more thing...Can you make a video on negative testing. ..how to think in terms of "breaking" things .. backend testing and api's. Thanks for all of your amazing content.
