💻 QA: A bundle of 13 words to know if you want to survive on the IT team!

Because someone asked for it, today it combines the key words that Software Tester (QA) workers have to find in real life, 13 words, highlighting, digesting, concise, finished reading, understand the process immediately, save for a quick look!!!

Section 1: Planning & Design

1.Requirements (System Requirements): A reef or document explains what this feature needs to do. QA needs to use this as the main reference to check the work.

2.Test Case: A table or guide that we have written about how to press an app or web to use as a Step to check if the system is working in accordance with Requirements.

3.Positive Case (Normal Case): Testing in case of normal use by the user, such as filling in the correct password, must log in successfully.

4.Negative Case (Case is not normal): Testing in case of strange pressing or misinformation to try the system, such as filling in the phone number in letters to see if it will be Er.

5.Error Case (Case in which the system is malfunctioning): Testing to check that the system has failed. You have to manage yourself. For example, try to turn off the internet during the money transfer. See if the app will bounce the user notification correctly, not hold the page.

Section 2: Test Execution

6.Smoke Test (Smoctease): A "quick test" to check the main function after Dave sends the work. Make sure the system is active, not demolished. If you pass through it, you will go through it in detail.

7.Sanity Test (Sanity Test): The test only delves into the point where the code is modified or the bug is fixed.

8. Regression Test (Regression Test): Elephant of the Week! Is to go back to "recheck the entire original system" to ensure that new code or new features are inserted. It does not secretly crash the original system.

9. Exploration Testing (Free Testing): Instinctively pressing random tests without pre-writing Test Cases to find strange bugs that we might not expect.

Section 3: Manage bugs, pour systems and send jobs (Defect & Deployment)

10.Bug / Defect (bug): System error. Anything that does not work according to the reef, such as pressing the checkout button and then the bounce app, or a crooked screen, the keypad does not.

11.SIT (System Integration Testing): Pouring a large version of the system to check that parts or subsystems, when combined and connected, work together correctly.

12.UAT (User Acceptance Testing): The final test with the user, customer or BA / PM team to try to use it to determine that the system is working correctly and ready to use.

13.Deployment / Go-Live (Deploy): Taking the code up. If Dave says "Deploy," it means we have to prepare to wear the spirit of Detective Luitess! Or if Dave says Go-Live, it means the system is going to be open for real users to play.

💡 Trick for Rookie / Move Line:

Newbie or early move. Don't remember all in one day. Focus on understanding the Step. It's necessary: Get Requirements - > Write Test Case - > Luitess (Find Bug) - > Send Bug to Dave - > Dave has finished editing. Deploy is back - > We've done Regression Test. Repeat the loop here. Do it often and talk to the team about it.

Who is studying and find any words other than this that are read and confused again. Stop by to comment, leave a question. I'll come in and answer for you.

# Lemon 8 invites # Before having today # Share experience # Trending # workfromhome