Manual Testing

Question 1

System Testing

Answer 1

End-to-End, checking how different components are interacting and working together

Question 2

Regression Testing

Answer 2

re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change.

Question 3

Smoke Testing

Answer 3

basic features and functionalities , very high level , making sure build is good for developers to have a a degree of stability

Question 4

Sanity Testing

Answer 4

high level business scenarios , will user be able to login , is navigation ok

Question 5

Unit Testing

Answer 5

usually done by Devs, they are responsible , they test a unit or component, then they give to QA team

Question 6

Integration Testing

Answer 6

• Its like Uber and Uber driver app

* Need to make sure notification from ride requester is sent to the driver

Question 7

Database Testing

Answer 7

checking the database making sure we are able to fetch data from database

Question 8

Whitebox Testing

Answer 8

theres’ an app, I can see code and the methods by writing script

Question 9

Blackbox Testing

Answer 9

cannot see what is written inside the software , pass in input, and get output

Question 10

Grey box Testing

Answer 10

Can see some components but not all

Question 11

Monkey Testing

Answer 11

Just play with application, no idea what the features are, just test it

Question 12

Ad-hoc/Random Testing

Answer 12

go in and randomly test

Question 13

Component testing

Answer 13

only a specific model

Question 14

GUI Testing

Answer 14

Graphic User Interface – making sure buttons, tables, are aligned, sorting is happening, text is not overlapping, column names is not mismatched

Question 15

End to End Testing

Answer 15

launching the browser from complete business flow from beginning to end

Question 16

UAT

Answer 16

User Acceptance Testing –
o Alpha - occurs after all features are developed, have been tested by QA team
o Beta- based on customer feedback

Question 17

Acceptance Testing

Answer 17

to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery

Question 18

Negative testing

Answer 18

ensures that your application can gracefully handle invalid input or unexpected user behavior.

For example, if a user tries to type a letter in a numeric field

Question 19

Happy Path Testing

Answer 19

a well-defined test case using known input, which executes without exception and produces an expected output