1.what is manual testing?

Manual testing is the process of testing the software manually to identify the
bug, issues and defects in the software product.

1.a.Difference between bug,defect & error?

A mistake in coding is called Error, error found by tester is called Defect,

defect accepted by development team then it is called Bug,
build does not meet the requirements then it Is Failure.

2. software testing concepts:-

software:- A set of programmes which performs a setting or certain task.

Software development life cycle process(SDLC) - it is a end to end process or step

by step process

Requirement-->Design-->Coding-->Testing-->Deploy the software to the customer.

(RDCTD)

Difference between project and product?

product based companies - develops the software based on the market requirements
service based companies - develops the software particularly for the client.
(project)

3.Software testing life cycle:-

test planning--> writing test cases-->Execute text cases --> reporting & finding
the defects-->test reports.

Main objective of testing:-

1.we should always deliver quality product to the customer.
2.we have to find as many defects of the product.

Testing is an activity ,to find defects in the software.

4. Types of Testing:-

white box testing

Black box testing
Grey box testing

WBT :- developer will execute the complete white-box testing for the particular
software and send the specific application to the testing team.
it is also known as open box or glass box or clear box testing.(check the
internal logic of the programme)

Unit testing and Integration testing are done by developers.

UT:- It is often done by the programmer by using sample input and

observing its corresponding outputs.
Unit testing, a testing technique using which individual modules are
tested to determine if there are any issues by the developer himself.
It is concerned with functional correctness of the standalone modules.
The main aim is to isolate each unit of the system to identify, analyze and
fix the defects.
 IT:- Integration testing is testing in which a group of components is
combined to produce output.
Upon completion of unit testing, the units or modules are to be
integrated which gives raise to integration testing.
The purpose of integration testing is to verify the functional,
performance, and reliability between the modules that are integrated.

BBT :- black box testing is a process of checking the functionality of an

application as per the customer requirement.
The source code is not visible in this testing; that's why it is known as
black-box testing.

BBT divided in to two types:- 1. functional testing

2. Non-Functional testing

System testing:-
System Testing is a level of testing that validates the complete and fully
integrated software product.
system testing is done by testers and testers comes under system testing.
system testing is nothing but end to end testing.
system testing consists of both functional & non functional testings.

User Acceptenance testing:- After completion of testing, when we hand over to the
customer and he do the testing.
once the UAT is successful ,then only customer deploy in to the live environment.

In functional testing, all the components are tested by giving the value, defining
the output, and validating the actual output with the expected value.

5. Bug life cycle:-

Defect Life Cycle or Bug Life Cycle in software testing is the specific set of
states that defect or bug goes through in its entire life.

NEW

ASSIGN

OPEN --->REJECTED/DUPLICATE/DEFERRED

REOPENED <-- TEST

VERIFIED

CLOSED
6. functional testing:-

Build:- it is nothing but an integrated product.

A developer create a no of programmes and they dont provide to the QA(Quality
assurance) team or testing team .testing team dont test the programmes.
They test the software completely, so they need an built.

1.Smoke testing:- it is a intial level testing which verifies the critical

functionality or when the software is unstable.
2.Sanity testing:- Verifies new functionality,when bug fixes in the build.

sanity and smoke testing done at the same time ,whenever u recieved the build
from the developer.The difference is smoke testing
is done at intial level and sanity testing is done at later level.

3.Re-Testing:- Testing only the particular change again and again after the
bug is fixed.
4.Regression testing:- The purpose of Regression Testing is that new code
changes should not have any side effects to existing functionalities
5.End to End Testing:“End-to-end testing is a methodology used to test
whether the flow of an application
is performing as designed from start to finish.

6.In system, testing Product is tested against the requirement specification

while at the end to end testing, testing is done as per the business requirements.
In system testing covers all functional and non-functional aspects while in
end to end testing covers end to end flow.
System testing executed when Integration testing is done while end to end
testing executed after system testing.
Manual and automation both testing is performed in System testing while in
end to end testing automation is complex to perform.
Hence manual testing is preferred.

7. Diff b/w Adhoc vs Monkey vs Exploratory testing:-

These all are comes under random testing.
no need of documentation
it is a informal testing.

7. NON-functional testing:-

1.globalization and localization testing

2.stress testing - process of putting a system through stress.
3.load testing - understand the behaviour of the application under a
specified load.
4.user interface testing - checking the design of the application.
5.usability testing - whether the application is user friendly or not.
6.performance testing - to determine how fast some aspect of a system
performs under a particular workload. “
7.security testing - check that whether the application or the product is
secured or not.
8.Compatibility Testing: This type of testing helps find out how well a
system performs in a particular environment that
includes hardware, network, operating system and other software etc.
9. Installation Testing: “Installation testing is performed to ensure that all
necessary components
are installed properly and working as per the requirements of the software,
post installation.
10. Recovery Testing: “Recovery testing is done in order to check how fast and
better the
application can recover after it has gone through any type of crash or
failure.
11.GUI Testing is a software testing type that checks the Graphical User
Interface of the Software.
The purpose of Graphical User Interface (GUI) Testing is to ensure the
functionalities of software application
work as per specifications by checking screens and controls like menus,
buttons, icons, etc.

8. TEST PLAN:-

Test Plan is a dynamic document. Test Plan is more or less like a blueprint of
how the testing activity is going to take place in a project.

A test plan includes a product description, objectives, testing strategies,

scope, schedule, procedures, testing resources, and deliverables.
Test plans are essential in the development of software as they outline what
testing needs doing to ensure the software is up to standard and
is working exactly how it should.

test planning:- how to test , what to test, when to test

test desigining
test execution
defect reporting/tracking
Test closure / sign off

Use case describes the functional requirement.(prepared by business analyst)

test scenario :- possible area to be tested.(what to test)
test case:- step by step procedure of a functionality,(how to test)
test suite :- it is a group of test cases which belongs to same category.

Requirement traceability matrix:-it is a mapping between requirement and test

cases.

test bed:- it is a software development environment. it allows the developers to

test their own modules without affecting the live production service.

test environment:- which is used to execute the test cases

test execution:- test cases, test data, test plan or test strategy.

test cases:-

AGILE PROCESS:-

Agile testing refers to a software testing practice that follows different

principles of agile software development.
Agile testing requires continuous interaction between developers, customers,
managers, stakeholders, and testers.
Testing is an important component of each phase of the developmental process.

testers and developers go parallely.

 Epic:- epic is a large level requirement.(define the business needs)
story:- it is a smaller level requirement.(define the customer needs)
epic divided in to story
task is an action that has to be performed on that story.

Agile roles:-
product owner -- responsible for getting the requirements from the
customers/stake holders.
define the features of the product.
decide on release date and content
priortize features according to market
adjust features and priority
accept or reject work results.

Scum master:- who will drive the complete agile process.

he is not a developer,manager or QA or a tester.

Scrum team:- devdelopers + QA comes under one team.

DOR :- definition of ready

DOD :- definition of done.

product backlog - this is prepared by product owner which contains requirements

which are given by the customer.
it contains the complete stories.

sprint planning
sprint/iteration

story point-an estimation given by tester and developer for the specific story.
the estimation time is given in fibonaic series

sprint backlog:- contains the committed stories.

scrum meeting for 15 mts a day

sprint retrospective meeting will be held after the completion of first sprint.

Advantages:-
we can save time and cost of the project.
the quality can be ensured bcoz each sprint is tested multiple times
requirements can be changed at any time

managing agile process:-

create backlogs
create sprints
tasks
update story stary in scrub board

write test cases

execute test cases update the status of the test cases

JIRA:-
JIRA is a software testing tool developed by the Australian Company Atlassian.
It is a bug tracking tool that reports all the issues related to your software or
mobile apps.
The word JIRA comes from the Japanese word, i.e., "Gojira" which means Godzilla.

two tools are there

test management tools
bug reporting & tracking tools

Agile tools
- JIRA
-version one
-teamcity

jira is a purely agile management tool.

Agile scrum activities--

1. how to create a project in jira.

2. how to add users/people in jira

Backlog--->Epic--->stories
create sprint-->Add stories to the sprint-->start sprint-->add tasks for every
story

3. how to create backlog--> Epic

each and every object considered as a issue type(story,task,epic,bugs)

4. how to create stories in jira & add story points(rough estimation for
particular story)
5. how to create sprint
6.adding user stories to the sprint
7.starting sprint
8. adiing sub-tasks to stories
9.sprint life cycle

TEST MANAGEMENT ACTIVITIES:- (Zepyre)

1. test cases
2. test cycle
3. update test cases passed/failed/blocked
4. report bugs
5. reports

how to create a test case in jira manually.

how to import multiple test cases in jira

creating test cycles

add test cases to cycle
execute/update test cases
reports in zephyr
traceability matrix
GIT:-

git is a local reprocity.

Questions:-
1. what is the difference between SDLC & STLC?
SDLC- software development life cycle
STLC- software testing life cycle

SDLC - requirement-->design-->coding-->testing-->deployment of software to

the customer. (RDCTD)
STLC - requirement-->test planning-->test case development--> environmental
set up-->test execution-->test cycle closure (rttett)

SDLC is mainly related to software development.

STLC is mainly related to software testing.
Besides development other phases like testing is also included.
It focuses only on testing the software.
In SDLC, more number of members (developers) are required for the whole process.
In STLC, less number of members (testers) are needed.
In SDLC, development team makes the plans and designs.
In STLC, testing team makes the plans and designs.
Goal of SDLC is to complete successful development of software.
Goal of STLC is to complete successful testing of software.
It helps in developing good quality software.
It helps in making the software defects free.
SDLC phases are completed before the STLC phases.
STLC phases are performed after SDLC phases.

2. difference b/w product & project?

product is nothing but developing the software for the market purpose
project is developing the software for the customer/client purpose.

3.what is v-model?
4. what is the difference between QA & QC?

Input domain testing uses a minimum number of inputs to check the output of a
system.
The purpose of this process is to prove that the tested system will accept only
certain
inputs that lie within the acceptable range. The system is expected to deliver the
required outputs only and block any invalid input values.

Database Testing is a type of software testing that checks the schema, tables,
triggers, etc. of the Database under test.
It also checks data integrity and consistency.
Database Testing is Important in software testing because it ensures data values
and information received and stored into database are valid or not.
difference between load & 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

Ad Hoc Testing implies learning of the software before its testing. During
Exploratory Testing, you learn and test the software simultaneously

When to conduct Adhoc testing :

When there limited time in hand to test the system.
When there is no clear test cases to test the product.
When formal testing is completed.
When the development is mostly complete.

When should you use exploratory testing? Exploratory testing is suited for specific
testing scenarios,
such as when someone needs to learn about a product or application quickly and
provide rapid feedback.
It helps review the quality of a product from a user perspective.

End To End Testing is a software testing method that validates entire software from
starting to the end
along with its integration with external interfaces. The purpose of end-to-end
testing is testing
whole software for dependencies, data integrity and communication with other
systems,
interfaces and databases to exercise complete production like scenario.

A use case is a written description of how users will perform tasks on your
website.
It outlines, from a user's point of view, a system's behavior as it responds to a
request.
Each use case is represented as a sequence of simple steps, beginning with a user's
goal and ending when that goal is fulfilled.

Test Case is a set of actions executed to verify particular features or

functionality whereas Test Scenario is any functionality that can be tested.
Test Case includes test steps, data, expected results for testing whereas Test
Scenario includes an end to end functionality to be tested.

API (Application Programming Interface) testing is a type of software testing that

aims to determine
whether the APIs that are developed meet expectations when it comes to
functionality, performance, reliability and security for an application.