Software Quality Assurance's Basic Vocabulary

-Frequently Encountered Terms in Quality Assurance [part 1]- 

First time trying to work in the Quality Assurance Field? Here is some vocabulary that might come up during the journey of improving your skills. While I made this list not only for beginners to distinguish the terms that are frequently used in the Quality Assurance field, but also for those who have already worked in this field.

1. Manual Testing 

The first term that might be something that is not really strange to the beginner is 'Manual Testing', where manual testing is a test that is done manually by the tester to check from the UI side whether it has been synced with the design that has been planned before, or it can be a functionality manual testing like opening the browser manually and see where the browser direct the user. 

2. Automation testing 

Automation testing is a kind of test where you have to use programming language to navigate a website or apps to do the testing part. This might be an alternative for testers, while we know checking by manual testing is extremely time-consuming. 

3. System Integration Testing / SIT 

Before a software feature is released or delivered to end-customers, a SIT is necessary to make sure that testing for interfaces between modules is done correctly and see how the modules in the code that correlate one to another can work properly as a whole system. 

4. User Acceptance Test / UAT 

In UAT, the real end-user is included in the testing phase, where the aim of UAT as the last phase of testing is to make sure that the software or the software's feature that is going to be released, meets the end-user's requirement and can be a key to the problem that they are facing previously. 

5. Test Case 

The test cases will probably be simplified as a scenario to make sure or validate that every part of the software is running properly and returns a output as expected. Just say as it was stated in the test case that if you click a link then it will redirect you to a google form, then, the result of testing when its performed must be synced with what is stated in the test case. 

6. Positive and Negative test case 

Positive test cases are used when a tester wants to validate a test case by using valid data while the opposite negative test case is used when the tester wants to break the rules or tries to give a invalid input while the testing is done.

Hope this simple vocabulary summary can help to figure out what we really do in the quality assurance field! I will continue with part 2 anyway.