QA Basics

- Difference between QA/QC and Testing

QA is about engineering processes that assure quality is achieved in an effective and efficient
way.
QC is the function of software quality that determines the ending result is what was expected.
Testing is a subset of QC. It is the process of executing a system in order to detect bugs in the
product
so that they get fixed.

************************************
- Levels of Testing

1-Unit Testing :
checks if software components are fulfilling functionalities or not.
2-Integration Testing :
checks the data flow from one module to other modules.
3-System Testing :
evaluates both functional and non-functional needs for the testing.
4-Acceptance Testing :
checks the requirements of a specification or contract are met as per its delivery.

**************************************
- Diff between Black Box, White Box and Grey Box Testing

Black Box:
It is a way of software testing in which the internal structure or the program or the code is hidden
and nothing is known about it.
White Box:
It is a way of testing the software in which the tester has knowledge about the internal structure
or the code or the program of the software.
Grey Box:
It is a way of testing the software in which the tester has Partially Knowledge of the internal
working structure.

**************************************

- Diff between Functional and Non Functional Testing

Funcional Testing:
Functional testing is a type of testing which verifies that each function of the software application
operates in conformance with the requirement specification.
Non Functional Testing:
Non-functional testing is a type of testing to check non-functional aspects (performance,
usability, reliability, etc.) of a software application.

***************************************
- Functional testing types

Unit Testing:
Unit testing ensures that each part of the code developed in a component delivers the desired
output.
Component Testing:
Testing a module or component independently to verify its expected output
Smoke Testing:
Smoke testing is performed on the ‘new’ build given by developers to QA team to verify if the
basic functionalities are working or not.
Integration Testing.
Integration testing is performed to test individual components to check how they function
together.
Regression Testing:
Regression testing is performed to make sure that a change or addition hasn’t broken any of the
existing functionality.
Sanity Testing:
When a new build is received with minor modifications we perform a sanity test.It determines
that the modifications have actually fixed the issues and no
further issues have been introduced by the fixes.
System Testing:
System testing is testing conducted on a complete, integrated system to evaluate its compliance
with the specified requirements.
User Acceptance Testing:
In UAT actual software/app users test the software to make sure it can handle required tasks in
real-world scenarios.

*****************************************
- Non Functional testing types

1) Security:
SECURITY TESTING is a type of Software Testing that uncovers vulnerabilities, threats, risks in
a software application and prevents malicious attacks from intruders.

2) Reliability:
Reliability Testing is a software testing process that checks wheather the software can perform a
failure-free operation for a specified time period
in a particular environment.
3) Survivability(Recovery Testing):
Recovery Testing is software testing technique which verifies software's ability to recover from
failures like software/hardware crashes, network failures etc.

4) Availability(Stability Testing):
Stability Testing is a type of non functional software testing performed to measure efficiency and
ability of a software application to continuously function
over a long period of time.

5) Usability:
Usability Testing also known as User Experience(UX) Testing, is a testing method for measuring
how easy and user-friendly a software application is.

6) Scalability:
Scalability Testing is a non functional testing method that measures performance of a system or
network when the number of user requests are scaled up or down.

7) Interoperability:
INTEROPERABILITY TESTING is a software testing type, that checks whether the software can
interact with other software components and systems.

8) Efficiency:
The extent to which any software system can handles capacity, quantity and response time.

9) Flexibility:
The term refers to the ease with which the application can work in different hardware and
software configurations. Like minimum RAM, CPU requirements.

10) Portability:
The flexibility of software to transfer from its current hardware or software environment.

11) Reusability:
It refers to a portion of the software system that can be converted for use in another application.

*******************************************
- Software Testing life cycle
1-Requirement Analysis
2-Test Planning
3-Test case development
4-Test Environment setup
5-Test Execution
6-Test Cycle closure
*******************************************
- Difference between Bug and Defect
If testers find any mismatch in the application/system in testing phase then they call it as Bug
and when developer/Manager accepts it as bug its called defect.

*******************************************
- Difference between Validation and verification
Verification in Software Testing is a process of checking documents, design, code, and program
in order to check if the software has been built according to the
requirements or not. Validation in Software Testing is a dynamic mechanism of testing and
validating if the software product actually meets the exact needs of the
customer or not.

******************************************
- Bug Life Cycle

New:
When a new defect is logged and posted for the first time. It is assigned a status as NEW.
Assigned:
Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the
bug to the developer team
Open:
The developer starts analyzing and works on the defect fix
Fixed:
When a developer makes a necessary code change and verifies the change, he or she can
make bug status as "Fixed."
Pending retest:
Once the defect is fixed the developer gives a particular code for retesting the code to the tester.
Since the software testing remains pending from the testers end,
the status assigned is "pending retest."
Retest:
Tester does the retesting of the code at this stage to check whether the defect is fixed by the
developer or not and changes the status to "Re-test."

******************************************
- What is UAT? Alpha Testing and Beta Testing
UAT is the step that validates the User Story. It ensures the Product Owner’s expectations are
met.
Alpha Testing is a type of acceptance testing; performed to identify all possible issues and bugs
before releasing the final product to the end users.
Beta Testing is performed by "real users" of the software application in "real environment" and it
can be considered as a form of external UAT.
******************************************
- What is difference between Regression Testing and Retesting?
Regression testing is to ensure that changes have not affected unchanged part while Retesting
is done to make sure that the tests cases which failed in last execution
are passed after the defects are fixed.

******************************************
- Smoke Testing and Sanity Testing

Smoke Testing:
Smoke testing is performed on the ‘new’ build given by developers to QA team to verify if the
basic functionalities are working or not.
Sanity Testing:
When a new build is received with minor modifications we perform a sanity test.It determines
that the modifications have actually fixed the issues and no
further issues have been introduced by the fixes.

*******************************************
- UI Testing
This usually means testing the visual elements to verify that they are functioning according to
requirements – in terms of functionality and performance.

******************************************
- Difference between Load and Stress testing
Load testing is performed to find out the upper limit of the system or application. Stress testing
is performed to find the behavior of the system under pressure.
The factor tested during load testing is performance. The factor tested during stress testing is
robustness and stability.

*******************************************

- Test case document knowledge

*******************************************
- Difference between use case and test case
A use case tells how a System will behave or perform a certain task provided the given
conditions and a test case contains the actual test data,
set of instructions to system and expected result of the interaction with system.

*******************************************
- What is test case and test scenario
Test Case is a set of actions executed to verify particular features or functionality whereas Test
Scenario is any functionality that can be tested

*******************************************
- Bug Severity and Bug Priority
Severity is related to standards and functionality of the system; whereas, Priority is related to
scheduling

********************************************

- All testing types definitions

Software Engineering concepts:

- What is SDLC
SDLC is a systematic process for building software that ensures the quality and correctness of
the software built. SDLC process aims to produce high-quality
software that meets customer expectations.
***********************************

- SDLC phases
Phase 1: Requirement collection and analysis
Phase 2: Feasibility study:
Phase 3: Design:
Phase 4: Coding:
Phase 5: Testing:
Phase 6: Installation/Deployment:
Phase 7: Maintenance:
************************************
- What are models of SDLC?
Waterfall Model
Incremental Model
V-Model
Agile Model
Spiral Model

***********************************
- Waterfall and Agile definitions
- Difference between waterfall and agile
************************************
- Agile methadology
AGILE methodology is a practice that promotes continuous iteration of development and testing
throughout the software development lifecycle of the project.

************************************
- What is RAD?
RAD model is Rapid Application Development model. It is a type of incremental model. In RAD
model the components or functions are developed in parallel as
if they were mini projects. The developments are time boxed, delivered and then assembled into
a working prototype.
***********************************
- What is Prototype
A prototype is an early sample, model or release of a product created to test a concept or
process.

***********************************
-What is Retrospective Meeting
A retrospective is a meeting held after a product ships to discuss what happened during the
product development and release process, with the goal of improving things
in the future based on those learnings and conversations.

Learn the basic definitions of other SDLC models just for the idea.