1

TESTING:
In Testing Dept There are 2 Types of Testing as below

Testing (QA)

Manual Automation
Testing Testing
To Test
Software
Testing Dept Tester Projects and
Company
Product

Project:
• Project is something which is developed based on Client given Requirements.
• That project is used by that Client only is called Project.

Product:
• Product is something which is developed based on Software Companies Specifications.
• That project is used by multiple uses in the market is called Product.
Note:
• Both Project and Product both are developed by development Dept.
• And Also, both are Tested by Testing Dept. but the usage in the market is different.

Domain:
The Group of the related Projects will come under one class and that class is called Domains.

Departments in software company:

Departments

Development Database Testing Marketing

Networking Dept HR Dept
Dept Admin Dept Dept Dept
1. Development Dept?
Role : Developer
1. Front-End (Angular , jQuery)
2. Back-End (Java, .net ,python
They will write the code to develop the software.

2. Database Admin Dept?

Role : DB Admin (Ms SQL ,MySQL ,oracle )
They will take care of database servers.
3. Testing Dept?
Role : Tester or QA
 2
1. Manual tester
2. Automation tester
We will test the software which is developed by development team.

4. Networking Dept?
Role : Network engineer
They will take care of software and hardware related problems.

5. Marketing Dept?
Role : Business Analyst (BA)
They will take care of getting the Projects into the company and marketing the Products.

6. HR Dept?
Role : HR Associate
They will take care salary related , Insurance related etc, works.

TESTING DEPT
1. What is Testing ?
• Testing is the process in which Defects are Identified and Grouped together and prepare Defect
Profile.
• That Defect Profile is subjected for rectification to developer (Sending to developer)
to ensure that the software is Defect free, In order to provide the Quality Project to Client.

2. What is Defect ?
Defect is defined as deviation from Client Requirements in the software is called Defect.

3. What is Quality ?
Justification of Client requirements in the software and it should add some values(User friendly) in the
software then it is called Quality.
4. Tester Job?
TESTING the software by Identifying the DEFECTS to provide the QUALITY Software to Client.

TESTING METHODOLOGIES
There are 3 types of Testing Methodologies as below
1. Blackbox testing
2. White box testing Note:
3. Grey box testing Structural Part of an Application (Back End Code) ---> Developer
Functional Part of an Application (Front End Application) ---> Tester

TESTING
METHODOLOGIES

Black Box White Box Grey Box

Testing Testing Testing
 3
1. Black Box Testing (Tester)?
• Black Box Testing is done by Tester.
• If one performs the testing on Functional Part of an Application which means (Front End
Application) and without having any knowledge on Structural Part of an Application which means
(Back End Code) This process is called Black Box Testing.
• In simple the testing of Functional Part is called Black Box testing.

2. White Box Testing (Developer)?

• It is done by Developer.
• If one performs the testing on Structural Part of an Application means( Back End Code) and this
process is called White Box Testing.
• In simple way testing of Structural Part is called White Box testing.

3. Grey Box Testing?

• It is done by Developer,
• Developer will develop the software and same developer will test the software which means
developer having the knowledge on Testing and this process is called Grey Box Testing.

SOFTWRE DEVELOPMENT LIFE CYCLE (SDLC)?

Software Development Life Cycle process is done in 6 different Phases as below

1
• Initial Phase (or) Requirement Phase

2
• Analysis Phase

3
• Design Phase

4
• Coding Phase

5
• Testing Phase

6
• Delivery and Maintenace Phase

1. Initial Phase (or) Requirement Phase?

Task: Interaction with Client/Customer and gathering requirements.
Role : Business Analyst(BA) and Engagement Manager(EM)
BA---> Templates (Pre-defined format)
EM---> Prototype (Non-functional application)
Output :
Functional Requirement Specification (FRS)
or
Client Requirement Specification (CRS)
or
Business Requirement Specification (BRS)
or
Requirement Document (RD)
Note :FRS means It’s a Functional Requirement Specification, What Client wants will be described in this
document means Client needs.
 4
2. Analysis Phase?
Input : FRS
Task:
1. Feasibility Study
2. Tentative Planning
3. Technology Selection
4. Requirement Analysis
Role : Project Manager
Process :
1. Feasibility Study
• Feasibility is a detailed study of the Requirement Document
• in-order to check that information is sufficient or not, to develop the Project successfully in
future and process is called Feasibility Study which is done by Project Manager.
2. Tentative Planning
• To develop the Project successfully
• how much time will it may take, these will be analysed by Project Manager that to temporarily.
3. Technology Selection
• List of all Technologies which are required to develop the Project successfully will be analysed in
this section.
Ex:
• Developer ---> HTML , .Net
• Designer ----> UML, XML
• DB Admin ----> RDBMS, SQL
• Tester -----> Manual Testing
4. Requirement Analysis
• What kind of software , what kind of hardware and how much man-power etc., things are
required will be analysed in this section.
Output :
• Software/System Requirement Specification (SRS).
Note: This SRS Document contains timelines related information, Technology related information ,
Budget related information. Etc.,

3. Design Phase?
Input : FRS and SRS
Task:
1.High Level Designing (HLD)
2.Low Level Designing (LLD)
Role : Chief Architect and Technical Lead
Process :
UML- Unified Modeling Language
Chief Architect by using Unified Modeling Language they will divide the complete Project document into
main modules and this process is called High Level Designing (HLD)
And
Technical Lead by using Unified Modeling Language they will divide the Modules into Sub-modules and this
process is called Low Level Designing (LLD).
Output : Technical Design Document (TDD)
Note: This Technical Design Document contain Project Architecture.

4. Coding Phase?
Input : FRS , SRS and TDD
 5
Task : Developing the software by writing the Code.
Role : Developer
Process:
Project is divided into 2 based as below
1. Windows based project
2. Web based project.
1. Windows based project
.exe file (Executable) will be installed in to the system, For this no need to have any internet to
access.
2. Web based project
Web link will be provided, With the help of internet we will access.
Note: To develop the software every company must follow below rules
• Project should contain title
• First letter of the title should be in upper case
• In Project there should not be any GUI (Graphical User Interface) and there should not be any
functional problems.
Output : Build/Software
5. Testing Phase (Software Testing Life Cycle(STLC)?
Input: FRS and Build(Software which is developed by developers)
Task : Testing the software
Role : Tester
Process:
1. We will get the FRS, Start reviewing the FRS, While reviewing if at all any doubts then prepare Review
Report and send to BA.
2. Waiting for Clarifications.
3. One fine day BA will give the clarifications and Updated FRS will be released to Testing Dept.,
4. Now we will review the Updated FRS, If at all any doubts found then update Review Report and resend
to BA, If there were no doubts then start writing the Test Cases and Test Data.
5. Waiting for Build.
6. One fine day Build-1 is released to Testing Dept., Now start executing all test cases in that Build.
7. If at all any Defects found then prepare Defect Profile and send to Development Dept.,
8. Waiting for next Build.
9. One fine day Developer will fix those defects and released the next Build called Build-2 to Testing Dept.,
10. Now we will Re-Execute all Test Cases in that Build, If at all any defects found then update the Defect
Profile and re-send to development Dept.,
11. This process will be continuous till the software is Defect Free.
Output : Quality Software
6. Delivery and Maintenances Phase?
Input : Quality Software
Task : Installing the software in Client location
Role : Deployment Engg.,/ Network Engg, Project Manager, Development Lead and Test Lead.
Process:
Development Lead will create guidelines document to install the software, Now Network Engg with the
help of guidelines document they will install the software in Client Location.
While installing the software if at all any technical problems faced by network engg then
Development Lead will take care of those problems.
Maintenances Phase:
In future if at all Client wants any changes then software company is ready to do those changes with cost.
Output: Good (like name and fame).
 6

End of SDLC
SORTS OF TESTING?
1: Un-Conventional Testing
2: Conventional Testing
There are 2 Levels of Testing as below?

Testing Levels

Static Level Dynamic Level

Testing Testing
Unit Level Testing

Module Level Testing

Integreation Level Testing

System Level Testing

User Acceptance Level
Testing (UAT)

1. Static Level Testing (Sr and Jr Tester)?

• Without performing any actions on the application just by viewing the application testing is done
which is called Static Level Testing.
Ex: GUI (Graphical User Interface) and Document Review.
2. Dynamic Level Testing?
• With performing some actions on the application testing is done which is called Dynamic Level
Testing and this Dynamic Level Testing is divided into sub-parts as below
 7
1. Unit Level Testing?
• It is done by Developer, Unit is the small part of complete Project,
• IF one performs the testing on that small part that process is called Unit Level Testing which is done
by developer in coding side.
• Once Unit level testing is done now all units grouped together some modules and sub-modules will
be ready. Those modules will be released to Testing Dept., now Tester will perform Module Level
Testing.
2. Module Level Testing (Jr and Sr Testers)?
• Group of related functionalities to perform one major task is called Module
• if one performs the testing on that Module is called Module Level Testing which done testers by
writing Test Cases and Executing Test Cases testing will be done.
• Once we confirm this module are working fine now we will send back these modules to
Development Dept., now developer will perform Integration Level Testing.
3. Integration Level Testing (Developer)
• Joining one module to another module with the help of some interfaces and developer will test that
interface is working fine or not and this process is called Integration Level Testing which is done by
developer in coding side.
• Note: Interface means internal code which is written by developer to join one module to another
module.
• Once Integration Level Testing means complete Project is ready and it is released to Testing Dept.,
Now Tester will perform System Level Testing
4. System Level Testing (Sr. Tester)?
• Once complete Project is ready that Project will get installed in one single system and testing the
flow of the Project is called System Level Testing.
• With this System Level Testing we confirm Project is Quality that Quality Project before released to
Client we will perform User Acceptance Level Testing (UAT).
5. User Acceptance Level Testing (UAT) (Test Lead)?
• Complete Project in the present of Client in Software Company location testing the flow of the
Project is called User Acceptance Level Testing of Alpha Process.
• Complete Project in the present of Client in Client location testing the flow of the Project is called
User Acceptance Level Testing of Beta Process.
SOFTWARE DEVELOPMENT MODELS (SDM)?
Software Development Life Cycle will be processed in one model, Model will be selected by Management
based on Client given Requirements and based on usage of the software by Client and based on Client
mind set , Management will decide which model need to be used.
In the market there are different types of Models some of as below.

Waterfall
Model
Prototype
Agile Model
Model

SDM
Evolutionary
Model

V-Model
Fish
Model
 8

1. Waterfall Model?
• When Client gives clear requirements and not changing the requirements in the middle of the
project development process then this model is used.
• The name of this model is Sequential software development model.
2. Prototype Model?
• Prototype means non-functional application.
• When Client givens un-clear requirements and keep on changing the requirements then this model
is used.
3. Evolutionary Model?
• When Client gives clear requirements and changing the requirements at the end of project
development process if needed then this model is used.
4. Fish Model?
• If the Project is under risk based then this model is used, Risk based project means some scientific
related software's some defence related software, banking related software's will come under risk-
based projects.
• In this model Client can give the changes anywhere in the middle of the Project development
process and in this model Quality Assurance people will involve.
5. V-Model?
• V-Stands for Verification and Validation.
• Verification means one level of implementation process with Group Dept.,
• Validation means only testing process in testing dept.,
• If Client wants the software within short period of time then this model is used and in this we may
implement less modules contain projects.
• In this both the works called Verification and Validation done Parallel.
6. Agile Model?
• In this model Client is also one of the Role in Software Company, So in this model there is a face-to-
face communication between Client and Team members in Software Company.
• In Agile Model Project will be divided into Time boxes which means small time frames to deliver the
Project within short period of time.
• In this Model Project is released into small Incremental builds which s called as Iteration process or
Scrum process.
• Every Iteration involves cross functional team working simultaneously on various areas like Initial
planning, Requirement Analysis, Designing, Coding , Testing and Delivery and Maintenance.
• In this model Project will be Tested very frequently through the release Iterations.

SOFTWARE TESTING LIFE CYCLE

• Software Testing Life Cycle will be processed in 6 different phases as below:

Test Test Result Bug/Defect Defect

Test Plan
Development Execution Analysis Tracking Reporting
Phase
Phase Phase Phase Phase Phase
 9
1. Test Plan Phase
Test Plan is one Strategy Document (or) Narrowly defined Document
1) which describes how to test the Project in an effective way to provide the Quality Project to Client.
Test Plan is prepared by Test Lead
Test Plan will be approved by the Project Manager and released to Testing Team members.
Index of Test Plan
1. INTRODUCTION
1.1 objective :- The main purpose of the project means what exactly the project is will be described
in this section.
1.2 Reference Documents :- List of all documents which are used by test lead to prepare Test Plan
will be described in this section
2. COVERAGE OF TESTING
2.1 Features to be Tested :- The modules which are need to be tested within the scope will be
described in this section.
Ex Module-1: Login Order
Module-2: Flight Reservation
Module-3: Open Order
2.2 Features not to be Tested The modules which are no need to test at this point of time which
means out of scope will be described in this section.
EX Module-4: Fax Order
3. TEST STRATEGYS
3.1 Types of Testing :- List of all Types of Testing which are required to test the project will be
described in this section. This topic before end of manual testing we will discuss)
3.2 Test Design Techniques To test the project, we required some input or test data, To prepare
that input or test data we need to follow below 2 Test Design Techniques.
Boundary Value Analysis (BVA)
Equivalence Class Partitioning (ECP)
3.3 Configuration Management
It’s a storage or server location where projects related all files will be stored in this server.
3.4 Terminology’s
List of all Terminology’s which are used in the company will be described in this section.
3.5 Levels of Testing
List of all Levels of Testing which is followed in testing dept will be described in this section.
EX:
1. Static Level Testing
2. Module Level
3. System Level
4. User Acceptance Level Testing
5. Automation Plan
3.6 Automation Plan
List of Modules which may take more time to test in manual and that modules need to move to
test in tool called automation testing tool. And modules will be described in this section.
3.7 list of Automation Tools
List of automation tools which are running in software company will be described in this section
4. BASE CRITERIA
4.1 Acceptance Criteria (Entry)
4.2 Suspension Criteria (Exit)
4.3 Acceptance Criteria (Entry)
When to accept the project means on which situation we need to accept the project for testing will
be described in this section.
EX : If Application is stabled then we can accept
 10
4.4 Suspension Criteria (Exit)
When to reject the project means on which situation we need to reject the project will be
described in this section.
Ex: If application is not even opens , In Application major functions are not provided then we can
reject.
5. TESTING WORK DELIVERABLES
5.1 Review Report
5.2 Test Case
5.3 Test Data
5.4 Defect Report
5.6 Status Report
6. PROJECT ENVIRONMENT (Developer Job)
6.1 On which Environment current Project is running will be described in this section.
Ex: Client-Server
7. PROJECT MODEL
7.1 On which Model current Project is running will be described in this section.
Ex: Agile Model
8. SCHEDULING
8.1 When to start testing and when to end testing means starting and ending dates will be provided
in this section.
EX: Duration 2 Months
Starting Date : 1-7-2022
Ending Date : 1-10-2022
9. STAFFING AND TRAINING
9.1 How much staff we required and if needed what kind of training need to be provided will be
described in this section.
Ex: Staffing - Team Size : 9
Sr Testers - 6
Jr Testers - 3
10.RESOURCE PLANNING
10.1 Who has to do what kind of work means which role has to do what kind of work will be
described in this section.
Ex: Test Lead has prepare Test Plan
Sr Tester has to prepare Review Report , Test Cases
Jr Tester has to prepared Test Cases and Test Data
11.RISK (Problem) AND CONTINGENCIES (Solution)
11.1 What kind of problems we may face in current Project and what solution need to be used
for that problems will be described in this section.
12.APPROVAL INFORMATION
12.1 Who has to approve what kind of work will be described in this section.
Project Manager has to approve - Test Plan ( Test Lead)
Test Lead has to approve - Test Cases , Defect Profile ( Sr Tester / Jr Tester)
Sr Tester will approve Jr Tester works
FAQ : Provide few points which are used in your current Test Plan document ?
For this Any 3 to 4 topics of above.

End of Test Plan

 11
2. TEST DEVELOPMENT PHASE
In this Phase we will prepare Review Report if needed and write the Test Cases and Test Data.
Working Process.
Step-1 : We will get an email as below
New FRS is ready for QA.
FRS is available in VSS.
File location: \\VSS\Flight Application\Testing\Documents\Login.frs
Please continue testing and update the status by tomorrow EOD.
Thanks, Anitha
Step-2 :Enter into the VSS and get the FRS then start reviewing the FRS, While reviewing if at all
Any doubts found then prepare Review Report and send to Business Analyst(BA).
To review the FRS we need to follow below Pre-Conditions
1: Text Field : It is used to enter input data or test data.
A: What kind of data need to be enter (Eg: Alphabets / Numbers / Spl chrs ...etc.,)
B: How much data need to be enter (Eg: Range like min 4 to max 8 )
C: Is this field is mandatory or not (means required field or not)
In FRS document there should not be any incomplete information and there should not be
any spelling mistakes and also there sould not be any missing information...etc.,
Review Report Template
S.No- Its a numerical order number like 1,2,3 ...etc.,
Page number- On which page we have doubt that page number will be provided.
Eg: Page of 20.
Field names and other information - On which filed we are having doubt that field name will
be provided.
Eg: OK Button
Tester Comments / Description - What is our doubt will be provided.
Attached File - YES or NO, YES means attaching the FRS throught email and NO means not
attaching
Send Date- On which date we are sending that date will be provided
Author comments (BA)- It is used by BA.
Step-3: Once we prepare review report and send to BA, Now we are waiting for clarifications.
Step-4: One fine day BA will give the clarifications and Updated FRS will be released to Testing
Dept.,
Stpe-5: Start reviewing the Updated FRS, If there is no doubts then perpare Test Cases and Test
Data.
Step-6 Test Case(TC)Test Case is an idea of a tester to test the Project.Different company's will
follow different ways/style to write the test cases.
Note-1:
With the help of Updated FRS and by following some scenarios we will write the Test Cases.
Note-2:
While we are writing test cases on that time there was no application is released so we just assume
and write the test cases.
Note-3:
Once application released we can change the test cases if needed, Or no need to change if
meaning is correct.

TEST CASES

GUI FUNCTIONAL
 12
1. GUI Test Case (Graphical User Interface)
Without performing any actions on the application just by viewing the application testing is done
which is called Static Level Testing and this testing with the hlep of GUI Test Cases we will do.
1. To write the GUI Test Case we need to follow below Scenarios.
2. Open the application.
3. Check the availability of all fields in application.
4. Check the Alignment, Font size, Font style, Images, BG Colour etc., in application.
5. Check the Consistency of all fields in application.
6. Check the Spelling mistakes in application.
7. Check the Tab Order.
8. Check the Cursor focus.
Test Case Template
1. S.No- Its a numerical order number like 1,2,3,....etc.,
2. Test Case ID- It is also numerical order number with lable names. Eg: TC_1.1_Login.
3. Test Description- Its a functional level term, What acation need to be performed on the
application will be described in this section.
4. Expected Result- Based on action what Client is expecting will be described in this section.
2. Functional Test Case
With performing some actions on the application testing is done and this process is called Dynamic
Level Testing and this dynamic level testing with the help of Functional Test Cases we will do.
1. To write the Functional Test Case we need to follow below Scenarios.
2. Entering Valid data and testing is done (+Ve Testing)
3. Entering Invalid data and testing is done (-Ve Testing)
4. Without entering any data testing is done (Blank Testing)
5. Combination of all above testing is done (Combination Testing)--> This with button
functionalities we will do
Note-1:
Alphabets - (A to Z) & (a to z)
Numbers - (0 to 9)
Special Chars - !@#$%^&*&
Project Name : Employee Information Form
Requirements :
1. First Name-Its a text field and it should allow only alphabets and its a required field.
2. Middle Name-Its a text field and it should allow only alphabets and its Not a required field.
3. Last Name-Its a text field and it should allow only alphabets and its a required field.
4. Save Button- Once we enter all valid data and click on save button, Data should save in
database
5. Clear Button- Once click clear button data should get clear.
Valid data ---> Alphabets ( A to Z) and (a to z)
Invalid data ---> Numbers and spl chrs