As a #software #developer, you must deal with #git repositories. But depending on the team, you may find two kinds of strategies: #multirepo or #monorepo
What is that about? 🧵

Where may you find multirepos?
Most likely on distributed systems, a microservices architecture, and where the #frontend apps are not that coupled with #backend services.

What are the challenges of multirepos?
Versioning: the team will get to a point where they will need to be very careful on how to manage each app version and its compatibility with the other apps or services

Testing: the team will also need more repos to develop the testing tools. e2e tests, performance, or any other test type that runs over the whole system will be in yet another repo.

What are the challenges of monorepos?
Probably versions are not that hard to manage because basically "everything" will have the same version.
Same for testing, just another folder or module on the same repo to develop all the test types the team will run.

But monorepos are prone to the coupling between apps or services. The team will need to be very careful with the branch strategy to avoid conflicts and coupling.

Also the build pipelines will need to manage exceptions or conditions. You don't want the whole system to be rebuilt on any change.

They are just different strategies. There is no one better than the other. So be aware of what you can find when joining a new team. And get ready to know the reasons behind the decision made.

About repositories

As a #testautomation engineer, do I need to be familiar with #DevOps?

Yes!...and this is why... 🧵

🐳
#docker
You need to know how to run a container or either build an image of your test runner.
You may need to launch a local environment of your app under test. Better to know what `docker-compose` is and how it works.

⚙️
#ci tools
Your tests may run on #Jenkins, #GitHub Actions, #GitLab CI, #Bitbucket pipelines, or anything else. So, better to know how they work. And it is strongly related to #docker.

☁️
#cloud providers
AWS, GCP, Azure...
Probably your team has it's own CI infrastructure there. Most likely the environments are there. Don't hesitate to get familiar with the cloud services that support your testing runs.

⛰️
#terraform
A good cloud implementation may be based on infrastructure as code. Basically scripts that automagically spin up cloud instances. e.g. on demand environments. You may need to make sure the terraform scripts include your tests commands.

Do you think there are other #DevOps concepts or tools a #testautomation engineer would need to be familiar with?
Feel free to reply!
Thanks for reading!
🤓💭🔍

Knowing DevOps as a Test Automation Engineer

@playwrightweb #VisualTesting is awesome.
Take a look at this approach.
It does not only save some lines of code.
It can also catch CSS issues like color changes or elements alignment that the toBeVisible function cannot.

Here is an example.
I tweaked the expected sign-in form on the SauceDemo website so the test failed the visual comparison.
#Playwright created three files so you can easily see what is the issue. Would this have been caught by toBeVisible only?
Check the diff file! 😍

Explore it further here!
https://playwright.dev/docs/test-snapshots