The difficulty is to be able to debug those, you have to guess.
The difficulty is to be able to debug those, you have to guess.
About the tests, I'm working with both Cypress and Playwright/Vitest to do unit and integration tests.
The most frustrating parts is always with the tests are failing on headless mode but not on UI mode when you debug.
(make me want to smash my head in the wall)
About the tests, I'm working with both Cypress and Playwright/Vitest to do unit and integration tests.
The most frustrating parts is always with the tests are failing on headless mode but not on UI mode when you debug.
(make me want to smash my head in the wall)
I'm guessing you want to focus on the "automation" part.
The biggest difficulty for me was the setup.
Being a Front end dev, I had to get into Jenkins/Docker/Bitbucket Webhook which was all new to me, took me a while and some help to get it working
I'm guessing you want to focus on the "automation" part.
The biggest difficulty for me was the setup.
Being a Front end dev, I had to get into Jenkins/Docker/Bitbucket Webhook which was all new to me, took me a while and some help to get it working
in order to put pair programing practice in your team, I am guessing you need to organize the pair daily, try to mix evenly the pple of your team depending on their expertise and seniority, etc... and for me this also looks quite heavy TBH
in order to put pair programing practice in your team, I am guessing you need to organize the pair daily, try to mix evenly the pple of your team depending on their expertise and seniority, etc... and for me this also looks quite heavy TBH
I don't like the word "trust" here but it mean that you have a team with at least enough senior dev to pair with junior.
If the idea is to review each other or create reliable tests with each feature, can you really trust 2 junior pairing ?...
I don't like the word "trust" here but it mean that you have a team with at least enough senior dev to pair with junior.
If the idea is to review each other or create reliable tests with each feature, can you really trust 2 junior pairing ?...
mixing dev that want to start coding first and fix the errors with dev that wants to spend the first hours reading the docs. This can create frustration and conflicts
mixing dev that want to start coding first and fix the errors with dev that wants to spend the first hours reading the docs. This can create frustration and conflicts
But you only scratch what I consider blockers for Pair Prog.
1 / You need your team to have pple skills :
We are talking of 2h to full days of pair with someone on your back, it can be intimidating or exhausting.
But you only scratch what I consider blockers for Pair Prog.
1 / You need your team to have pple skills :
We are talking of 2h to full days of pair with someone on your back, it can be intimidating or exhausting.
I'm looking forward to try it, thanks for all the effort
I'm looking forward to try it, thanks for all the effort