Manual Software Testing!

(1). What is Software ?

Ans. A software is a collection of computer programs
that helps us to perform a task.

Types of Software:-
1).System Software
Exm. Device Driver, Operating system,Servers,utilities etc
2).Programming Software
Exm. Compiler, debuggers,interpreted,etc
3).Application Software
Exm. Web applications , Mobiles Apps, Desktop applications,etc

(2) What is Software Testing?

-------
Ans:- Software testing is part of the software development process.
Software testing is an activity to detect and identify the bugs in the
application.The objective is the testing to release (delivered) quality
products to the client.

Exam:- X Bank (Client)------>IT Company---> Develop----->Test------->Delivery------->X BANK

(3). What is software Quality?

---------
Ans:- 1). Bug free
2). Delivered on time
3). within Budget
4). Meets Requirements and / expectations.
5).Manintanable.

(4). What is the difference between Project and Product?

--------------
Ans. Project:- If a software application is developed for a
specific customer based on his requirement then it is called
Project.
**
Product:- If a software application is developed for multiple
customers based on market requirements then it is called a
product.

(5). Why do we need testing?

-------------
Ans. Testing is used to help detect and identify bugs in the
application.

(6). Difference between Error, Bug and Failure.

-------------------
Ans.(1)Error. An error is a mistake a coder makes during the
software development process (Error is generated by Human).

(2)Bug. Bug is an error that is found by a tester after developing the

application.
(3) Failure. Failure is an error that is found by the client when the
client drives the application.
________________________________________________________

(7). Why does the software have bugs?

-----------
Ans.(1).Miscommunication and no communication:-
(2). Software Complexity (difficult).
(3).Programming Error.
(4).Lake( acknowledge)of skilled Testers.
(5).Changing requirements.
________________________________________________________

(8). What is SDLC ?

-------------------------
Ans. SDLC( Software Development Life Cycle) is the process used by
the software industry to design ,develop and test software required by
clients.

SDLC has three poles. (A) People.

(B) Process.
(C)Product.

SDLC- MODEL:-
(a) Requirements Analyst
(b) Design
(c) Development
(d) Testing
(e) Deployment
(f) Maintenance
Note:- Tester to Developer:- Tester testing the software and finding
the bug from the software and if bug or bugs have in the software.so
tester forward the information about the bug with developer after the
developer fixed the bug and forward the software with tester for
retesting.
________________________________________________________
(8). Waterfall model:- Waterfall model is a software development
model.It is developed in 1970.Waterfall model is the process used by
software industry to design ,develop,testing software required by
client.Waterfall model works like waterfall.Waterfall model develops
the software step by step. after completing the first phase, then
moves to the next phase.

// When starting work at a software application and no feedback till the end to the client between the software development process.//

------------------
Waterfall-model:-
(a) Requirements Analyst, (b) Design, (c) Development (Implements)

(d) Testing, (e) Deployment, (f) Maintenance

Waterfall model Advantages:-

(a).Quality of the project will be good

(b).Base model.
(c). Easy and simple.
(d).Small projects.
(e).Initial investment is less.

Waterfall model Disadvantages:-

(a). Requirements changes are not allowed.
(b).If there is a bug in any phase, it will continue in all phases.
(c).No feedback
(d).Testing will start only after coding.
________________________________________________________
(9):- V-Model // VV model (Verification and validation model):-
 ● V-Model is a software development model.
● V-model work like V -shape shape
● It tests all phases.
● In this model review all phases.
● V-model has two parts: first is verification and second is
validation.
● In verification every phase is reviewed.
● In validation is to test the application.After developing the
application(Product).
● V-model is based on SDLC.

● Verification model:-
● Verification is the documents review process.
● Tester reviews the SRS document.
● Verification works with the SDLC steps.
● First point is requirements discussed with the client and
Business analyst(BA, Developers,QA,Tester) .And BA designs
the SRS.
● Business analyst contains the requirements in SRS.
● After that review the requirement document(SRS)by tester and
team members.And after document reviews,tester writes the test
cases.

NOTE :-
Verification mode has a question:- Are you building it right?

Verification Methods:-

Walkthrough Review:-
 ● Walkthrough in software testing is used to review the documents
with managers and the team members.Who are guided by the
author of the document.
● In this review all the team members review the document. And
match the user's requirements.
● During review of any error in documents.The author notes the
error in the document and fixes the error.

Inspection Review (Formal review):-

Validation model:-
● Validation is the dynamic process .
● Tester tests the final project according to the requirements.
● Tester tests the final product bug free.
● It is tested by the tester or QA and Product manager(Business
analyst) and the QA leader.
● This is only dynamic.

NOTE:-
● Validation mode has a question:- Have you built the right
thing?

Testing types:
● User acceptance testing
● System Testing
● Integration Testing
● Unit Testing
 ● Software Levels of Testing:-

● Unit Testing:- Unit testing is the process of the software

testing.unit testing tests the application in different different
parts.It is tested by the developer.And the developer checks
individual parts that's working or not.
● Exam-Instagram:-
● Login page
● Home page
● Reels
● Photos

These are some different parts in instagram and unit testing

checks these parts individually.

(2).Integration Testing:-
● Integration testing is the process of software testing.
● Integration combines two or more units or modules.
● It tests between two or more software units or modules.
● When the two software units or modules are connected between
then integration tests.
● It is done by the developer or QA.

Exam :- Instagram ➖ Like Instagram has many units in

software.login and password are two parts of an application
if we combined valid user id and password we get new
page . It is integration testing.
 Valid Instagram user id + valid Password==== Home page

Paytm scanner + Upi Barcode == User information

(3).SYSTEM TESTING:-
● System testing is the process of software testing.
● System testing is used to identify and detected the error in the
application
● System testing tests the application end to end.
● During the integration testing, System testing tests the overall
software units that's connected to each other.
● It tests after the application developed by the developer.
● It is tested by the tester.

(4). USER ACCEPTANCE TESTING:-

● User acceptance testing is the process of software testing.
● UAT tests after all the testing levels.
● User tests the application end to end.
● Client tests project according to his requirements.
● Client checks the application and knows all functions working or
not.
● UAT tests when the application is released with the client.
● UAT tests by the client.
(10).Agile Model.Agile model is a software development model. It is
the latest model in the software industry. Because it develops the
application in iterations. The main advantage of this approach is that it
helps you launch the software in the initial phase with the minimum

Exam:-Facebook- Facebook is a social media platform.

In facebook :-
1.Login
2.Logout
3.Update
4.Delete
5.Reels
6.Videos
7.Photos
8.Etc
Note:-Facebook is a social media application it has many parts .All
the facebook parts are developed by the software industry but these
are not developed in a single part.It is developed in the form of
iterations. And it is developed according to the market.

Agile Advantages:-
1). Client requirements changes are allowed in any stage of software
development.
2).Software release will be very fast.
3). Good communication between developer, tester and other
company members.
4).It is a very easy model to adopt.
5).Client no need to wait for a long time.
Agile disadvantages:-(1).Less focus on design and documentations
we deliver the software very fast.
________________________________________________________
Scrum:- Scrum is the Framework and through which we will build the
product by the agile principles.

Agile roles:-
1). Sprint
2).Project Owner:- Project owner defines the features of the product.
3).Scrum Master:- The main role is facilitating and driving the agile
process.
4).Developer:- Developer develops the project by coding.
5).Testing:- Tester tests the bug in the application.

Note :- Agile Meetings:-1).Sprint Planning

2). Daily meeting
3).Restroscopy meeting.
—----------------------------
Scrum Technology:-

White-box testing:-White box testing is a model of software testing

that tests internal structure working of an application.The developers
can perform white box testing.and the developer knows about the
software how it does it.

1).Control flow testing

2).Data flow testing
3).Statements coverage
4).Decision coverage
5).Path Testing

Black-box testing:- Black- box testing is a model of software testing

.In black box testers focus on only the input and output of our
product.The tester can perform (black-box )testing without knowledge
of source code and programming.

Black-box testing:- Black box testing is a model of software testing. Tester is performed without knowledge of source code or programming.Test don't
know how it does it

Techniques of black-box testing

___________________________
(1).Equivalence partitioning:-
Equivalence partitioning is a design technique of black box test.It is
used to reduce the test data.It divides input test data into
partitions.and tests only once.

● It is a black box test design technique.

● It is used to reduce the test data.
● We identify the input which reproduces the same output. We put
the same data in a class.
● At the time of testing, we select one test data from each class to
test the application.
● After one test data output we know about the data.It works
properly or not. If one data output has a bug so all class data is
bug full.

Exam:- Facebook user id and password.

User id:- Valid Valid Invalid Invalid

Password:- Valid Invalid Valid Invalid
Is login:- yes No No No
(2).Boundary value analysis:- BVA is a design technique of the black
box test.It is used to reduce the test data.It tests boundary values that
contain the upper and lower limit of a variable.

//Boundary values depend on the +1 and -1.This is the main point of

boundary this is the limit of boundary value analysis.

Exam:-Valid age for Insurance. Age valid 18-60

Invalid valid Invalid
<=17 18-60 >=61
18-1=17 17+1=18 60+1

(3).Decision Table Testing

(4).Error Guessing:- Error guessing is the design technique of the
black box test.The experience tester is used to find the bug in the
application.Error guessing has no rule for testing. And the experience
test works with the developer and tests the application easily.

(5).State Transition Testing

(6).All pairs testing techniques

***********************************************
//Advantages of Black-box testing:- (1).Tester does not need to
have more functional knowledge or programming skills.
(2).It is efficient for implementing the tests in the large system.
(3). Tests are executed from the user's and client point of view.

Disadvantages of Black-box testing:-(1).Without clear programming

knowledge,Test cases are very difficult to implement.
(2).It does not reveal the errors in the control structure.
STLC— SOFTWARE TESTING LIFE CYCLE
STLC :-
● Stands for software testing life cycle.
● It is a process to test the application.
● STLC is used to test the application properly.
● STLC identifies and detects the errors in
application.
● It is tested by the QA and QA leader.
● Tester and QA leader tests the application as
soon as when the SRS is finalized.

Activities of STLC:-

1. Requirements analysis:-
1. Requirements analysis is the first point of
software testing life cycle.
2. In this phase the QA team understands the SRS
like what is to be tested.

2. Test Plan:- Test plan is a planning document and the

test leader prepare it.It is reviewed by the test
manager.once it is reviewed ,QA follows it
for the testing activities.
 Test plan Template content:-

1. Purpose:- The test plan purpose is to define the

testing activities, scheduled approach.

2. Project overview:- QA leader writes the overview

about the application.Overview means short note
about the application.

3. Scope:- Scope types.

(A) In Scope:- Which functionality to test.

Exam:- Flipkart is the exam :- Login ,add

,remove,sign up are tested in the In-scope .

(B)Out-Scope:- Which functionality to not to test.

Exam:- Payment of flipkart in the OUT-Scope.

4. Schedule:- Test plan is scheduled by the QA leader

and decides the Activity Start date and End date of
task.QA leader decides the resource for the task.
 5. Entry criteria:- Specify when to start Tc execution.
(a) App is ready
(b) Unit testing is done.
(c) Test cases are approved by the Qa leader and Qa
manager

6. Exit criteria:- When to stop testing.

(a) All test cases are executed

(b) All bugs are fixed.
(c) App is working as expected.
(d) Schedule is over.

7. Dependencies:- VPN is needed for testing.

8. Risk mitigation plan:-

Risk | Impact | Plan

_______________________________________
(a) QA is on leave | Testing delay |will hire a Qa from another team.

(b) VPN is not working | Testing delayed |

Bug report template:-

1. Bug summary:- Wrong error message is displayed when

username is valid and password is invalid.

2. Steps to Reproduce:-
● Enter valid user name
● Enter invalid password
● Click on the login button

3. Expected result:-
● “Please enter valid username and password”

4. Actual Result:-
● “Invalid credentials” Error message is displayed.

5. Severity:- Impact of that bug on application.

High:- Unable to use application
Medium:-Error message
Low:- Grammatical mistake.
6. Priority:-How urgent to fix this bug.
High:-Immediate
Medium:-Before release
Low:-After release redease

7. Assign:- Developer Name

Severity :-Severity describes how much impact of that bug has
on an application.

Parts of Severity.
● Very high severity:-When nothing can not proceed
further in the application.

Example:- Application is crashed,login not work etc

● High severity:- When the main functionality of the

application can not proceed further.

Example:- when multiple users have problems in

login.

● Medium Severity:- When testing time has the

error message in the application but the
application is working.
Exam:-
 ● Low severity:- When testing time an application has a
minor mistake that is called low severity.That defect
has no impact on the application.

Exm:- Spelling mistakes and other small mistakes is in

application.

Priority:- Priority describes How urgent to fix this bug.

Parts of the Priority:-

● High priority:- When application can not proceed further.
Immediate
● Medium priority:- Before release
● Low priority:- After release

Smoke testing:-
● Smoke testing is generally used for critical
functionality.And the application is working in happy
flow when all cases are tested by the Qa.If application
is not working happy flow.when Qa rejects the
application.
● The main purpose of the smoke testing is to reject the
software application.
● It is tested by the Qa and the developer.

Bug life cycle:-

 ● New:- When the tester creates (reports) the bug for the first
time.
● In progress:-When developer starts fixing the bug.
● Fixed:- When the developer fixed the bug.
● Closed.

Retesting :-When the developer fixed the bug. After that the
tester retests the bug in the application.

Regression Testing:-
● Regression is the type of software testing.
● Regression is used when the developer fixes the bug or
changes in the application so don't impact on previously
working functionality.

Regression Testing:-

● Pass:-Pass cases
● To check if previously working test cases are still getting
pass.

when the developer fixes the bugs and adds new features in the
application.then tester tests all previously passed cases and once
again.It’s called regression testing.
 Types of Testing:-
1. GUI Testing:-
● GUI is the graphical user interface.
● GUI checks the aliments ,colors,Font size,radio
button,Button,Background etc in the application.
● GUI is tested by the QA.
● During the system testing, the tester checks the
GUI.

2. Functional Testing:-
● Functional testing checks the features of the
application.
● Functional testing is used to check if the
functionality is working fine in the application.
● Functional testing is tested by the QA.
● During the system testing.

3. Usability testing:-

● Usability testing tests the application.How easy to use

this application.
● Are application error messages correct and meaningful?
● Is the application guiding the user how to use it?
● To check good UI and good usability.
● Usability testing is tested by the QA.
● During the system testing.
4. Cross Browser testing:-
● Cross browser testing tests applications on different
-different browsers and versions.
● Like -Chrome browser versions-125,126,127.
● During cross browser testing,UI and the Functionality
are working fine or not.
● Cross browser testing is tested by the QA.

5. Database testing:-