suresh_240878@yahoo.

com

Suresh.B –9440163282

Jai Sri Ram Jai Sai Ram Quality Quality means satisfaction of the customer. To define good quality of software, the company people will concentrate on two (2) factors such as 1) Technical factor and 2) Non-technical factor. 1) Technical factor a. Customer requirements in terms of functionalities. b. Customer expectations (Look and feel, Ease of use, right output, speed of processing, security) 2) Non-technical factor a. Low cost to purchase b. Time to market. S.Q.A (Software Quality Assurance) It means monitoring and measuring the strength of development process.
REQUIREMENTS GATHERINGS Business Development People / Business Analyst Business Requirement Specification (BRS) / User Requirement Specification (URS) / Customer Requirement Specification (CRS) ANALYSIS Analyst Software Requirement Specification (S/W RS) FRS Functional Requirement Specification SRS System Requirement Specification HLD High Level Design Document  LLD Low Level Design Document 

DESIGN Designers Design Document CODING Programmers  TESTING Testers  PROJECT MANAGEMENT Release and Maintenance 

Manual Testing  

1

Suresh.B –9440163282

suresh_240878@yahoo.com 

1) REQUIREMENT GATHERINGS: In general software development starts with requirement gathering. In this stage Business Development People (BDP) / Business Analyst People (BA) are preparing Business Requirement Specification Document (BRS) / User Requirement Specification Document (URS) / Customer Requirement Specification Document (CRS), after gathering all required requirements from the user / customer. Business Requirement Specification Document defines the requirement of the customer. 2) ANALYSIS: After completion of Business Requirement Specification Document, Analyst People are preparing “Analysis Document”. This document is also called as “Software Requirement Specification Document” (S/w RS). The document consists of (2) Sub documents such as FRS & SRS (i) FRS It means “Function Requirement Specification”. It defines the required functionality to be used in the project. (ii) SRS It means “System Requirement Specification”. It defines the required Hardware to develop that functionality. 3) DESIGN After completion of Analysis Document, Designers are preparing Design Document. It consists of (2) sub documents, such as (i) HLD & (ii) LLD (i) HLD (High Level Design Document) It is also called as External Design Document. It defines the hierarchy of over all application functionalities in terms of modules from root level to leaf level. Ex: Mail
 

Login Chat Logout
 

2

Manual Testing

suresh_240878@yahoo.com

Suresh.B –9440163282

(ii)

LLD (Low Level Design Document) It is also known as Internal Design Document. It defines the internal logic of every functionality or module in terms of ER Diagrams, Data Flow Diagrams. V - Valid LOGIN User Name Password
IV - Invalid V V V IV IV IV V IV

MESSAGE BOX Please Try Again

OK

CANCEL

 

OK
DATA BASE

INBOX Note: A Project will have one HLD and Multiple LLDs.

4) CODING: A Physical construction of Software is called as “Coding”.
System M1 M2 M3

S1 SS1 P1 P2 SS2 P3

S2 SS3

S3

BUILD

Build: An executable form of all integrated module set is called “Build”. 5) TESTING In this stage, the testers are validating that developed Build with respective Customer requirements and customer expectations. 6) RELEASE AND MAINTENANCE After completion of software testing the Project Management will deliver that software to customer for usage. During utilization of the software, if customer get any problem or if customer want to enhance the application, that can be handled by the company people.
Manual Testing  

3

com  What is the difference between Software Product and Software Application? Software Application If the Software developed with respective particular client requirements or single client requirements that can be called as Software Application.Suresh. What is Error. that can be called as Software Product. Defect: Any mistake found by the tester during Testing can be called as “Defect”. Defect. Operating System etc. Bug? Error: Any mistake in a programme is called “Error”. Ex: Bank Applications. SQC (Software Quality Control) It is a process of validating the Software. Solutions (i) Solid requirements (ii) Good communication (iii) Realistic schedule (iv) Adequate testing (v) Gather / Stick to initial requirements as much as possible. Bug: The reported defect is accepted by developer to resolve can be called as “Bug”. Ex: MS Office. (iv) Unrealistic schedule (v) Inadequate testing. VB. Hospital Applications. 4 Manual Testing . Why Software has Bugs? (i) Poor requirements (ii) Futurities (Customers requirements are frequently changing) (iii) Miscellaneous Communication.. Software Product If the Software developed with respective multiple clients requirements.B –9440163282 suresh_240878@yahoo.

During the review they are concentrate on the below factors. In this. During the review they concentrate on below factors. After completion of analysis document. S/W RS (FRS & SRS) Analysis Design (HLD & LLD) Coding Release & Black Box Maintenance Testing / Functional & System Testing / Close Box Testing Requirements Gathering BRS / CRS / URS Verification Validation Reviews in Analysis Reviews in Design Reviews in Analysis In general Software Development process starts with requirements gathering and analysis. After completion of design document the same category people are conducting reviews in design document for completeness and correctness. designers are preparing design document which includes Functional Requirement Specifications and System Requirement Specifications. Business Development People are preparing Business Requirement Specification Document and Analyst people are preparing Analysis Document with respective to Business Requirement Specification.com Suresh. Manual Testing   White Box Testing / Glass Box Testing / Programe Phase Testing / Open Box Testing Test Software Changes 5 .B –9440163282 TESTING MODELS FISH MODEL Fish model defines the mapping between development stages and Testing stages. i) Are they complete? ii) Are they right requirement? iii) Are they achievable? iv) Are they reasonable? v) Are they testable? Reviews in Design Document After completion of Analysis document and corresponding reviews.suresh_240878@yahoo. the same category people conducting reviews in Analysis Document for completeness and correctness.

. (I) Unit Testing It is also called as Program Testing or Micro Testing. If conditions. c) Program Technique Testing In this testing the programmers are checking the execution speed of the program. a) Basic Path Testing. Unit testing consists of below factors. b) Control Structure Testing In this testing the programmers will concentrate on corresponding program output. After completion of preparing all programs. In this testing programmers are performing wanted changes in the program and executing the program repeatedly.B –9440163282 suresh_240878@yahoo. 1) Draw flow diagram of that program.com  i) Are they complete/ ii) Are they met right requirements? iii) Are they understandable? iv) Does they handle Errors or not? White Box Testing After completion of deign document and correspondence reviews. programmers are conducting “White Box Testing” White Box Testing classified as Two Types such as (I) Unit Testing (II) Integration Testing. 2) Calculate number of independent paths in that program (Cyclometic Complexity) (The number of independent paths in the program) 3) Execute the program more that one time to cover all independent paths in that program. If the execution speed of the program is not good. In this Test repetition. Memory allocation etc. d) Mutation Testing Mutation means changes in a program. then programmers are performing changes in the structure of the program without disturbing functionality. programs with concentrate on coding to construct a Software Build. For loops. In this programmers will concentrate on every statement including.Suresh. 6 Manual Testing . In this interconnection of programs to verify the programs and interface between programs or modules. During this testing programmers are checking that whether the program is running or not? To perform this test they will follow below approach. Unit testing means “Single Program Testing or Component Testing. Programmers are interconnecting them to a system.

it is also called as Called Program. They are (4) Types of approaches. b) Bottom-Up Approach.suresh_240878@yahoo. it works like as under constructive Main Module. Manual Testing   7 . The verification of main module without coming to some of the Sub-Modules is called as Top-Down Approach. a) Top-Down Approach.com Suresh.B –9440163282 Programmers are checking the completeness and correctness of the Test. it works like as under constructive Sub Module. “Conducting test on Sub-Modules without testing on Main Module is called Bottom-up Approach. “Conduct test on Main module without conducting test on some of the Sub-Modules is called Top-Down Approach. Main Module Driver / Calling Program Sub-Module-1 Sub-Module-2 Sub-Module-3 In the above approach “Driver” is temporary program. Programmers are interconnecting to form a system. A=10 B=20 C=A+B msgbox I A=10 B=20 I=A+B C=I msgbox I Perform change Passed (II) Passed Failed (In-compete (Complete Testing) Testing) Integration Testing After completion of dependent program development and corresponding Unit Testing. Driver is also known as Calling Program.” Main Module STUB Temporary Program / Called Program Sub-Module-1 Sub-Module-2 Sub-Module-3 In the above approach “STUB” is a Temporary Program. To estimate the interface between programs or modules programmers are conducting Integration Testing. The verification of Sub-Modules without coming from Main Module is called “Bottom-Up” Approach.

com  c) Hybrid Approach / Sand-witch Approach The combination of Top-down Approach and Bottom-Up Approach is called as Hybrid Approach / Sand-witch approach. when the customer’s requirements are constituent of clear. when the customer’s requirements are not clear or frequently changing. The verification of all modules after completion of all Modules development and corresponding unit testing is called as “Bigbang Approach”. CASE STUDY Case 1: Top-down approach is followable. Case 3: Hybrid Approach is followable. This approach is not suitable for large modules.B –9440163282 suresh_240878@yahoo. 8 Manual Testing . Case 2: Bottom-up approach is followable. Main Module Driver / Calling Program Sub-Module-1 Sub-Module-2 Sub-Module-3 STUB Sub-Sub-Module-1 Sub-Sub-Module-2 Sub-Sub-Module-3 Bottom-Up Approach Top-Down Approach d) Bigbang Approach.Suresh. Case 4: Bigbang Approach is followable. when the customer’s requirements are clear and the architecture structure of the system is changing. when the application build consists less number of modules or less number of interconnections.

Usability Testing is classified into (2) Types such as (a) User Interface Testing (2) Manual Support Testing. Installation Testing. 2) Ok. 3) System Menu existence. Intersystem Testing e. 3) Non-Functional Testing. 1) Usability Testing After receiving build from the development people. a. d. i. Storage Testing. Compatibility Testing c. h. Stress Testing j. b. Load Testing. Ex: The Microsoft (6) Rules for testing 1) Controls are initcaps. a. Sanitation Testing. 2) Functional Testing.suresh_240878@yahoo. User Interface Testing. Cancel existence. a. Configuration Testing. 4) Controls are not overlapped. a. g. Security Testing. b. This separate testing team validates the Software build with respective customer’s requirements and expectations through “Black Box Testing” techniques. Comparative Testing f. Functionality Testing. Recovery Testing. k. b. testers are conducting usability testing to check whether the application build is providing user friendly screens or not.com Suresh.B –9440163282 BLACK BOX TESTING After completion integration of all modules to form a system. Manual Support Testing. Manual Testing   9 . 5) Controls should be visible. It is also known as “Close Box Testing” / “Functional & System Testing” It is classified as (3) types such as 1) Usability Testing. 6) Controls must be aligned. Data Volume Testing. Ease of use of application of build screen. developers are sending that build to the separate Testing team. User Interface Testing During this testing testers are checking the Look and Feel.

Case 1: Receive build from the developers. with respective to Business Operation. 6) Service level Coverage. 2) Input Domain Coverage In this testing Testers are checking whether the input objects / Input fields are taking right type and range of value or not. To perform this test we (Testers) are using (2) Types of Testing. Testers are conducting Functional Testing to validate customer requirements. 5) Back-end Coverage. 1) Behavioural Coverage. 1) Behavioural Coverage. Functional Testing classified into (2) Types (a) Functionality Testing (b) Sanitation Testing. Word Missing. During this testing Testers are checking the context sensitiveness testing.com  b.B –9440163282 suresh_240878@yahoo.Suresh. 4) Calculation Coverage. Manual Support Testing It is also known as “Help document Testing”. In this testing Testers are checking whether the objects are properly responding of not. Grammar mistakes. 2) Functional Testing After completion of User Interface testing.. Ex: Spelling Mistakes. Line Missing etc. 3) Error-Handling Coverage. (i) BVA (Boundary Value Analysis (ii) ECP (Equivalence Class Partitioning) BVA ECP (Range of Object) (Defines Type of Object) Range Expected Actual Result Valid Invalid Pass Min= Min-1= Fail Min+1= Pass Pass fail Pass Max= Max-1= Pass Max+1= Fail 10 Manual Testing . 2) Input Domain Coverage. a) Functionality Testing During this Testing Testers are validating customers requirement in terms of (6) coverage. User interface testing. Usability Functional & Non-Functional Testing Testing Manual Support Testing.

In this User Name object allows “Alphabets lower case” Range from 4 to 8 Characters long and Password object allows “Alphabets lower case” range from 6 to 10 Characters long. BVA & ECP for Age Range Min= 16 Min-1= 15 Min+1= 17 Max= 60 Max-1= 59 Max+1= 61 Manual Testing   BVA Expected Actual Pass Fail Pass Pass Pass Fail ECP Result Valid [0-9] Invalid [A-Z] [a-z] All Special characters 11 .suresh_240878@yahoo. Prepare BVA and ECP for the above expected.B –9440163282 Ex: A Login process allows User Name and Password from a User. Prepare BVA and ECP for the above expected. BVA & ECP for User Name BVA Expected Actual Result Pass Fail Pass Pass Pass Fail ECP Valid [a-z] Invalid [A-Z] [0-9] All Special characters Range Min= 4 Char Min-1= 3 Char Min+1= 5 Char Max= 8 Char Max-1= 7 Char Max+1= 9 Char BVA & ECP for Password BVA Range Expected Actual Result Pass Min= 6 Char Min-1= 5 Char Fail Min+1= 7 Char Pass Pass Max= 10 Char Max-1= 9 Char Pass Max+1= 11 Char Fail ECP Valid [a-z] Invalid [A-Z] [0-9] All Special characters Ex: Age object allows numeric range from 16 to 60.com Suresh.

ODBC JDBC In this testing we are checking whether the insert of front end operations on back end table context. 12 Manual Testing . BVA & ECP for Mobile No. BVA Expected Actual Result Valid Pass [0-9] Fail Fail Range Max= 10 Max-1= 9 Max+1= 11 ECP Invalid [A-Z] [a-z] All Special characters 3) Error-Handling Coverage.Suresh.B –9440163282 suresh_240878@yahoo. In this we are checking whether the functionality output is right or wrong. object allows numeric 10 digits only. Prepare BVA and ECP for the above expected. 4) Calculation Coverage. In this we are checking whether the objects are preventing “Negative Operations” or not. The order functionality. 6) Service level coverage.com  Ex: Mobile No. 5) Back-End Coverage.

B –9440163282 b) Sanitation Testing It is also known as “Garbage Testing”.suresh_240878@yahoo. Browsers. 13 Manual Testing   . Platform means Operating System. Abnormal State to Normal State Normal State Abnormal State b) Compatibility Testing They are (2) types of Compatibility Testing.S V. They are divided into (11) Types.B Ex: Unix does not support VB Techniques Unix VC++ Win98 Win98 is supporting VC++ But Build is not working Properly due to defects During this testing we are checking whether the application build is able to run on different platforms or not. During this testing. compilers and other System software’s. testers are finding extra functionalities in the build with respect to customer requirements.S Build O.com Suresh. a) Recovery Testing During this testing we are checking that whether the application Build is changing from Abnormal State (Crash / Hang) to Normal State or not. 3) Non-Functional Testing After completion of Functional Testing. testers are concentrating on Non-Functional Testing to validate extra characteristics of that build. Build O.

invalid user is preventable or not. (i) Authorization. f) Security Testing. It is also known as “Penetration Testing”.: E-Seva. During this testing we are checking whether the application build is coexistence with other existence to share common resource or not. It is also known as “Competitive Testing”. d) Intersystem Testing. During this testing we are validating whether the application build is supporting different technologies input / Output devises or not. In this testers are checking whether a valid user is accessible or not. (iii) Encrypt / Decrypt Data Testing. Note: Comparative Testing is applicable for Software Produces only not for applications. It is also known as “Inter operability Testing”. (ii) Access Control. but product can be developed with respect to multiple clients requirements. because Software application is developed for a single client requirement. During this testing we are comparing the features of produce with some like previous produce (or) Existing produce in the market to estimate competitiveness. Ex. (ii) Access Control In this we are checking whether a valid user have permission to use specific features / Services or not.B –9440163282 suresh_240878@yahoo. Bill Telephone Bill Water Tax Bill Income Tax Bill Municipal Bill Common Data Base Server Server Server Server Server e) Comparative Testing. During this testing we are validating (3) types of factors such as (i) Authorization. Elec.com  c) Configuration Testing It is also known as “Hardware Compatibility Testing”.Suresh. 14 Manual Testing .

but Storage Testing is representing in Number of bytes and Data Volume Testing is representing number of Records. i) Stress Testing.suresh_240878@yahoo.B –9440163282 (iii) Encrypt / Decrypt Data Testing. Data volume Testing coverages same. Easy Navigation. k) Data Volume Testing. During this testing we are validating below factors. Check Un-installation. Occupied Disk Space. The execution of application build under customer expected configuration under huge amount of resources to estimate the storage capacity of the application database is called Storage Testing. During this testing Testers are calculating the number of records to be stored into application database. The code conversion in between client process and server process to avoid third party accessing.com Suresh. j) Storage Testing. 15 Manual Testing   . Build & Supported Software Customer expected configure Computer Setup Program. Run the application under customer expected configuration under various loads from low to peak to estimate Stress capacity of the application build is called Stress Testing. CLIENT User Name Password SERVER Request Encrypt Decrypt Decrypt Cipher Text Request Encrypt Cipher Text g) Installation Testing It is also known as “Deploying Testing”. Run the application under customer expected configuration under customer load to estimate the speed of processing is called “Load Testing”. Note: Storage Testing. h) Load Testing.

B –9440163282 suresh_240878@yahoo. This release team will go to customer’s site to install the software ion the customer’s environment. By Real customer. By Model customer. Compact Installation. Input device handling. the Project Management will establish Release Team with few Developers. They are (2) types such as α – Test β – Test (Beta Test) Software Product. During this they will concentrate on below factors. UAT (User Acceptance Test) After completion of Software Testing.Suresh. Coexistence with other existence software. few Testers and One (or) two Hardware Engineers. After completion of above like factor observation the release team is providing required training sessions to the customers to understand about the project. Overall functionality. At development site.com  GRAY BOX TESTING Gray Box Testing is a combination of “White Box Testing” and Black Box Testing. At customer site. Release Testing It is also known as “Port Testing”. the Project Management / Project Manager will invite customer to collect feedback on one developed software. Secondary storage handling. After completion of User Acceptance Test” and corresponding modifications. OS Error handling. Output device handling. 16 Manual Testing . (Alfa Test) Software Application.

few testers and Project Manager.com Suresh. Some time this separate Testing team is also not able to conduct planned Testing or good testing due to some risks. CCB Receive change Enhancement Missed Defect Impact Analysis Impact Analysis Perform changes Perform changes Test S/w changes Increase Testing process Capability Test S/w changes CASE STUDY TESTING STAGES Review in Analysis Review in Design Unit Testing Integration Testing Functional & System Testing User Acceptance Testing Release Testing / Port Testing TERMINOLOGY DEVELOPERS TESTERS Input Test Data Output Test Log Program Test Script Challenges in Testing Generally organizations are maintaining separate Testing for Functional and System Testing.suresh_240878@yahoo.B –9440163282 Maintenance During utilization of Software by customers. This separate Testing team is also involving in Release Team and CCB. the company people are receiving change request from them. Manual Testing   RESPONSIBLE PERSONS Analyst Designer Programmers Programmers Test Engineers / Testers Users / Customers CCB 17 . To receive change request from the customers the Project Management establish “CCB” (Change Control Board) with few Developers.

Testers are grouping with programmers to conduct Test on application as early as possible. (c) Pair Testing. Due to lack of knowledge on domain Junior Testers grouped with Senior Testers to share their knowledge.B –9440163282 suresh_240878@yahoo. the people are following “Ad-hoc” Testing. 18 Manual Testing . To overcome above like risks. discussions with other and get the requirements from customers. Buddy means a group of Programmers and Testers. Testers are conducting test on major functionalities of the application build. Testers are conducting Test on application depending on available documents. Planned Testing A Tester conduct Test on application build with pre-planned procedure is called Planned Testing. (or) A Tester conduct test on application build by following “Informal Methods” is called “Ad-hoc Testing”. They are classified as (4) Types. It is also known as Cheapening Testing. This style of testing is called Pair Testing. (or) A Tester conduct Test on application build by following formal methods are called Planned Testing. Ad-hoc Testing A Tester conduct test on application build without Pre-planed is called Ad-hoc Testing. This style of testing is called “Monkey Testing”. Lack of Test Data. Due to lack of Test Data. (b) Buddy Testing. (d) Exploratory Testing. Due to lack of time. Due lack of time. Lack of time. (a) Monkey Testing. Lack of resources. This style of Testing is called as Buddy Testing. Lack of communication.Suresh.com  The risks are Lack of knowledge on project domain. This style of testing called Exploratory Testing.

0 Analysis Coding Testing R&M R. iii) It is flexible when the customer requirements are constant. the rectification of that defect would be difficult.0 Manual Testing   19 . ADVANTAGES i) It is less expensive.B –9440163282 SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) 1) WATERFALL MODEL Requirement Gathering Analysis Design Coding Testing Release & Maintenance In this Model next stage starts after completion of previous stage. ii) It works well for small applications. 2) INCREMENTAL WATERFALL MODEL To overcome some of the limitations of Waterfall we can use Incremental Waterfall model.G R. Incremental Waterfall Model can be used Software Produce Development.suresh_240878@yahoo.com Suresh.G Design R. In this Model a set of requirements they would be one working product.G Analysis Analysis Design Design Coding Coding Testing Testing R&M R&M 2. 1. There is no overlapping between two stages. iii) It is “not flexible” to have changes in the customer requirements during developing the software.0 3. ii) If any defect is found during Testing. DISADVANTAGES i) Testing is a single stage starts after coding.

0  2.0  1.com  3) PROTOTYPE MODEL It is followable when the customer requirements are not clear.Suresh.B –9440163282 suresh_240878@yahoo. DISADVANTAGES i) It is expensive 4) Spiral Model Spiral Model is followable when the customer requirements are enhanceble in terms of versions. “Prototype means a sample Model of application without functionality. Not Clear Hardware Prototype Demo to Client Finalize Environment SRS Base lined Requirements refined BRS Base lined Software Prototype ADVANTAGES i) It is flexible when the customer requirements are not clear.0  Risk Analysis Customer Evaluation ADVANTAGES It is flexible for high risk based projects. Planning Requirement Gathering 5. 20 Coding and Testing Engineers Evaluation Manual Testing .0 4. In this Model we will start the process within complete requirements.0  3. DISADVANTAGES It is expensive.

Software Testing The “Verification and Validation” of a Software is called Software Testing.B –9440163282 5) V-MODEL Like as Fish Model “V-Model” is also defines the mapping between Development stages and Testing stages.suresh_240878@yahoo. In V-Model V stands for “Verification and Validation”. Validation To check whether the developed product is right or not. Verification To check whether the people are developing right product or not. BRS Requirement Gathering FRS Analysis HLD Design LLD Unit Testing User Acceptance Testing System Testing Black Box Testing Integration Testing White Box Testing Coding Manual Testing   21 .com Suresh.

During this testing we will be concentrate on below factors. Sanity Testing is also known as Build Verification Testing (BVT) or Tester Acceptance Testing (TAT) or Testability Testing or Oct-angle Testing. so that he rectification of the defect cost and time would be very less. Smoke Testing is also used to estimate the stability of the Build.com  6) Agile Model It is a latest model which is used in Software produce development. (b) Scrum ADVANTAGES i) Any defect identified early.Suresh. Sanity Testing After receiving the build from the developers we people are conducting “Sanity Testing” to estimate stability of that build before start real testing. d) Controllable. ii) As the defect is identified early. 22 Manual Testing . f) Automatable. They are (2) methods such as (a) X-Tream Programming.B –9440163282 suresh_240878@yahoo. In this model we can get build from the developers in very short time (1 to 4 Weeks) In this model development process. testing process will be carried out parallelly. Smoke Testing Like as Sanity Testing. g) Maintainable h) Simplicity. DISADVANTAGES i) Documentation is very less. c) Observable. the impact of the same defect is very less on subsequent features. b) Operatable. a) Understandable. From the above (8) factors. e) Consistency.

They are (1) Traditional Project (2) Outsourcing Project (3) Maintenance Project Type of Project R/G Analysis Design Coding Testing R&M Traditional Outsourcing Maintenance Manual Testing   23 .suresh_240878@yahoo. Case 1: The repeating of same test for more than one time with multiple data is called as “Re-Testing”.A. to check is there any side effects occurred or not on dependent functionalities by modifying reported defects or by adding new requirements.com Suresh.B –9440163282 Re-Testing. They are (1) Initial Build (2) Stable Build (3) Defect effected Build (4) Modified Build (5) Complete Build (6) Master Build (7) Golden Build U. The Re-execution of selected test or modified build. Case 2: The re-execution of failed tests on modified build to ensure bug fixing work is called “Re-Testing” Regression Testing. Types of Build They are (7) types of Build.T Golden Build Sign off Development Initial Build Sanity Testing Stable Build Defect Effected Build Comprehensi ve Testing Modified Build Bug Fixing Re-Testing Regression Testing Complete Build Master Build Test Closer (Test Lead) Types of Projects Mainly there are (3) Types of projects.

Suresh.B –9440163282

suresh_240878@yahoo.com 

MANUAL TESTING
Testing Process
Test Initiation (Project Management / Quality Analyst T.R.M (Test Responsibility Matrix) 1) What to Test? 2) How to Test? 3) Who to Test? 4) Whom to Test? 1) Scope of the Project 2) Type of the Project 3) Risk involved in that Project

Test Plan Document (Test Lead)

Test Scenarios & Test Cases with Step by step procedure (Test Engineer / Tester)

Re-testing & Regression Testing

Test Case execution as Batches Final Summary Report

Defect Report Bug fixing

Test Closer (Test Lead) UAT  Sign Off 

24

Manual Testing

suresh_240878@yahoo.com

Suresh.B –9440163282

PETT Process (Process Expert Tolls and Techniques)
Requirement Gathering Analysis

Design Coding

Test initiation  Test Plan Document Test Scenarios & Test Case with Step by step process (1) Initial Build

Level ‘2’ Testing Re-Testing / Regression Testing  (4) Modified Build

Level ‘0’ Testing / Sanity Testing (2) Stable Build Level ‘1’ Testing / Comprehensive Testing / Batch Testing 

Defect Report (3) Defect Effected Build

Bug Fixing

(5) Complete Build

Level ‘3’ Testing / Test Closure / Postmortem Testing / Pre-acceptance Testing  (6) Master Build User Acceptance Testing (7) Golden Build Sign Off

Manual Testing  

25

Suresh.B –9440163282

suresh_240878@yahoo.com 

Testing Initiation: In general testing process start with “Test initiation”. In this, Project Manager / Quality Analyst develop Test starting Document. This document defines the required testing approach to be followed by the testing team. During this document preparation they will concentrate on below (12) components. 1) 2) 3) 4) 5) 6) Scope & Objective. Budget Control. Test approach. Roles & Responsibilities Communication & Status Reporting Test deliverables 7) 8) 9) 10) 11) 12) Test Automation Defect Tracing & Reporting Measurements & Matrix. Change & Configuration Management Risks & Mitigations Training Plan.

1) Scope & Objective: The need of testing in the project. 2) Budget Control. Time & Cost allocation to the project. Ex: As per U.S. Norms
100%

64% Development Department

36% Testing Department

#  3) Test approach ## 
In this they will specify a list of selected quality factors to be applied by the Tester. T.R.M (Test Responsibility Matrix) can be finalized by Project Manager / Quality Analyst based on scope of the project, type of the project and Risks involved in that project. TRM : It defines the mapping between Test factors and Development Stages.

26

Manual Testing

com Suresh. Data Integrity: Whether the input objects are taking right type and range of values or not. Correctness: Whether the functionality output is right or wrong. Ease of operate: Easy to installation. Coupling: Co-existence with other Software. Continuity & processing: The integration of modules. Recovery: Whether the application build is changing from abnormal state to normal state or not. 27 Manual Testing   .B –9440163282 Quality Factors / Test Factors 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) RG & Analysis Design Function & Coding System R&M Testing Authorization Access Control Ease of use Ease of operation Correctness Continuity & Processing Coupling Data integrity Recovery Portable Service Level Performance Maintainable Methodology Audit trail. un-installing. downloading. Authorization: Whether a valid user is accessible or not and Invalid User is preventable or not. Portable: Whether the application build is able to run on different platforms or not. Maintainable: Whether the application build is longtime serviceable in customers site or not. dumping. uploading. Access control: Whether a valid user have permission to user specific service of not Ease of Use: Whether the application build is providing user friendly screens or not. Performance: The speed of processing. Service Level: The order of functionality.suresh_240878@yahoo.

Test Cases.. Storage.com  14) Methodology: 15) Audit Trail: Whether the people (Tester) are following right process of not. Test log. twice. 4) Roles and Responsibilities Name of the jobs and his / her responsibilities. If not he will be punishable.) Security Testing Security Testing User interface Testing Installation Testing Functionality Testing Integration Testing Intersystem Testing Input domain Testing Recovery Testing Compatibility Testing Functionality Testing Load. 6) Test deliverables The required documents to be prepared by the testing team. Bank Application.B –9440163282 suresh_240878@yahoo. daily etc. Whether the system is maintains data for the user operation (Ex. Final Summery Report etc. 5) Communication n& Status reporting The required communication between two consecutive jobs. Test Plan. Ex: Project Management Test Lead Test Engineer When do report? Weekly Once. Data volume Testing Stress Testing Compliance Testing Functionality Testing 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) Authorization Access Control Ease of use Ease of operation Correctness Continuity & Processing Coupling Data integrity Recovery Portable Service Level Performance Maintainable Methodology Audit trail.Suresh. Withdrawal time. The following documents were prepared by the Test lead and Test engineers. ATM Centre Code etc. Defect report... Test Data. 7) Test automation The purpose of Automation testing in the project and available tools in the organization. 28 Manual Testing . Test Scenario. Stress.

B –9440163282 8) Defect tracing & Reporting.com Suresh. Manual Testing   29 . 10) Change & Configuration Management How to handle change request from the customer and how to store the documents for future reference. In measurements there are (3) types such as (1) Quality Assessment Measurement (2) Test Management Measurement (3) Process Capability Measurement. The required communication between Programmers and Testers when Test Engineer / Tester got a mismatch.suresh_240878@yahoo. 11) Risk & Mitigations: The possible risks and solutions to overcome them. 12) Training Plan: The required training secession to the Testing team to understand about the project. Large Scale Small Scale Project Management Project Lead Team Lead Test Engineer Programmer Test Engineer Programmer Project Management Test Lead Test Lead Team Lead Transmittal Report 9) Measurement & Matrix: The required measurement to estimate the status of the project.

Delays in delivery. Project duration. iii. Lack of communication. vi. Availability of domain testers. v. ii. Test Lead category people follows below approach. Lack of development process rigor. i. ii. the strategy of the Project implemented by Test Lead in the Project through Test Plan. vii. iv. In this Test Lead category people form the Testing Team depending on below factors. i. Lack of time. iv. Lack of resources. iii. b) Identify Risks After completion of Team Formation the Test Lead identifies risks with respect to that formed testing team in Testing. Project size. BRS TRM Development Plan a) Team formation b) Identify risks c) Prepare Test Plan d) Review Test Plan System Test Plan Module Test Plan (if project is big then only Module Test Plan is to be prepared) a) Team Formation: In general Test Plan Document preparation starts with Team formation.com  TEST PLAN After completion of Test Strategy Document. Lack of test data.Suresh. Lack of knowledge on project domain. Resources (Automation Tools) 30 Manual Testing . During Test Plan Document preparation.B –9440163282 suresh_240878@yahoo.

of reported defects – No. Entry criteria When to start Testing Take complete and correct Test cases. Features to be tested The name of the requirements or features to be test. 8) Suspension criteria When to suspend testing temporarily When we have network problem. Receive Stable Build from the developers. Team Lead will prepare Test Plan Document in IEEE (Institute of Electrical & Electronic Engineer) Format (829) Test Plan ID 9) Exit Criteria Introduction 10) Test deliverables Test items 11) Test environment Features to be tested 12) Staff & Training needs Features not to be tested 13) Responsibilities Test approach 14) Schedule Entry criteria 15) Risks & Mitigations Suspension Criteria 16) Approved by Test Plan ID: Unique number for feature reference. of resolved defects) 31 Manual Testing   .B –9440163282 1) 2) 3) 4) 5) 6) 7) 8) 1) 2) 3) 4) 5) 6) 7) c) Prepare Test Plan After completion of Team formation and Risk Analysis. Test items The name of the requirements or features.suresh_240878@yahoo. Create Test Environment. Introduction Introduction about the project or module. Features not to be tested The name of the requirements or features not to be test Test approach The list of selected quality factors to be applied by the Tester.com Suresh. If pending defects are more (Pending defects = No.

FSR ………… etc. Defect Report. Testers. Modules Vs.com  9) Exit criteria When to stop testing After completion of all module testing. Staff and Training needs The names of selected testers and their training needs. Risks and Mitigations The required solutions for the previously analyzed risks. 10) Test deliverables The required documents to be prepared by the Testers. Test Cases.. During this review they will concentrate on below coverages. Test Data. 11) 12) 13) Test environment The required Software and Hardware to conduct Testing. the signature of the Project Manager. Name of the Test Lead. Test log. Schedule Time duration to the testers. Ex. 14) 15) 16) d) Review Test Plan: Completion of Test Plan Document preparation. After completion of all Major bugs resolved.B –9440163282 suresh_240878@yahoo. Responsibilities Work allocation to the testers.: Test Scenarios. Ex. Approved by Who approved the document. Test Scripts.Suresh. Test Lead is conducting Review Meeting to estimate completeness and correctness of that document. (i) Requirements Based Coverage (What to Test?) (ii) Risk Based Coverage (Who to Test & When to Test?) (iii) TRM Based Coverage (How to test?) 32 Manual Testing .

we can study the Use Case below approach. TEST SCENARIOS Test Scenarios means Test situations. No. 3) Prepare scenarios. Project Name: Reviewed by Module Name: Created by: Reviewed by Created on: Sl. 5) Prepare Test Cass with step by step procedure. Requirement Name Test Scenario Test Cases Manual Testing   33 .1) Identity Entry Point. 6) Continue from step (2) to (6) until completion of all Use Cases. 2. Testers are preparing corresponding Test Scenarios and Test Caes based on Requirement Specifications.com Suresh. USE CASE Use Case is a required document which maintenance the detail information about one low level requirement.3) Identity Outputs 2.B –9440163282 TEST SCENARIOS & TEST CASE DESIGN After completion of Test Plan Document and corresponding Reviews Test Lad allocate the work to the Testers. 2.2) Identity Input Requirement 2. 4) Review scenarios.4) Identity Alternative flows and exceptions. 2. If you want to design Test Cases based on Use Cases.5) Identity exit point. Test Scenario Template These templates are created in MS Excel. 2) Take one Use Case and Study.suresh_240878@yahoo. USE CASE FORMAT: Title Requirement Description Actors / Users Pre-operation Action Positive Flows Exceptions / Negative flows Alternative flows / Alternative Positive flows 1) Collect all Use Cases.

TEST CASE TYPE 1) User Interface Test Cases. Ex: a) Default cursor should be present at the first field.B –9440163282 suresh_240878@yahoo.Suresh.com  TEST CASES A set of Test steps documented along with required inputs and expected results in order to test one low level requirement. 34 Manual Testing . 4) Functional Test Cases: Test Cases that are required to validate the functionality. 3) Validation Test Cases. b) Tab keys should be implemented for all input objects from left to right in downward direction. Thinks to remember while designing the Test Cases. c) Shortcut keys should be implemented for all menu operation. d) Tool tips (Whenever we place the cursor on particular object. 2) Usability Test Cases. Ex: Font Size. 1) User Interface Test Cases To verify the look and Feel of application build screens.. Text alignment. 1) Test Case should be simple and clear. 3) No duplicate Test Case should b written. Images etc. TEST DESIGN TECHNIQUES They are mainly (5) types of design techniques. 2) Test Case should be complete. 4) Functional Test Cases. (1) Boundary Value Analysis (BVA) (2) ECP (Equal Class Partition) (3) Error Guessing (4) Decision Tables (5) State transition. 2) Usability Test Cases To verify ease of use of application build screens. it should return meaningful message) 3) Validation Test Cases: Test Cases that are required to validate business rules or field validation.

invalid state transition.suresh_240878@yahoo. Insert card Block Card PIN Wrong PIN Wrong 1st Entry PIN Ok PIN Ok PIN Ok Access Account 2 nd Wait for PIN Entry Entry PIN Wrong 3rd Entry Manual Testing   35 .B –9440163282 (1) (2) BVA: It is used to validate the range of input objects. To verify the type of input objects. in which test cases are designed to execute valid.com Suresh. ECP: Splitting the inputs into equal parts and randomly checking them. This can be used by experts) Decision Tables A Black Box Test Design testing in which test cases are designed to execute the combination of inputs. (3) (4) Valid Invalid Valid Valid Valid Invalid Invalid Valid (5) State Transition A Black Box Test design techniques. Error Guessing It is a technique which can be used by the people. who have prior knowledge on that application (Ex.

Step–3 etc. Priority Importance of the Test Case. Manual Testing 2) 3) 4) 5) 6) 36 .. Pre-requisites Documents referred. Test Data Set of inputs that are required to execute steps. Step–2.com  TEST CASE TEMPLATE Test Case Test Case Step Step Priority Name / ID Description Name Description 1 2 3 4 5 Expected Results 7 Test Data 6 Actual Created Created Status Comments Results By on 8 9 10 11 12 Reviewed By 14 Reviewed On 15 Reviewer’s Comments 16 QC Path 13 1) Test Case Name / ID: Unique Number for future reference Ex: TC001_Project Name_Module Name_Functionality Name Test Case Description: The description about that Test case. Ex: Step–1.) (3) Low Priority (Cosmetic Test Cases – User Interface Testing) Step Name Every Test Case divided into multiple steps. Step Description The required action to be performed by the user..B –9440163282 suresh_240878@yahoo.Suresh. every step in the test case will have unique number. They are classified into (3) Types such as (1) High Priority (Basic functionality Test Cases) (2) Medium Priority (General functionality Test Cases – Recovery. Compatibility Testing etc.

Created on Date and Time of the created Test Case. such as (a) No Run: Test Case not executed atleast for once. QC Path The path of Quality Control.com Suresh. “Test is failed”. Actual Results The actual output of the system after performing user action. (d) Failed: Test Case any step(s) expected values mismatched with actual value. Reviewed on When (Date & Time) the document was reviewed by reviewer. (b) Not complied: A partially executed test case. 8) 9) 10) 11) 12) 13) 14) 15) 16) Manual Testing   37 . They are classified into (4) types. “Test is passed”. (c) Passed: Test Case executed and the expected value and Actual value is same. who created the Test Cases.B –9440163282 7) Expected Results The required expected output from the system for the corresponding user action.suresh_240878@yahoo. Reviewer’s Comments A set of comments given by reviewer. Reviewed By Name of the Reviewer. Comments A set of comments given by Tester for the Step or Test Cases. Status The current position of the Test Case. Created By The name of the Test Engineer.

Suresh.com  CASE STUDY 38 Manual Testing .B –9440163282 suresh_240878@yahoo.

Customer Address Customer Address object allows alpha-numeric and some special Characters (“–“ “/” “#” “. Mandatory. Mandatory. Customer Ph. object allows Numeric Only. First letter should be Upper Case. Mandatory.”) Maximum of 20 Characters.No. E–Mail E-Mail object allows alpha-numeric and special Characters.No. Date should be less than current system date.com Suresh.suresh_240878@yahoo. Manual Testing   39 . Format is suresh_240878@yahoo. Customer Name Customer Name object allows alphabets. It is not mandatory.B –9440163282 User Name User Name object allows alphabets lower case range from 4 to 8 characters. Password Password object allows alphabets lower case range from 6 to 10 characters.com.” “. Allows 10 digits only. The format is MM/DD/YYYY. Customer DOB Customer DOB object allows Numeric Only. Range from 4 to 12 characters. Phone number is unique. Customer Ph. Mandatory.

4) Verify Update with missing mandatory fields. No. 2) Verify Update with invalid data. 40 Manual Testing . Verify Insert with invalid data. 2) Verify Search with invalid data. 4) Verify Insert with missing mandatory fields.Suresh. Verify Ok with invalid data. 5) Verify Cancel 6) Verify Home Verify Delete Verify Cancel Verify Home Verify Logout 1) 2) 3) 1) 2) 2 Add Cancel Search 3 Search Cancel Update 4 Edit 5 6 7 8 Note: Delete Cancel Home Logout Cancel Home Delete Cancel Home Logout RCN (Requirement Clarification Note) Any doubt in FRS / BRS Document. we people design RCN Document and the same will be sent to BDP for clarification.B –9440163282 suresh_240878@yahoo. 5) Verify Cancel 1) Verify Search with valid data. 3) Verify Cancel 1) Verify Update with valid data. 1 Customer Info Admin Suresh 18/10/2008 Requirement Name Login Cancel Insert Reviewed by Reviewed by Test Scenario Ok Test Cases Verify Ok with valid data. Verify Cancel Verify Insert with valid data.com  TEST SCENARIO DOCUMENT Project Name: Module Name: Created by: Created on: Sl. 3) Verify Insert with duplicate data. 3) Verify Update with duplicate data.

Name.suresh_240878@yahoo. TC02_ enter Url. click Verify Cancel Cancel on Go User functionality Step-2 Enter on Cancel Test Data Url Expected Result It should display Login Page with User Name. click on Ok Step-3 Click on Add -It should display Add Customer page with C.com Suresh. Email objects and Insert. click Password objects and Ok. Password objects and Ok.. It should display meaningful error message. Search. Page with User Name. Password objects and Ok. Search. Reset. case Address.. Password objects and Ok. Info_Admin_ validates Address. C.Ph. Cancel functionalities. case Customer Address. Cancel functionalities. click Info_Admin_ validates on Go Verify Ok ‘Ok’ with invalid functionality Step-2 Enter invalid with invalid data User Name data and Password click on Ok TC03_ This Test Step-1 Open Brower. It should display Customer Information page with Add. word Logout functionalities. Cancel functionalities.No. Customer case enter Url.B –9440163282 TEST CASE DOCUMENT Test Case Test Case Step Step name description Name Description This Test Step-1 Open Brower. Logout functionalities. User It should clear all fields Name and Name and cursor should be Password click & Pass present in the first field.DOB. It should display Login Page with User Name. TC01_ enter Url. C. word Url TC04_ Customer Info_Admin_ Verify Insert with Valid data Url It should display Login This Test Step-1 Open Brower. User Name & Pass word Url User Name & Pass word It should display Login Page with User Name. click Info_Admin_ validates on Go Verify Ok ‘Ok’ with Valid functionality Step-2 Enter valid with valid data User Name data and Password click on Ok This Test Step-1 Open Brower. 41 Manual Testing   . C. validates on Go Cancel functionalities. enter Url.Addr. case Customer Address. Cancel functionalities. ‘Insert’ functionality Step-2 Enter should display valid User It with valid Information User Name Name Customer data and Password & Pass page with Add.

Cancel functionalities.Addr... click Password objects and Ok. case Customer Address. Info_Admin_ validates on Go Cancel functionalities. Verify Insert ‘Insert’ with invalid functionality Step-2 Enter should display valid User It with invalid data Information User Name Name Customer data and Password & Pass page with Add. C. Step-5 Enter valid It should display a data in meaningful Message corresponding such as “Customer Data fields and created with Customer click on Insert ID” Url It should display Login This Test Step-1 Open Brower. TC05_ enter Url. C.Name C. Verify Insert ‘Insert’ functionality Step-2 Enter with should display valid User It duplicate data with Information User Name Name Customer duplicate and Password & Pass page with Add. C. Reset.DOB C. Info_Admin_ validates on Go Cancel functionalities.. word Logout functionalities. C.PhNo E-mail C.PhNo E-mail Expected Result It should clear all fields and cursor should be present in the first field.DOB.Suresh.Name It should display a data in C.Ph. TC06_ enter Url.Addr. click on Ok Step-3 Click on Add -It should display Add Customer page with C. C. Search.Name. Search.Addr. C. word Logout functionalities. Page with User Name. C.B –9440163282 suresh_240878@yahoo. Page with User Name.Name C.Name. data click on Ok Step-3 Click on Add -It should display Add Customer page with C.DOB corresponding Message. 42 Manual Testing . case Customer Address.DOB C.No. Email objects and Insert.PhNo fields and E-mail click on Insert Url It should display Login This Test Step-1 Open Brower. click Password objects and Ok.Addr.Addr. Step-4 Enter invalid C.com  Test Case name Test Case description Step Step Name Description Step-4 Enter data in corresponding fields and click on Reset Test Data C. meaningful Error C.

Cancel functionalities. Enter data in C. should display Enter valid User It Information User Name Name Customer and Password & Pass page with Add.DOB. meaningful Error C. C. Email objects and Insert. C.com Suresh. Email objects and Insert. C. should display Enter valid User It Information User Name Name Customer and Password & Pass page with Add. Reset. word Logout functionalities.. Page with User Name. meaningful Error C. word Logout functionalities. C.Ph. C.DOB in Message. Url It should display Login enter Url.. Url It should display Login enter Url. C.DOB.Name.Addr. Address. Page with User Name.PhNo missing some E-mail mandatory fields and click on Insert Open Brower. Search.PhNo corresponding E-mail fields and click on Insert Open Brower. Reset. on Go Cancel functionalities. click on Ok 43 Manual Testing   .No.No. click on Ok Click on Add -It should display Add Customer page with C.B –9440163282 Test Case name Test Case description Step Name Step Description Test Data Expected Result Step-4 TC07_ Customer Info_Admin_ Verify Insert with missing mandatory fields This Test Step-1 case validates ‘Insert’ functionality Step-2 with missing mandatory fields Step-3 Step-4 TC08_ Customer Info_Admin_ Verify Cancel This Test Step-1 case validates ‘Cancel’ functionality Step-2 C. on Go Cancel functionalities. click Password objects and Ok.Addr.suresh_240878@yahoo. Cancel functionalities. C.DOB fields by Message. Address.Addr. Search.Ph. click Password objects and Ok..Name It should display a Enter duplicate data C.Name It should display a corresponding C.

Step-4 Enter data in C. Url It should display Login This Test Step-1 Open Brower. Search.PhNo and Edit.Name Results Page with corresponding C.. Reset.No. Page with User Name. ‘Search’ functionality Step-2 Enter valid User It should display with valid User Name Name Customer Information data and Password & Pass page with Add.B –9440163282 suresh_240878@yahoo. Cancel functionalities. on Search Home functionalities.Name It should close current corresponding C. Info_Admin_ validates on Go Cancel functionalities.DOB. validates on Go Cancel functionalities. Page with User Name. click Password objects and Ok. C. C. C. Delete.No.Ph.DOB present in the first field. C.Addr. Cancel functionalities.ID It should display Search Step-5 Enter data in C. on Cancel C.Addr.Ph. case Address.ID.DOB Customers Information fields and click C. C. C.PhNo Reset valid C.DOB fields and click previous page. Reset. case Customer Address. Step-4 Enter data in C.Name. Email objects and Insert. Verify Search ‘Search’ with invalid functionality Step-2 Enter valid User It should display with invalid data User Name Name Customer Information TC09_ Customer Info_Admin_ Verify Search with valid data 44 Manual Testing .Suresh. TC10_ enter Url. C.DOB. click Password objects and Ok. click on Ok Step-3 Click on -It should display Search Search Page with C. objects and Search.PhNo E-mail Test Data -- Expected Result Url It should display Login This Test Step-1 Open Brower.ID It should clear all fields corresponding C. page and display C..com  Test Case name Test Case description Step Step Name Description Step-3 Click on Add It should display Add Customer page with C. Cancel.Name. word Logout functionalities. enter Url.Name and cursor should be fields click on C..

ID.ID It should display C.com Suresh.PhNo TC12_ Customer Info_Admin_ Verify Update with valid data Url It should display Login This Test Step-1 Open Brower. C. C.Ph. Page with User Name. C. It should display Search Page with C. Page with User Name.. enter Url.Name. C. Search. C..No. functionality Step-2 Enter valid User It should display User Name Name Customer Information and Password & Pass page with Add. Logout functionalities. click Password objects and Ok. Cancel functionalities.B –9440163282 Test Case name Test Case description data Step Test Description Data and Password & Pass word click on Ok Step-3 Click on -Search Step Name Expected Result page with Add.suresh_240878@yahoo. click on Ok Step-3 Click on -It should display Search Search Page with C. validates Address. word Logout functionalities. Step-4 Enter invalid C. ‘Cancel’ on Go Cancel functionalities. case Address. on Cancel C. fields and click C.DOB corresponding message. objects and Search. click Password objects and Ok.DOB previous page. Search. Url It should display Login case enter Url.Ph. Reset. objects and Search. Reset. Step-4 Enter data in C.DOB. Cancel functionalities.PhNo on Search TC11_ Customer Info_Admin_ Verify Cancel This Test Step-1 Open Brower.ID.Name meaningful data in error C.DOB. ‘Update’ functionality Step-2 Enter valid User It should display User Name Name Customer Information and Password & Pass page with Add. click on Ok 45 Manual Testing   .Name page and display fields and click C.Name.No. Search. C. word Logout functionalities. validates on Go Cancel functionalities.ID It should close current corresponding C.

C.Suresh.B –9440163282 suresh_240878@yahoo. C.Name done” message.. E-mail objects and Update.Name.Name. C.Ph.ID. objects and Search. Page with User Name.DOB.ID.No. C.Ph. Home functionalities.DOB fields and click C.ID.PhNo E-mail C. C.DOB C. Info_Admin_ validates on Go Cancel functionalities.No..ID It should display “Update C.. Reset. click on Ok Step-3 Click on -It should display Search Search Page with C. It should display Edit Page with C.Name C. ‘Update’ Verify Update with functionality Step-2 Enter valid User It should display with invalid invalid data User Name Name Customer Information data and Password & Pass page with Add. Cancel. TC13_ enter Url. Home functionalities.ID C. C.DOB. word Logout functionalities. C.. Reset.Addr. click Password objects and Ok. C. Delete. Cancel.Name.Name corresponding C. It should clear all fields and cursor should be present in the first field. objects and Search. C. C. 46 Manual Testing C.ID data in C.Addr. C. Search.Addr.PhNo E-mail . Step-4 Enter valid C. C.DOB. C.No.Ph.PhNo on Search - Step-5 Select a Customer data click on Edit Step-6 Enter data in corresponding fields click on Reset Step-7 Enter valid data in corresponding fields click on update Url It should display Login This Test Step-1 Open Brower.DOB C. case Customer Address. Cancel functionalities. It should display Search Results Page with Customers Information and Edit.com  Test Case name Test Case description Step Step Name Description Step-3 Click on Search Test Data -- Expected Result It should display Search Page with C.

C. Reset. Home functionalities..DOB fields and click C. case Customer Address.Name. Reset.Addr.DOB.Name C. It should display Customer Information page with Add.ID C. objects and Search.DOB fields and click C. Step-4 Enter valid C. It should display Search Page with C. C. C. C.Name.PhNo E-mail Url User Name & Pass word -- Step-4 Enter valid C.ID. Cancel functionalities.DOB.PhNo on Search - Step-5 Select a Customer data click on Edit Step-6 Enter invalid data in corresponding fields click on update This Test Step-1 Open Brower. Logout functionalities.PhNo on Search It should display Login Page with User Name. Cancel. Delete. C..Name corresponding C.DOB C. C. Home functionalities. TC14_ enter Url. It should display Search Results Page with Customers Information and Edit. E-mail objects and Update..ID data in C. 47 Manual Testing   . It should display meaningful error message. C. click Info_Admin_ validates on Go ‘Update’ Verify Update with functionality Step-2 Enter valid duplicate data with User Name duplicate and Password data click on Ok Step-3 Click on Search C.No.Name corresponding C.Ph. Delete. C.ID data in C. It should display Edit Page with C.B –9440163282 Test Case name Test Case description Step Name Step Description Test Data Expected Result Reset. Cancel. Cancel functionalities.No.ID.Addr.Ph.suresh_240878@yahoo. Cancel. Search. It should display Search Results Page with Customers Information and Edit. Home functionalities. Cancel functionalities. Password objects and Ok.com Suresh.

objects and Search.DOB in message. Home functionalities. Reset. C. C.No..ID. Reset. on Search Home functionalities. corresponding C.. Manual Testing 48 .DOB. C.Name Results Page with C.Name. Cancel. C. Delete. C. click Password objects and Ok.DOB.Ph. on Go Cancel functionalities..Addr.No. Home functionalities.B –9440163282 suresh_240878@yahoo. Cancel. click on Ok Click on -It should display Search Search Page with C. C. Search.Name meaningful duplicate data error C.DOB corresponding Customers Information fields and click C. Url It should display Login enter Url.Ph. Enter valid C.ID. Reset. Page with User Name. Cancel.ID Enter It should display C.Addr. C.Suresh.PhNo and Edit. - Step-5 Select a Customer data click on Edit It should display Edit Page with C. E-mail objects and Update. C. Cancel functionalities. C..ID.Name.DOB. C. Enter valid User It should display User Name Name Customer Information and Password & Pass page with Add. C.Addr.com  Test Case name Test Case description Step Step Name Description Step-5 Select a Customer data click on Edit Test Data - Expected Result Step-6 TC15_ Customer Info_Admin_ Verify Update with missing mandatory fields This Test Step-1 case validates ‘Update’ functionality Step-2 with missing mandatory fields Step-3 Step-4 It should display Edit Page with C.ID It should display Search data in C.Name. word Logout functionalities. C. E-mail objects and Update.PhNo fields click on E-mail update Open Brower.. Address.No.Ph. C.

DOB Previous Page.Ph.Addr. C. C.Name. click Verify Cancel Cancel on Go functionality Step-2 Enter valid User Name and Password click on Ok Step-3 Click on Search Test Case name Test Case description Test Data Expected Result display error C. Home functionalities. Home functionalities.B –9440163282 Step Step Name Description Step-6 Enter data in corresponding fields by missing some mandatory fields and click on update TC16_ This Test Step-1 Open Brower.Ph.Name corresponding C.ID It should C. Cancel.. It should display Search Page with C.Name page and display C. Cancel functionalities.DOB. Cancel functionalities. Password objects and Ok. Reset. Delete. objects and Search.ID. Info_Admin_ validates Address.. C.ID data in C. It should display Search Results Page with Customers Information and Edit. Search.No. C.Addr.ID It should close current C.com Suresh.Addr. Cancel. It should display Edit Page with C. C. Reset. Step-5 Select a Customer data click on Edit Step-6 Enter data in corresponding fields and click on Cancel Manual Testing   C. Logout functionalities.PhNo E-mail 49 . E-mail objects and Update.PhNo on Search - It should display Login Page with User Name.DOB fields and click C..DOB.No.ID.Name. C. C.DOB message.suresh_240878@yahoo. C. Customer case enter Url. C.PhNo E-mail Url User Name & Pass word -- Step-4 Enter valid C. It should display Customer Information page with Add. C.Name meaningful C. C.

Url It should display Login case enter Url. Cancel. C. C. objects and Search. click on Ok Step-3 Click on -It should display Search Search Page with C.com  Test Case name TC17_ Customer Info_Admin_ Verify Home Test Case Step Step Test Expected Result description Name Description Data This Test Step-1 Open Brower.ID valid Step-4 Enter It should display Search data in C. C. Search. Home functionalities. Customer case enter Url.Ph. Cancel on Go Cancel functionalities. click Password objects and Ok.. validates Address.Name. Cancel functionalities. functionality Step-2 Enter valid User It should display User Name Name Customer Information and Password & Pass page with Add. E-mail objects and Update.PhNo and Edit. C.Name page and display C. Search. word Logout functionalities. Delete..DOB.No. C. Cancel. on Search Home functionalities. Manual Testing Url . Cancel functionalities. User It should display Name Customer Information & Pass page with Add.DOB. C.ID. Password objects and Ok. C.Name.B –9440163282 suresh_240878@yahoo. C.Addr. Reset. C. Step-5 Select a Customer data click on Edit - It should display Edit Page with C. C.DOB Customers Information fields and click C.Ph.DOB Customer Info Page.ID It should close current C.PhNo E-mail It should display Login Page with User Name.ID.. Reset. word Logout functionalities. click Verify Delete Delete on Go functionality Step-2 Enter valid User Name and Password click on Ok 50 C.No.Addr. Step-6 Enter data in corresponding fields and click on Home TC18_ This Test Step-1 Open Brower. Page with User Name.Suresh. Info_Admin_ validates Address.Name Results Page with corresponding C.

Name corresponding C. It should display Search Results Page with Customers Information and Edit.DOB fields and click C.. Search. case Address.No.Name. It should display Login Page with User Name.ID data in C. C.ID data in C. C.com Suresh. It should display Customer Information page with Add. It should display Search Results Page with Customers Information and Edit. Cancel functionalities.No.. It should display Search Page with C. Cancel. Reset. C.Name corresponding C. Reset. C.PhNo on Search - Step-5 Select a Customer data click on Delete TC19_ Customer Info_Admin_ Verify Cancel Url This Test Step-1 Open Brower. objects and Search.Ph.PhNo on Search - Step-5 Select a Customer data click on Cancel Manual Testing   .ID.Ph.suresh_240878@yahoo. Logout functionalities. C. enter Url. Password objects and Ok. It should close current page and display previous page. Cancel functionalities.Name. Cancel functionalities. Home functionalities. It should remove customer’s information with “Customers Information was successfully deleted”.DOB. objects and Search. 51 Step-4 Enter valid C. C. Delete.B –9440163282 Test Case name Test Case description Step Step Name Description Step-3 Click on Search Test Data -- Expected Result It should display Search Page with C. Delete.DOB fields and click C. Home functionalities.ID. Cancel.DOB. click validates on Go Cancel functionality Step-2 Enter valid User User Name Name and Password & Pass word click on Ok Step-3 Click on -Search Step-4 Enter valid C.

ID.No. Search. C.PhNo and Edit. Search. Reset. Page with User Name. C. C. Verify Logout on Go Cancel functionalities. click on Ok Step-3 Click on -It should display Search Search Page with C. click Password objects and Ok. Step-5 Select a It should close current Customer page and display data click on Customer Info Page. word Logout functionalities. Page with User Name.com  Test Case name TC20_ Customer Info_Admin_ Verify Home Test Case Step Step Test Expected Result description Name Description Data This Test Step-1 Open Brower.Name Results Page with corresponding C. click on Ok Step-3 Click on It should close current Logout page and display Login Page 52 Manual Testing . Cancel. Home on Go Cancel functionalities.ID valid Step-4 Enter It should display Search data in C. Info_Admin_ validates Address. word Logout functionalities.DOB.Ph..Name. Home TC21_ This Test Step-1 Open Brower.DOB Customers Information fields and click C. Url It should display Login Customer case enter Url. C. Cancel functionalities. objects and Search. Url It should display Login case enter Url. on Search Home functionalities. validates Address. functionality Step-2 Enter valid User It should display User Name Name Customer Information and Password & Pass page with Add.B –9440163282 suresh_240878@yahoo.Suresh. Delete. Logout functionality Step-2 Enter valid User It should display User Name Name Customer Information and Password & Pass page with Add. click Password objects and Ok.

BVA & ECP for Password BVA ECP Range Expected Actual Result Valid Invalid [a-z] [A-Z] Pass Min= 6 Char [0-9] Min-1= 5 Char Fail All Min+1= 7 Char Pass Special Pass Max= 10 Char characters Max-1= 9 Char Pass Max+1= 11 Char Fail Customer Name Customer Name object allows alphabets. Range from 4 to 12 characters. BVA & ECP for Customer Name BVA Range Expected Actual Result Pass Min= 4 Char Fail Min-1= 3 Char Pass Min+1= 5 Char Pass Max= 12 Char Max-1= 11 Char Pass Max+1= 13 Char Fail Manual Testing   ECP Valid [a-z] [A-Z] Invalid [0-9] All Special characters 53 .suresh_240878@yahoo.com Suresh. BVA & ECP for User Name BVA Expected Actual Result Pass Fail Pass Pass Pass Fail ECP Valid [a-z] Invalid [A-Z] [0-9] All Special characters Range Min= 4 Char Min-1= 3 Char Min+1= 5 Char Max= 8 Char Max-1= 7 Char Max+1= 9 Char Password Password object allows alphabets lower case range from 6 to 10 characters. First letter should be Upper Case.B –9440163282 User Name User Name object allows alphabets lower case range from 4 to 8 characters. Mandatory.

object allows Numeric Only. BVA ECP Range Expected Actual Result Valid Invalid Max= 10 Digits Pass [0-9] [a-z] Max-1= 19 Digits Fail [A-Z] Max+1= 21 Digits Pass All Spl.No. Date should be less than current system date. Customer Ph. Phone number is unique. BVA & ECP for Customer Ph.B –9440163282 suresh_240878@yahoo.. Characters mentioned –/#. Mandatory.”) Maximum of 20 Characters. The format is MM/DD/YYYY.” “.No. Allows 10 digits only. BVA & ECP for Customer DOB BVA ECP Range Expected Actual Result Valid Invalid All Max= 20 Char Pass [a-z] Special Max-1= 19 Char Fail [A-Z] characters Max+1= 21 Char Pass [0-9] Except Some Spl. BVA & ECP for Customer Address BVA ECP Range Expected Actual Result Valid Invalid All Max= 20 Char Pass [a-z] Special Max-1= 19 Char Pass [A-Z] characters Max+1= 21 Char Fail [0-9] Except Some Spl.. Customer DOB Customer DOB object allows Numeric Only. Characters mentioned –/#. Mandatory.No.com  Customer Address Customer Address object allows alpha-numeric and some special Characters (“–“ “/” “#” “. Mandatory. Characters 54 Manual Testing . Customer Ph.Suresh.

0 1) rama TC01_ User 2) rames Customer Name 3) gahesha 1 Info_Admin_ 4) reliance StepVerify Ok with 2 1) suresh Valid data 2) sureshb Password 3) sureshbug 4) sureshbuga Stephttp://192.168.Addr. Brundavancolony7/G-3   Manual Testing   55 .Name pava Verify Cancel 2 Password ganesh Stephttp://192.U.1.0 Url 1 /Customer Info 1.-5/G C.Name pava TC04_ 2 Password ganesh Customer Ramu 4 Info_Admin_ Sita Verify Insert C.suresh_240878@yahoo.0 Url 1 /Customer Info 1.1. Name Name required Stephttp://192. Test Case Step Data Data generated Comments No.168.No.168.D.Name Ramakrishna Stepwith Valid data Koteswararao 5 Koti.0 Step.U.1.0 Url 1 /Customer Info 1.0 Customer 3 Info_Admin_ Step.168.com Suresh.0 TC03_ Url 1 /Customer Info 1.1.0 1) ram TC02_ User 2) sureshbug Customer Name 3) ga*1 2 Info_Admin_ 4) ram@123 StepVerify Ok with 2 1) sures invalid data 2) sureshbugat Password 3) SURESH 4) sarvani@bu Stephttp://192.B –9440163282 TEST DATA DOCUMENT Project Name Reviewed by Module Name Created By Reviewed on Created on Sl.

9440163282 suresh_240878@ E-mail yahoo. Brundavancolony7/G-3 Step.DOB 25/10/1976 C.Name Koteswararao C. 9440163282 suresh_240878@ E-mail yahoo. Brundavancolony7/G-3 Step.com Step1 Url http://192.DOB 05/25/1976 C.Name Koteswararao C.com  Sl.0 /Customer Info 1. 9440163282 suresh_240878@ E-mail yahoo.Suresh.C.Name pava 2 Password ganesh C.Ph.1.com Stephttp://192.0 Manual Testing 8 56 .Name pava 2 Password ganesh C.B –9440163282 suresh_240878@yahoo.U.168.Ph.1.com Stephttp://192. Brundavanacolony Step7/G-3 4 C.No.Ph.DOB 05/25/1976 4 C.168.U.Addr.0 Step.1.U.0 Url 1 /Customer Info 1.Name pava 2 Password ganesh Sai C.com Stephttp://192.Ph.168. +91-9440163282 suresh_240878# E-mail yahoo.0 Url 1 /Customer Info 1.0 Step.1.168.Addr.Addr.Name Saisarvanibug Brundavancolony7/G*3 C.0 Step.No.No.C.No.DOB 05/25/1976 4 C. Test Case Name 5 TC05_ Customer Info_Admin_ Verify Insert with invalid data 6 TC06_ Customer Info_Admin_ Verify Insert with duplicate data 7 TC07_ Customer Info_Admin_ Verify Insert with missing mandatory fields TC08_ Customer Info_Admin_ Step Data Data generated Comments Name required C.0 Url 1 /Customer Info 1. No.

Test Case Name Verify Cancel Step Data Name required Step2 Step4 Step1 Step2 Step5 U. Data generated Comments 9 TC09_ Customer Info_Admin_ Verify Search with valid data pava ganesh Koteswararao Brundavancolony7/G-3 05/25/1976 9440163282 suresh_240878@ E-mail yahoo. C.168.com Suresh.Name C.0 Url /Customer Info 1.DOB 05/25/1976 C. No.Ph.suresh_240878@yahoo. 9440163282 Manual Testing   57 .Addr.B –9440163282 Sl.Name Koteswararao C.Ph.0 U.1.Name Password C.DOB C.No.com http://192.No.Name pava Password ganesh C.

Testers are receiving initial build from the development people. Requirement Description Use Case Reference Project Manager Reviewed By Reviewed on Last Updated on Test Scenario Test Case Reference TEST CASE EXECUTION After completion of Test Cases preparation and corresponding reviews. Test lead is mapping Test Cases with Requirement Traceability Matrix Document. To receive any type of build from the developers. Traceability Matrix Template Project Name Prepared By Prepared on Sl. No. During Test Case execution Testers are receiving modified build from the developers.B –9440163282 suresh_240878@yahoo.Suresh. Test Engineer is conducting Peer Review and Test Lead is conducting Lead Review to estimate “Completeness and Correctness” of that document PM PL TE-1 TE-2 Peer Review After completion of review on Test Cases.com  Review on Test Cases After completion of Test Case preparation. (RTM) RTM defines the mapping between requirements and Test Cases. Testers required a valid negotiation / communications with developers like as below. 58 Manual Testing .

0 2.suresh_240878@yahoo.0 Client VSS (Visual Source Safe) The versions have been maintained by these VSS FTP (File Transfer Protocol) Deploy / Install Build Sanity Testing Testers EXECUTION LEVELS: Initial Build Stable Build Level ‘1’ Comprehensive Testing Defect Effected Build Level ‘0’ Sanity Testing Modified Build Level ‘2’ Re-Testing Regression Testing Bug Fixing Complete Build Master Build Level ‘3’ Test Closer (Test Lead) U.T Manual Testing   Golden Build Sign off 59 .A.B –9440163282 Developers COMMON REPOSITORY / SOFT BASE 1.0 3.com Suresh.

In this every Test Case has to be executed by Tester either in Manual or in Automation. 1) Under standable. P1. 6) Automatable. Build Build Test Cases Automation Testing Test Engineer Automation Testing Test Cases Test Engineer Manual Testing 60 Manual Testing . In this testing. Testers are conducting Level ‘0’ Testing to estimate stability of that build before start real testing. P1–Medium Priority. 7) Maintainable. 8) Simplicity. P2.B –9440163282 suresh_240878@yahoo. P2–Low Priority) to validate functionality. Test Cases (P0–High Priority. During this Testing they will concentrates on below factors.com  TEST HARNESS: Test Harness means ready to start testing. LEVEL ‘1’ TESTING It is also known as “Comprehensive Testing”. 2) Operatable 3) Observable 4) Controllable. During this testing Testers are executing all P0. Test Harness = Test Environment + List of Test Cases. Testers are concentrates on Core (Basic) functionalities. LEVEL ‘0’ TESTING After receiving initial build from the development people. 5) Consistency. From the above factors Level ‘0’ Testing is also known as “Oct-Angle Testing” or Sanity Testing or Build Verification Testing or Tester Acceptance Testing or Testability Testing.Suresh.

2) 3) 4) Summary Brief description of the defect. a.com Suresh. They are (2) types (i) New–Reporting for first time. If No: It is not reproducible.B –9440163282 Execution Process Skip Take all the Test Cases Test Case Execution Fail Pass Close Blocked Test Cases Partial Pass or Fail Defect Report During test execution. 5) 6) Manual Testing   61 . attach test procedure along with snap shots. attach test procedure. If Yes: It is reproducible.suresh_240878@yahoo. b. Defect Report Format 1) Defect ID Unique for future reference. Test Case Name Name of the Test Case (in which Test Case execution the defect is raised) Reproducible The defect is repeatable in every time execution. (ii) Re-open–For re-reporting defects. Status Status of the defect. Features The name of the feature / functionality in which defect. Testers are reporting mis-matches to development Teas as “Defect” in Defect Report Document.

9) 10) 11) 12) 13) 62 Manual Testing . It is classified into (3) types such as (i) High Priority (ii) Medium Priority (iii) Low Priority Assigned to Name of the Developer Detected By Name of the Tester (Who detected the defect) Reported on Date and Time Build Version ID In which version of the build the defect is raised. Resolved on Date and Time Resolution Type: Acknowledgment from the developers for the reported defect.Suresh. Approved by Signature of the Team Lead / Project Lead. Suggested to fix Suggestions to developer to fix the defects By Developers Fixed By: Name of the Programmer who fixed the defect. They are classified into (3) Types such as (i) (ii) (iii) High severity – Urgent to solve Medium severity – Mandatory to solve Low severity – Compulsory to solve 8) Priority Importance of the defect with respect to customer or importance of the functionality.com  7) Severity (Seriousness with respect to Testers) It means seriousness of the defect with respect to Tester or seriousness of the functionality.B –9440163282 suresh_240878@yahoo.

. Manual Testing   63 .com Suresh. What is Build Internal period? The time gap between two consequent builds is called as Build Internal period.B –9440163282 Types of defects 1) User interface defects (Low Severity) Spelling mistakes (High Priority) Improper alignment (Low Priority) 2) Input domain defect (Medium Severity) Input type is not taking valid type ((High Priority) Input type is taking invalid type also (Low Priority) 3) Error handling defect (Medium Severity) No error message for wrong operation (High Priority) Complex message in error message (Low Priority) 4) Calculation defect (High Severity) Wrong outputs (High Priority) 5) Load conditional defect (High Severity) Build is not supporting more than one user (High Priority) Build is not supporting customer expected load (Low/Medium Priority) 6) Hardware defect (High Severity) Build is not supporting any hardware devices (High Priority) Build is supporting hardware and wrong output coming from hardware (Low Priority) 7) Role conditional defect (High Severity) System crash. 8) Version control system (High Severity) Mistake in version control 9) Source defects (Medium Severity) Mistake in Help Document (High Priority) What is defect Age? The time gap between defect reported on and defect resolved on.suresh_240878@yahoo. Dead lock etc. Showstoppers.

Deferred: The defect is postponed to next version / release. P2 Test Cases 64 Manual Testing . P1.B –9440163282 suresh_240878@yahoo. not rejected due to developer need more information about that defect. Testers are performing Re-testing / Regression Testing to ensure whether the reported defects are properly rectified by the developers or not and to check whether there is any side effects occurred or not on dependent functionalities by solving the reported defects or by adding new requirements. Case Study Modified Build High Severity All P0. Duplicate: The defect is rejected due to defect is previously accepted defect. P2 Test Cases Enhancement All P0. LEVEL ‘2’ TESTING After receiving the modified build from the developers. & Selected P2 Test Cases Low Severity Some P0 & Selected P1.Suresh. P1. some P1.com  BUG LIFE CYCLE / DEFECT LIFE CYCLE New Review the defect Reopen Open Fixed Rejected Hold Duplicate Deferred Defect If defect is not fixed Close Hold: The defect is not accepted. P2 Test Cases Medium Severity All P0.

B –9440163282 Case 1: Case 2: Case 3: Case 4: If the development team resolved bug severity is high. After completion of above like coverages Test lead is conducting Test Closure in below approach. If the development team released modified build due to some change request then the Testers are re-executing all P0. If the development team resolved bug severity is low. Test lead is conducting “Test Closure” to estimate that whether the Test Engineer meets exit criteria or not. 1) Requirements Coverage: All the requirements with respect to functionality. Take High Bug density Module Do Regression Effort Estimation Do Regression Plan Regression Do Regression Manual Testing   65 . P2 Test Cases on that modified build. In this Test lead category people will concentrate on below coverages. P1. P1. LEVEL ‘3’ TESTING After completion of all test cases execution and corresponding bugs resolving. some P1 and selected P2 Tests cases on that modified Build. P2 Test Cases on that modified build.suresh_240878@yahoo. then Testers are re-executing some P0 and selected P1 and P2 Test cases on that modified build. 2) Bug density No. of defects in Module . If the development team resolved bug severity is medium then. Testers are re-executing all P0. Testers are sending complete build to the Test lead along with FSR (Final Summary Report) After receiving Final Summary Report from the Testers.com Suresh. X 100 No of defects in the Project 3) Analysis of deferred bugs: Whether the deferred bugs are reasonable or not to postpone. then Testers are re-executing all P0.

At customer site. (ii) Known issues 66 Manual Testing .B –9440163282 suresh_240878@yahoo. By Model customer. the Project Management deliver that software / build to the client along with Software Delivery Note (S/w DN). At development site.Suresh. By Real customer. It consists of (2) issues such as (i) User Manual.com  User Acceptance Testing After completion of “Test Closure” the Project Manager collects feedback from the customers on developed software through “User Acceptance Testing”. They are two types such as β – Test α – Test (Beta Test) (Alfa Test) Software Application. Software Product. Signoff After completion of User Acceptance Testing and corresponding modifications.

Sign up to vote on this title
UsefulNot useful