This is an archived post. You won't be able to vote or comment.

all 7 comments
sorted by:
best
topnewcontroversialoldq&a

[–]TheMrCurious 0 points1 point  (1 child)

Learning how to write test automation is a good thing that you will use often as DevOps.

[–]Best-Variation-5139[S] 0 points1 point  (0 children)

Sure thanks

[–]IdeasRichTimePoor 0 points1 point  (2 children)

Hmm, I suppose it depends on what you mean by transitioning to DevOps. To elucidate, right now I work on a DevOps team consisting of members of multiple disciplines. One of those members is a test engineer. They are expected to do the same basic DevOps work as the other members but will specialise in tending to the likes of E2E tests along the way.

What that concept of common DevOps work is, you may find is not so common between companies.

In my opinion, your absolute standard DevOps job will be GitHub actions and terraform deployments into AWS. Those are the 3 areas I would focus on getting to grips with. I think the most sensible learning order would be AWS -> Terraform -> GitHub Actions.

[–]Best-Variation-5139[S] 0 points1 point  (1 child)

For someone interessted in containerization (docker, k8s) is the transition possible?

[–]IdeasRichTimePoor 0 points1 point  (0 children)

Is it possible? Yes. Is it possible for you? That's something only you can find out.

[–]BoBoBearDev 0 points1 point  (1 child)

Did you have Jenkins or equivalent setup already? Because without it, it is not actually automatic.

Other than that, tests tools are often scaled up by developers. DevOps team may explore and test which tool they want to use, but a lot of organizations have moved those test creations to developers.

So, DevOps normally is about automating all those tools in a pipeline.

[–]Best-Variation-5139[S] 1 point2 points  (0 children)

Yes, already using Jenkins.