SQA Interview

Q1:

SDLC is complete sw process like requirement gathering, implementation etc. whereas STLC is
Software testing lifecycle. It is a part of SDLC. The activities we perform in testing is design testing,
usecase testing, So STLC is testing process in SDLC.

Q2:

Project is specific to customer requirement

Product is developed on the base of market requirement.

Some are service based companies and some are product based companies like google they make
products acc to market requirements

Q3:

Verification and validation activities will take place. Develpers will develp and SQA team will do
testing.

V-Model contains Verification stages on one side of the Validation stages on the opposite
side. The confirmation and Validation process is joined by coding gradually works in V-
shape. In this manner, it is called the V-Model.
Q4:

QA is quality assurance and QC is quality control

Qa is complete process which QC is focused on testing activity.

QA is invoved I complete software development so QA is a prevention activity so we go w proper

policy. Qa will take entire SDLC oprocess.

QC team will only be involved in the testing’s part so it is a detection activity

Q5:

Unit testing a single progeam or tester

Done by programmer or developer

Q6:

Integraytii testing is comm btw multiple modules. Outpt of 1 modsl is inpout of next. It is internal
white box testing. Developer will perform it

7:

Sys testing tester will test comple functionality. Testerds will do that with respect to customers
reqmnts

8:

Types of sys testing

2 categories

Fuctiuona, UI, DATSBASE , behavious of app, error handling, cookie testing

Non functional: once fuctinality achieved so performace, security testing. They need specifc
environmentrequirement, load, recovery testing

9:

White and BLACK box testing

In white box we test internal logic

Bb we test functional of sys w respect to customer’s requirements we don’t test internal logic

10:
10:

Vetification and validaton:

Verfication is static testing technique. If doc is correct. To ensure if data in doc is Complete and
Correctness. Checks documentation before sw is develped

Validation. Once SW iks ready so we test it if acc to customwr. It is dynamic testing. It is dine aftere
sw is developed.

11:

Aligment, font size, spelling, images is GUI testin. Is app attractive

12:

Input Domain Testing and technique

Test the text box eg if we n eed to enter only number and length 8 then we check if it is being
followed. We verify input boxes.

Equivalence class partioning: What is valid or invalig for eg a-z valid not A-Z,0-9,space

Boundary value analysis: we test range 4-8

13:

Database testing is testing DML.

When we submit data it stores in database. We need toi check id data we are entering actually
getting updated in the database.

14:

Load and stress testing

We increase the size and ckecks speed. For e.d giving excess to 100 ppl is requirement so we starting
by giving access to 10 then 20 so on and check speed

In Load we increase load we give aacess to 10 50 and 100 so we check by increasing load. These 2
are performance testing techniques

What is the purpose of volume testing?

It is also known as Flood Testing. Description: The purpose of volume-testing is to
check system performance with increased volume of data in the database.
15:

Test design techniques:

Bounday value analysis

Equivalence class partioning

Decisiontable

Tasiton diagram

Error guessing

State Transition testing is defined as the testing technique in which changes in input
conditions cause's state changes in the Application under Test

16:

Give examples of above?

17:

Adhoc Testing

Randomly test application we know functionality but don’t have proper documentation. We do
testing randomly.\fter testing is done we can perform it.

18:

Exploratory testing

We don’t know app so we know by exploring the app.

We need to perform it when we don’t have any test cases.

19:Smoke and Sanity testing

In some mainly focus is on te installation part.

We validate login, see GUI, going on next state Sanity testing we test base tyest cases

20:

End to end testing:

Test complete functyionality of app

Login-blance-tranfer-balance so we will write one test case to cover complete functionality

What is end to end testing with example?

Vertical end to end testing is a way of testing an application by breaking it down into
layers, which can then be tested individually.
End to end testing is a type of black box testing

21:
Usecase:
It is requirement given by business analyst
22:
Test case describes how to test
23:
Test scenario describes what to test and tet case describes how to test
Test case and test scenarios are prepared by the test engineer.

--