Comments on: DevOps in Software Testing and QA Automation

By: Saurabh

Saurabh — Mon, 23 Dec 2024 10:25:56 +0000

Hi,
Thanks. Wonderful article to understand the DevOps which is future. Two Questions if you can help please.
1. Early automation sounds good but in actual, while requirements are changing frequently, there will be too much rework in updating the automation scripts.
Generally automation is advisable when system is matured. How beneficial it would be ?
2. How can we automate test cases for first sprint when application is not ready ? To achieve this, I think FSDs should be detailed enough but again that is difficult when requirements are changing frequently.

By: Siddharth Spehia

Siddharth Spehia — Sun, 22 Dec 2024 03:38:22 +0000

Article is really nice, but only question I have is what if product does not support Automation tool, then what can be done ?

By: Vidya

Vidya — Tue, 19 Nov 2024 02:52:42 +0000

In reply to Aniket Deshpande.

There are few releases such as Microsoft releases which happens every month, or upgrading OS or Software upgrades which requires Restart of the system. Change requests are created for these kind of releases, What you suggest to fit them into Devops cycle?

By: Ria

Ria — Wed, 04 Sep 2024 00:55:22 +0000

hello,
Since you are a QA Manager, do you have separate QA/Testers in the DevOps setup? Or this is shared on a Developer only? Meaning These Developers are multi-skilled at programming and testing. They can code review each other’s tasks and test each other’s tasks as well.
Have you experienced a setup where in DevOps, there are still separate roles on BA, Dev & QA?
Thanks.

By: Amrutha

Amrutha — Tue, 03 Sep 2024 00:07:19 +0000

A great article.

Thank you so much for sharing on web.

By: D Adesina

D Adesina — Tue, 27 Aug 2024 12:00:11 +0000

Hello again Aniket,

Thanks for the article .

How does DevOps work with System Integration Testing and also User Acceptance Testing?

I recognise the logic and need to automate, but we seem to be selling it as a magic pill that instantly shortens manual testing effort and I just cant seem to see that.

Software Testing on a new enterprise wide system being built requires extensive test preparation activities most of which will not immediately benefit from automation

What are your thoughts?

By: Aniket Deshpande

Aniket Deshpande — Fri, 16 Aug 2024 13:40:17 +0000

Hi Swapnil,
Thanks for the feedback.
Developers will either fix bugs or implement new features (User Stories). That is what is depicted in the diagram. Essentially, anyone in the chain can raise a bug (not just QAs).

By: Advait

Advait — Sun, 21 Jul 2024 02:15:11 +0000

Hi,
One doubt is how we can use this for 1st sprint where we will not be having for application during 1st deployment. So we cannot automate our test cases for 1st sprint till deployment is done. So I wanted to know how we can integrate automated test cases in “Devops” for 1st sprint.

By: amol

amol — Fri, 19 Jul 2024 07:49:17 +0000

Hi,

What about UAT and non functional Testing like Performance and Security testing in DevOps will work

By: Sirisha

Sirisha — Thu, 18 Jul 2024 00:34:46 +0000

This article gives a good birdeye view on the current methodology,thanks for the information.

By: Aniket Deshpande

Aniket Deshpande — Fri, 12 Jul 2024 22:51:29 +0000

Hi Siddharth Spehia,
Automation is the corner-stone of a successful DevOp cycle. There are various ways in which automation can be achieved like Non-UI automation or API automation, etc. Obviously, you cannot have all your tests automated, and DevOps does not mandate this. But all your high-priority, end-to-end tests need to be automated and added to the cycle. Talk to your developers to help you achieve this. Ideally, you should start your automation scripting along with early dev builds so that you can provide feedback to the developers regarding blockers for automation.

By: Vamsi

Vamsi — Wed, 19 Jun 2024 16:15:17 +0000

The Article is Very Nice and more Automation takes huge time to comlete the QA Cycle and revert back to Dev team for fixing bugs….

By: Tejaswini

Tejaswini — Fri, 14 Jun 2024 09:52:13 +0000

Nice read. Came across the term DevOps during my SAFe Agilist workshop. Your article gave more insight into it. Thanks Aniket 🙂

By: Harry

Harry — Mon, 25 Mar 2024 05:36:12 +0000

Hi Aniket,

its nice blog those who want to switch their career as a Devops QA Role which is hot skills in the current market.

Please let me know your email id so that i need to discuss more on Devops.

Thanks a lot !

By: Sergey

Sergey — Sun, 24 Mar 2024 05:10:03 +0000

‘QA changes for DevOps Testing:’ – not sure how is this different to any other Dev Methodology. Regardless if this is Waterfall or Agile-like Methodlogies – you want to automate deployments/testing/clean-ups to the best extent you can. Needless to say that environments have to be standartized as well.
So what is so specific here for DevOps? Just trying to the uathors point of view.

By: Manasi

Manasi — Fri, 22 Mar 2024 21:17:42 +0000

Thank you Aniket for sharing such a nice article on DevOps.

By: Anand

Anand — Sun, 17 Mar 2024 19:07:08 +0000

In reply to Saurabh.

Thanks Saurabh. I have same questions the moment I heard about DevOps. I would like to add third point
3. What would be the solution if some Test Scenarios can not be automated?

Sorry to switch over the topic. Very similarly when Agile is adopted, the I was searching for the answer for

In which Sprint one can do the E2E business process testing?. For an example, like “Order to cash business process” in the typical enterprise setup where multiple applications are involved. Especially when the user stories for a release requires the code change only few application in the stack of application to complete E2E business process. In some places, they run different sprint for E2E (Runs once in every four Sprints or where there is a logical end) and others run after the last sprint like waterfall model. I feel this defeat the purpose of Agile. Any one has better solution?

By: Gaurav Khurana

Gaurav Khurana — Fri, 15 Mar 2024 21:58:34 +0000

Article is good . With all these terminologies in market, what I feel are teams are coming closer and with co-ordinaton work is executed in a better way.

Tomorrow in market 1 new terminology will come where BA will also sit with testers, then you will have excellent results

By: Meghal

Meghal — Thu, 08 Feb 2024 08:57:23 +0000

Hi Aniket,
We are a team of 5 developers working for a telecom client project. We are to give integrated devops as a part of the deliverable along with the work assigned. I need to know whether in a devops culture are the developers supposed to do QA as well, Write Test cases themselves & also write the selenium automation scripts themselves for CI CD? What does devops principles say? Should there be a dedicated Dev & QA team along with Devops engineers who could wear bot the hats of Dev & QA. Are the Devops engineers part of Dev Team or QA team or are shared resources or are they a dedicated team separate from Dev & QA teams?
Now since I have just 5 developers should I train them in QA & in Devops automation & make them do all the work of Dev QA & Dev ops? Its going to be tightfisted situation if they are to deliver in weekly sprints as well as write QA test cases & do automation in the same week for the sprint. Should I propose the Client to allow me to add a team of QA engineers who know selenium & also know automation & let the 5 developers focus on Dev stories. Ofcuorse once the QA comes in then the Dev will start learning Selinium & contributing to the QA & the automation part.. Will this proposal be violating Devops principles that the developer needs to do QA & automation both in a typical Devops setup? Please suggest how to deal with this situation & what exactly are the devops guidelines for the duties of a developer, a QA & automation team. Or is it just one Devops team which does all 3 things?? Or is it a dedicated Devops team of engineers who take care od this integration of Dev QA & Deployment?? should the devops engineers be a part of Dev or QA team or are they a part of different devops team… I am really confused when it comes to resource allocation & resource billing for the client in a typice devops setup. Please advise.

By: Stacy LAwrence

Stacy LAwrence — Thu, 11 Jan 2024 04:25:33 +0000

The Philosophy of Continuous integration (CI) is to make small code changes and check-in code frequently to a central repository and then ensuring that you are making progress in terms of features (or bug fixes) while not breaking any existing functionality. To be able to check if no existing functionality is broken is to check this frequently via automated tests. Thus, CI can meaningfully exist only when there is adequate automated testing.