Assignment 01:

1. What is software Functional & Non-Functional Testing?

 Functional testing is a type of software testing in which the system

is tested against the functional requirements and specifications.It is
particularly concerned with the result of processing. Also ensures
that the requirements or specifications are properly satisfied by the
application.
 Non-Functional testing is a type of software testing that is
performed to verify the non-functional requirements of the
application. It verifies whether the behavior of the system is as per
the requirement or not. It tests all the aspects which are not tested
in functional testing.

2. What is Regression and Retesting?

 Regression Testing is a type of software testing, which is used to

verify that modifications in the software or the environment have
not caused any unintended adverse side effects.It can be performed
manually or using automated tools.
 Retesting is done to make sure that the bug is fixed and whether
the failed functionality is working fine or not, this is a kind of
verification method followed in the testing field for the fixed
bugs.

3. What all kind Software Testing like (Unit Testing, System Testing,
System Integration Testing, UAT Testing.)?

 Unit Testing is a fundamental aspect of software testing where

individual components or functions of a software application are
tested in isolation.
 System Testing is a type of software testing that evaluates the
overall functionality and performance of a complete and fully
integrated software solution .
 System Integration Testing (SIT) is the type of software
testing that is carried out to perform the overall testing of a
complete system that consists of many integrated components.
 User Acceptance Testing (UAT) is a crucial phase in software
testing where the software is tested in a real-world scenario
 by end-users to ensure it meets their requirements and functions as
expected.

4. What is Test Plan?

 A test plan is a document that consists of all future testing-related

activities. It is prepared at the project level and in general, it defines
work products to be tested, how they will be tested, and test type
distribution among the testers. It serves as the blueprint that changes
according to the progressions in the project

5. What all are Testing Strategies?

 Black box testing – Tests the functionality of the software without

looking at the internal code structure.
 White box testing – Tests the internal code structure and logic of the
software.
 Unit testing – Tests individual units or components of the software to
ensure they are functioning as intended.
 Integration testing – Tests the integration of different components of
the software to ensure they work together as a system.
 Functional testing – Tests the functional requirements of the
software to ensure they are met.
 System testing – Tests the complete software system to ensure it
meets the specified requirements.
 Acceptance testing – Tests the software to ensure it meets the
customer’s or end-user’s expectations.
 Regression testing – Tests the software after changes or
modifications have been made to ensure the changes have not
introduced new defects.
 Performance testing – Tests the software to determine its
performance characteristics such as speed, scalability, and stability.
 Security testing – Tests the software to identify vulnerabilities and
ensure it meets security requirements .

6. What is difference between Smoke Testing, Build Verification Testing

& Sanity Testing.

 Build Verification Teting (BVT) and Smoke testing are both used to
verify software builds, but they serve different purposes.
  BVTs are a superset of smoke tests and exercise basic functionality in
the build more thoroughly.
 Smoke testing checks for the stability of a software build and is
performed before detailed testing.
 Sanity testing is performed after a stable build is received and ensures
that all bugs have been fixed.

7. What are Test Cases?

 A test case is a defined format for software testing required to

check if a particular application/software is working or not. It
consists of a certain set of conditions that need to be checked to
test an application or software. It also consists of various
parameters such as ID, condition, steps, input, expected result,
result, status, and remarks.

8. What is Test Data?

 The set of input values used to run tests on a software program to

confirm its dependability, functionality, and performance is
referred to as test data in software testing. A variety of input
formats are included in test data, such as normal, boundary,
invalid, error-prone, stressed, and corner case data.

9. What is Test Result?

 Test results are the outcome of the whole software testing life cycle
process. The results thus produced offer an insight into the
deliverables of a software project, significant in representing the
project’s status to the stakeholders.

10.What is RTM?

 RTM stands for Requirement Traceability matrix. RTM maps

all the requirements with the test cases. By using this document
one can verify test cases cover all functionality of the application
as per the requirements of the customer. The main purpose of the
requirement traceability matrix is to verify that the all requirements
of clients are covered in the test cases designed by the testers.
11.What IS SDLC & STLC?

 Software Development Life Cycle (SDLC) and Software

Testing Life Cycle (STLC) are important parts of software
engineering. SDLC has a broad scope; it consists of 6 phases:
requirement analysis, design, development, testing, deployment,
and maintenance. Whereas, STLC is a subset of SDLC. It has
Focused scope, specially focus on the testing phase of SDLC. It
also ensure the quality, functionality and reliability of software
through various testing activities.

12.What is Bug life cycle or defect life cycle?

 In the Software Developement process, the Defect Life Cycle is

the life cycle of a defect or bug that it goes through covering a
specific set of states in its entire life .Alternatively ,it is also called
a Bug Life Cycle. The life cycle of a bug typically involves several
stages such as:
New,Assigned,Fixed,Pending,retest,Retest,Verified,Closed,Reopene
d,Duplicate,Rejected,Deferred and Not a bug.

13.What is Verification and Validation?

 Verification is the process of checking that software achieves its

goal without any bugs. It is the process to ensure whether the
product that is developed is right or no. Whereas, Validation is the
process of checking whether the software product is up to the mark
or in other words product has high-level requirements. It is the
process of checking the validation of the product i.e. it checks what
we are developing is the right product.

14.Difference between Use Cases, Test Cases, Test Plan & Business
Scenarios.

 The use case is a diagram that includes sequential actions to

describe the interaction between the role and the system to
maintain a specified objective.
 A test case is a group of conditions under which a tester will
determine whether the developed system is working as per the
expectations or not.
  A test plan is a document that consists of all future testing-related
activities. It is prepared at the project level and in general, it
defines work products to be tested, how they will be tested, and
test type distribution among the testers.
 Business Scenarios a technique used by business analysts to
effectively communicate complex ideas by breaking them into
manageable units They help identify potential issues early on,
allowing for timely adjustments and mitigations during development

15.Difference between Waterfall Model & Agile methodology?

 Agile methodology  Waterfall Model

 It is a continuous  It is a linear sequential

iteration life cycle model to model to develop and test a
develop and test a software software product.
product.

 In this The entire process  The software

of development is divided into development process is broken
sprints down into different phases .

16.What is Jira Tool and what is it used for?

 JIRA is a software development tool used for project

management and issue tracking. It is a popular tool among
software development teams to plan, track, and release software
projects. It is used for the following;
Project Management, Task Management, Agile Planning,
Reporting and Dashboards and Collaboration.

17.What is ETL and Datawarehouse Testing?

 ETL testing is a category of testing practice that refers to Extract,

Transform, and Load Testing in the common data warehousing and
data integration project.
 Datawarehouse Testing is a critical process that ensures the
accuracy, consistency, and eliability of data within an organization's
 data warehouse. This type of testing is essential because it validates
the integrity of data used for analytics and decision-making.

18.What is Black Box testing and White Box testing?

 Black Box testing is a type of software testing in which the tester

is not concerned with the software’s internal knowledge or
implementation details but rather focuses on validating the
functionality based on the provided specifications or requirements.
 White Box testing techniques analyze the internal structures the
used data structures,internal design, code structure, and the
working of the software rather than just the functionality as in
black box testing. It is also called glass box testing or clear box
testing or structural testing.

19.Difference between Manual Testing and Automation Testing.

 Manual Testing  Automation Testing

 In manual testing, the test  In automated testing, the

cases are executed by the test cases are executed by the
human tester. software tools.

 Manual testing is time-  Automation testing is

consuming. faster than manual testing.

 Manual testing takes up  Automation testing takes

human resources. up automation tools and trained
employees.

End of the Assignment-1