Smoke / Retest / Regression What's the difference?

I first saw the word regression in QA.

The first image in the head is the regression equation.

Because I learned economics and this word is in my study

I took it to a group of friends, and someone said,

"Does this work require that?" 🫠

Different things.

.

🐱 3 words heard every day, but no one explains it.

Smoke / Retest / Regression

When I came in, I nodded.

And then open to find out later what is OK

Today, I would like to summarize in one post.

The important thing is that these 3 words are not divided by difficulty.

But divided by the rhythm done.

.

🐱 Smoke - episode of Just Comes to Hand

When the dev sends me the test, I'm not going to go deep right away.

I'll play quickly and see if I'm ready for the details now.

Is there anything on it, such as not opening that page? The button does not work.

All I did was smoke, no test case.

Just play to see if it's worth continuing.

If you press Play and install it here, send it back first.

Don't waste time chasing the whole set of Tess.

.

🐱 Retest - The original bug said it was solved.

When dev says it's done, I'm going to go back to that defect.

And follow exactly the steps I wrote when I found Bug.

If the result meets the requirements, it can be closed.

But if I still find it, I'll turn the card back to dev.

Ready to paste it in the comment retest and still fail.

This is important. Don't close the leaves because you are considerate.

And do not say hello only personally without writing on the leaf

Because the rest of the team won't see what's going on.

.

🐱 Regression - pre-operational episode

This is the last test round before taking up production.

The heart of it is to check that the unsolved thing still works.

Because the thing that solved Tess was gone at UAT.

But what I actually did, I didn't just test things that weren't solved.

I combined the unsolved flow and the unsolved flow again.

Because this is the last round. If let go, the next person to meet is a customer.

The dress that brought QA was the choice.

The core functions that the team sees as unlikely to affect new things.

I worked for about five days, and I made a team.

As for the number of cases, I don't ask for money because I've seen both many and very few.

The test method will be a long flow like UAT.

.

🐱 And what does it catch?

I caught it, but I don't see it often.

The cycle I remember is part by part. Everything's fine.

When the code is finished, the regression is finalized.

Turns out the client's onboard is unsuccessful.

That wasn't even the one that solved that round.

Luckily, there was a regression round, so caught first.

The solution is finished, then repeated again until passed and then production. 🔖

Without this round, the client will find us instead.

.

Are there any words you've ever misunderstood like me? Comments can tell.

Or where you are. Say hello to ask. Don't be considerate. 🐱

# Move IT line # Softwaretters # Develop yourself # New ending # fyi