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

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

designers are preparing design document which includes Functional Requirement Specifications and System Requirement Specifications. During the review they are concentrate on the below factors.B –9440163282 TESTING MODELS FISH MODEL Fish model defines the mapping between development stages and Testing stages. the same category people conducting reviews in Analysis Document for completeness and correctness.com Suresh. After completion of analysis document. Manual Testing   White Box Testing / Glass Box Testing / Programe Phase Testing / Open Box Testing Test Software Changes 5 . In this.suresh_240878@yahoo. Business Development People are preparing Business Requirement Specification Document and Analyst people are preparing Analysis Document with respective to Business Requirement Specification. 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. During the review they concentrate on below factors. 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.

programs with concentrate on coding to construct a Software Build. In this Test repetition. During this testing programmers are checking that whether the program is running or not? To perform this test they will follow below approach. Programmers are interconnecting them to a system.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.B –9440163282 suresh_240878@yahoo. a) Basic Path Testing. If conditions. c) Program Technique Testing In this testing the programmers are checking the execution speed of the program. (I) Unit Testing It is also called as Program Testing or Micro Testing. d) Mutation Testing Mutation means changes in a program. In this testing programmers are performing wanted changes in the program and executing the program repeatedly. Memory allocation etc.Suresh. In this interconnection of programs to verify the programs and interface between programs or modules. b) Control Structure Testing In this testing the programmers will concentrate on corresponding program output. Unit testing consists of below factors.. 1) Draw flow diagram of that program. For loops. then programmers are performing changes in the structure of the program without disturbing functionality. Unit testing means “Single Program Testing or Component 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. programmers are conducting “White Box Testing” White Box Testing classified as Two Types such as (I) Unit Testing (II) Integration Testing. If the execution speed of the program is not good. In this programmers will concentrate on every statement including. 6 Manual Testing . After completion of preparing all programs.

Manual Testing   7 .com Suresh. it works like as under constructive Main Module. “Conducting test on Sub-Modules without testing on Main Module is called Bottom-up Approach. a) Top-Down Approach.suresh_240878@yahoo. 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. Programmers are interconnecting to form a system. it works like as under constructive Sub Module. To estimate the interface between programs or modules programmers are conducting Integration Testing.B –9440163282 Programmers are checking the completeness and correctness of the Test. it is also called as Called 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. b) Bottom-Up Approach. Main Module Driver / Calling Program Sub-Module-1 Sub-Module-2 Sub-Module-3 In the above approach “Driver” is temporary program. “Conduct test on Main module without conducting test on some of the Sub-Modules is called Top-Down Approach. They are (4) Types of approaches. Driver is also known as Calling Program. The verification of main module without coming to some of the Sub-Modules is called as Top-Down Approach. 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. Case 4: Bigbang Approach is followable. Case 3: Hybrid Approach is followable. This approach is not suitable for large modules. The verification of all modules after completion of all Modules development and corresponding unit testing is called as “Bigbang Approach”. 8 Manual Testing . when the application build consists less number of modules or less number of interconnections. when the customer’s requirements are constituent of clear. when the customer’s requirements are clear and the architecture structure of the system is changing.B –9440163282 suresh_240878@yahoo. Case 2: Bottom-up approach is followable. CASE STUDY Case 1: Top-down approach is followable. when the customer’s requirements are not clear or frequently changing. 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.

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

Functional Testing classified into (2) Types (a) Functionality Testing (b) Sanitation Testing. 6) Service level Coverage. a) Functionality Testing During this Testing Testers are validating customers requirement in terms of (6) 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. (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 . Line Missing etc.Suresh. 3) Error-Handling Coverage. To perform this test we (Testers) are using (2) Types of Testing. Testers are conducting Functional Testing to validate customer requirements.com  b. 2) Functional Testing After completion of User Interface testing. Word Missing. Manual Support Testing It is also known as “Help document Testing”. Ex: Spelling Mistakes.. Usability Functional & Non-Functional Testing Testing Manual Support Testing. Grammar mistakes. 1) Behavioural Coverage. 5) Back-end Coverage. User interface testing. Case 1: Receive build from the developers. 1) Behavioural Coverage.B –9440163282 suresh_240878@yahoo. In this testing Testers are checking whether the objects are properly responding of not. 2) Input Domain Coverage. During this testing Testers are checking the context sensitiveness testing. 4) Calculation Coverage. with respective to Business Operation.

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. Prepare BVA and ECP for the above expected.B –9440163282 Ex: A Login process allows User Name and Password from a User. 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 . 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.suresh_240878@yahoo. Prepare BVA and ECP for the above expected.

5) Back-End Coverage. 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. 12 Manual Testing . object allows numeric 10 digits only. The order functionality.com  Ex: Mobile No. ODBC JDBC In this testing we are checking whether the insert of front end operations on back end table context. In this we are checking whether the objects are preventing “Negative Operations” or not. Prepare BVA and ECP for the above expected. 6) Service level coverage. In this we are checking whether the functionality output is right or wrong. BVA & ECP for Mobile No. 4) Calculation Coverage.Suresh.B –9440163282 suresh_240878@yahoo.

com Suresh.B –9440163282 b) Sanitation Testing It is also known as “Garbage Testing”.S V.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. 3) Non-Functional Testing After completion of Functional Testing. Browsers.suresh_240878@yahoo. They are divided into (11) Types.S Build O. 13 Manual Testing   . Abnormal State to Normal State Normal State Abnormal State b) Compatibility Testing They are (2) types of Compatibility Testing. testers are finding extra functionalities in the build with respect to customer requirements. Platform means Operating System. During this testing. 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. Build O. testers are concentrating on Non-Functional Testing to validate extra characteristics of that build. compilers and other System software’s.

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

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”. i) Stress Testing. During this testing we are validating below factors. 15 Manual Testing   . j) Storage Testing. 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.suresh_240878@yahoo. Easy Navigation. Data volume Testing coverages same. During this testing Testers are calculating the number of records to be stored into application database. Check Un-installation. Build & Supported Software Customer expected configure Computer Setup Program. Note: Storage Testing.B –9440163282 (iii) Encrypt / Decrypt Data Testing. Run the application under customer expected configuration under customer load to estimate the speed of processing is called “Load Testing”. k) Data Volume Testing.com Suresh. h) Load Testing. The code conversion in between client process and server process to avoid third party accessing. Occupied Disk Space. but Storage Testing is representing in Number of bytes and Data Volume Testing is representing number of Records.

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

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. To receive change request from the customers the Project Management establish “CCB” (Change Control Board) with few Developers. the company people are receiving change request from them. This separate Testing team is also involving in Release Team and CCB.B –9440163282 Maintenance During utilization of Software by customers. few testers and Project Manager. Manual Testing   RESPONSIBLE PERSONS Analyst Designer Programmers Programmers Test Engineers / Testers Users / Customers CCB 17 .com Suresh. Some time this separate Testing team is also not able to conduct planned Testing or good testing due to some risks.suresh_240878@yahoo.

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

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

com  3) PROTOTYPE MODEL It is followable when the customer requirements are not clear.0  3. “Prototype means a sample Model of application without functionality.Suresh. 20 Coding and Testing Engineers Evaluation Manual Testing .0  Risk Analysis Customer Evaluation ADVANTAGES It is flexible for high risk based projects.0 4. Planning Requirement Gathering 5.0  2. In this Model we will start the process within complete requirements. DISADVANTAGES It is expensive.B –9440163282 suresh_240878@yahoo. 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  1. DISADVANTAGES i) It is expensive 4) Spiral Model Spiral Model is followable when the customer requirements are enhanceble in terms of versions.

B –9440163282 5) V-MODEL Like as Fish Model “V-Model” is also defines the mapping between Development stages and Testing stages. Verification To check whether the people are developing right product or not. In V-Model V stands for “Verification and Validation”.suresh_240878@yahoo. 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. Software Testing The “Verification and Validation” of a Software is called Software Testing. Validation To check whether the developed product is right or not.

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

Types of Build They are (7) types of Build. 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.A.suresh_240878@yahoo.com Suresh. to check is there any side effects occurred or not on dependent functionalities by modifying reported defects or by adding new requirements. 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 .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. Case 1: The repeating of same test for more than one time with multiple data is called as “Re-Testing”.B –9440163282 Re-Testing. Case 2: The re-execution of failed tests on modified build to ensure bug fixing work is called “Re-Testing” Regression Testing.

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

Recovery: Whether the application build is changing from abnormal state to normal state or not. Coupling: Co-existence with other Software. uploading.com Suresh. Authorization: Whether a valid user is accessible or not and Invalid User is preventable or not. Correctness: Whether the functionality output is right or wrong. Service Level: The order of functionality. dumping. Data Integrity: Whether the input objects are taking right type and range of values or not. Maintainable: Whether the application build is longtime serviceable in customers site or not. downloading. Ease of operate: Easy to installation. Portable: Whether the application build is able to run on different platforms or not. Performance: The speed of processing.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. 27 Manual Testing   . Continuity & processing: The integration of modules.suresh_240878@yahoo. un-installing. 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.

ATM Centre Code etc. Stress. twice.com  14) Methodology: 15) Audit Trail: Whether the people (Tester) are following right process of not. The following documents were prepared by the Test lead and Test engineers. Defect report. Withdrawal time. 7) Test automation The purpose of Automation testing in the project and available tools in the organization.) 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. Ex: Project Management Test Lead Test Engineer When do report? Weekly Once. Test Plan.. Bank Application. Final Summery Report etc. If not he will be punishable.. Test Data. 6) Test deliverables The required documents to be prepared by the testing team. Test Scenario.B –9440163282 suresh_240878@yahoo. Test Cases. Storage. Whether the system is maintains data for the user operation (Ex. Test log. 5) Communication n& Status reporting The required communication between two consecutive jobs. 28 Manual Testing . daily etc. 4) Roles and Responsibilities Name of the jobs and his / her responsibilities. 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..

Manual Testing   29 . 10) Change & Configuration Management How to handle change request from the customer and how to store the documents for future reference. 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.com Suresh. In measurements there are (3) types such as (1) Quality Assessment Measurement (2) Test Management Measurement (3) Process Capability Measurement.suresh_240878@yahoo. 12) Training Plan: The required training secession to the Testing team to understand about the project.B –9440163282 8) Defect tracing & Reporting. 11) Risk & Mitigations: The possible risks and solutions to overcome them. The required communication between Programmers and Testers when Test Engineer / Tester got a mismatch.

i. vi. Test Lead category people follows below approach. Lack of communication. During Test Plan Document preparation. v.B –9440163282 suresh_240878@yahoo.Suresh. In this Test Lead category people form the Testing Team depending on below factors. iv. Lack of time. Lack of test data. b) Identify Risks After completion of Team Formation the Test Lead identifies risks with respect to that formed testing team in Testing. ii. the strategy of the Project implemented by Test Lead in the Project through Test Plan. iv.com  TEST PLAN After completion of Test Strategy Document. Lack of development process rigor. iii. Delays in delivery. Project size. Project duration. Lack of resources. Availability of domain testers. iii. 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. i. ii. Resources (Automation Tools) 30 Manual Testing . vii. Lack of knowledge on project domain.

of reported defects – No.suresh_240878@yahoo. Features to be tested The name of the requirements or features to be test. Introduction Introduction about the project or module.com Suresh. If pending defects are more (Pending defects = No. 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. 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. of resolved defects) 31 Manual Testing   . Create Test Environment.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. Entry criteria When to start Testing Take complete and correct Test cases. 8) Suspension criteria When to suspend testing temporarily When we have network problem. Receive Stable Build from the developers. Test items The name of the requirements or features.

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

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

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

ECP: Splitting the inputs into equal parts and randomly checking them.suresh_240878@yahoo. To verify the type of input objects.B –9440163282 (1) (2) BVA: It is used to validate the range of input objects. in which test cases are designed to execute valid.com Suresh. (3) (4) Valid Invalid Valid Valid Valid Invalid Invalid Valid (5) State Transition A Black Box Test design techniques. 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 . who have prior knowledge on that application (Ex. 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. invalid state transition. Error Guessing It is a technique which can be used by the people.

Suresh.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. Step–2.B –9440163282 suresh_240878@yahoo.) (3) Low Priority (Cosmetic Test Cases – User Interface Testing) Step Name Every Test Case divided into multiple steps. They are classified into (3) Types such as (1) High Priority (Basic functionality Test Cases) (2) Medium Priority (General functionality Test Cases – Recovery.. every step in the test case will have unique number. Step Description The required action to be performed by the user. Ex: Step–1.. Step–3 etc. Compatibility Testing etc. Priority Importance of the Test Case. Pre-requisites Documents referred. Manual Testing 2) 3) 4) 5) 6) 36 . Test Data Set of inputs that are required to execute steps.

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

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

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

4) Verify Update with missing mandatory fields. Verify Ok with invalid data.com  TEST SCENARIO DOCUMENT Project Name: Module Name: Created by: Created on: Sl. 40 Manual Testing . 3) Verify Cancel 1) Verify Update with valid data. 2) Verify Update with invalid data. 3) Verify Insert with duplicate data. Verify Cancel Verify Insert with valid data. 2) Verify Search with invalid data. 5) Verify Cancel 1) Verify Search with valid data.B –9440163282 suresh_240878@yahoo. we people design RCN Document and the same will be sent to BDP for clarification. 4) Verify Insert with missing mandatory fields. 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. No. Verify Insert with invalid data.Suresh. 3) Verify Update with duplicate 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.

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

C.DOB corresponding Message. click Password objects and Ok. C. word Logout functionalities. Search. C. Search. C. data click on Ok Step-3 Click on Add -It should display Add Customer page with C. Info_Admin_ validates on Go Cancel functionalities.No. Page with User Name. Step-4 Enter invalid C.Name C.Suresh.Addr.Addr.PhNo E-mail C.Name. case Customer Address.Addr. word Logout functionalities.B –9440163282 suresh_240878@yahoo.DOB C.DOB. 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. click on Ok Step-3 Click on Add -It should display Add Customer page with C. Page with User Name. C. Cancel functionalities. C.Name C. Info_Admin_ validates on Go Cancel functionalities. 42 Manual Testing . TC06_ enter Url.DOB C. meaningful Error C.PhNo E-mail Expected Result It should clear all fields and cursor should be present in the first field. TC05_ enter Url.. case Customer Address.Addr.Name It should display a data in C. 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.PhNo fields and E-mail click on Insert Url It should display Login This Test Step-1 Open Brower.Name.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.Addr. 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. Reset. Email objects and Insert..Ph. click Password objects and Ok..

C. Address. should display Enter valid User It Information User Name Name Customer and Password & Pass page with Add. C. click on Ok 43 Manual Testing   .. Email objects and Insert.Addr.Ph.Addr. Cancel functionalities. click Password objects and Ok. C. C. on Go Cancel functionalities. Reset.No. C.Name It should display a Enter duplicate data C.DOB. word Logout functionalities. C. Search. click Password objects and Ok.DOB in Message. click on Ok Click on Add -It should display Add Customer page with C. Address.PhNo missing some E-mail mandatory fields and click on Insert Open Brower. Search.Addr. Page with User Name.DOB. Url It should display Login enter Url..suresh_240878@yahoo. C.DOB fields by Message.PhNo corresponding E-mail fields and click on Insert Open Brower. meaningful Error C. Reset. Cancel functionalities. Page with User Name.Name It should display a corresponding C.Name. on Go Cancel functionalities. meaningful Error C..No. should display Enter valid User It Information User Name Name Customer and Password & Pass page with Add.Ph. Url It should display Login enter Url. Enter data in C. word Logout functionalities. Email objects and Insert.com Suresh.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.

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

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

Name corresponding C.DOB. Reset.Name. click Password objects and Ok. Delete.No. C.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. Search.Name. C.ID data in C.DOB C.DOB fields and click C.PhNo E-mail C..ID.Name C. Cancel. C. Home functionalities. Info_Admin_ validates on Go Cancel functionalities. C.B –9440163282 suresh_240878@yahoo.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.. Cancel.Addr.Ph. C.No.. Reset.DOB C. C. C.Suresh.Name done” message. C. It should display Edit Page with C.Ph.Addr. objects and Search. C. case Customer Address.ID.DOB.Name. TC13_ enter Url. Home functionalities. word Logout functionalities.ID C. It should clear all fields and cursor should be present in the first field. ‘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 functionalities. objects and Search.No. C. click on Ok Step-3 Click on -It should display Search Search Page with C. C.ID It should display “Update C..ID. Page with User Name. It should display Search Results Page with Customers Information and Edit.PhNo E-mail . C. Step-4 Enter valid C.DOB. E-mail objects and Update.Ph. 46 Manual Testing C. C.Addr.

Name corresponding C. C. Home functionalities. Password objects and Ok. C.ID data in C.suresh_240878@yahoo.DOB 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.ID. It should display Edit Page with C.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.Name.com Suresh. objects and Search.Addr.Ph.DOB.DOB fields and click C. C. Step-4 Enter valid C. It should display Search Results Page with Customers Information and Edit.PhNo on Search It should display Login Page with User Name. It should display Search Page with C. Cancel functionalities. E-mail objects and Update. Home functionalities. C. Cancel functionalities. Cancel. C. C. C.ID data in C. Search.ID C.Addr.Name C. C. Cancel.Ph. Logout functionalities.B –9440163282 Test Case name Test Case description Step Name Step Description Test Data Expected Result Reset. Reset. It should display meaningful error message.PhNo E-mail Url User Name & Pass word -- Step-4 Enter valid C.DOB. Delete.DOB fields and click C. TC14_ enter Url. Cancel.Name corresponding C. Reset. Cancel functionalities.No. case Customer Address..ID. Home functionalities.Name. It should display Customer Information page with Add... 47 Manual Testing   . Delete. It should display Search Results Page with Customers Information and Edit.No.

Name.Addr. Enter valid C. C. Cancel.No.DOB.PhNo fields click on E-mail update Open Brower. Manual Testing 48 .DOB. Cancel functionalities.No.ID. Address.B –9440163282 suresh_240878@yahoo. E-mail objects and Update.ID It should display Search data in C.DOB. - Step-5 Select a Customer data click on Edit It should display Edit Page with C.Name. C.Name meaningful duplicate data error C. Reset...No.. E-mail objects and Update. C.DOB in message. Search. Home functionalities. Cancel.Suresh..Name.PhNo and Edit. C.Ph.ID. Url It should display Login enter Url.Addr.ID.. C. C. Reset. corresponding C.ID Enter It should display C. C. objects and Search. C.DOB corresponding Customers Information fields and click C.Addr. C. on Go Cancel functionalities.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. Delete. click Password objects and Ok. click on Ok Click on -It should display Search Search Page with C. Reset. word Logout functionalities. C. C. Page with User Name.Ph. Home functionalities. C.Ph. Enter valid User It should display User Name Name Customer Information and Password & Pass page with Add. on Search Home functionalities. C. Cancel.Name Results Page with C.

Reset.DOB.Name.PhNo E-mail Url User Name & Pass word -- Step-4 Enter valid C. Password objects and Ok..PhNo E-mail 49 .ID It should close current C. Home functionalities. C. Info_Admin_ validates Address. objects and Search. E-mail objects and Update. It should display Edit Page with C.Ph. Cancel functionalities. Reset.com Suresh. Logout functionalities.ID.Name.ID It should C.. C. C.ID. C. It should display Search Results Page with Customers Information and Edit.DOB. C.Name corresponding C. Search.ID data in C.DOB Previous Page. Customer case enter Url. C.No. Cancel functionalities.No.Addr. Step-5 Select a Customer data click on Edit Step-6 Enter data in corresponding fields and click on Cancel Manual Testing   C.DOB message.Ph.DOB fields and click C. Cancel. Home functionalities. C. Delete.Name meaningful C. C. It should display Customer Information page with Add.suresh_240878@yahoo. It should display Search Page with C.. C. C. Cancel.Addr. 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.PhNo on Search - It should display Login Page with User Name.Addr.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.Name page and display C. C.

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

It should remove customer’s information with “Customers Information was successfully deleted”. enter Url.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.Name corresponding C. It should display Search Results Page with Customers Information and Edit.Name corresponding C. C.Ph. Cancel.DOB fields and click C. C. case Address.com Suresh.. Delete. C. Delete. It should close current page and display previous page. It should display Search Page with C. Search. Logout functionalities.ID.DOB. Cancel.DOB fields and click C.DOB.Name. 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. Cancel functionalities. Home functionalities. It should display Customer Information page with Add. Cancel functionalities. Reset. 51 Step-4 Enter valid C.No.ID data in C. C.suresh_240878@yahoo. Reset. objects and Search. C.ID.No.Name. objects and Search.PhNo on Search - Step-5 Select a Customer data click on Cancel Manual Testing   .. Home functionalities. C.ID data in C. Password objects and Ok.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.Ph. Cancel functionalities. It should display Login Page with User Name. It should display Search Results Page with Customers Information and Edit.

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

suresh_240878@yahoo.com Suresh. Mandatory. 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 .B –9440163282 User Name User Name object allows alphabets lower case range from 4 to 8 characters. Range from 4 to 12 characters. First letter should be Upper Case. 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. 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.

Characters mentioned –/#. Characters 54 Manual Testing . 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. Customer Ph. Mandatory. object allows Numeric Only. The format is MM/DD/YYYY.Suresh.B –9440163282 suresh_240878@yahoo.. BVA & ECP for Customer Ph.No. Date should be less than current system date.”) Maximum of 20 Characters. Characters mentioned –/#. Allows 10 digits only. Customer Ph. 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. Mandatory. 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.No.” “..com  Customer Address Customer Address object allows alpha-numeric and some special Characters (“–“ “/” “#” “.No. Customer DOB Customer DOB object allows Numeric Only. Phone number is unique. Mandatory.

D.168.168.Addr.1.U. Name Name required Stephttp://192.0 Url 1 /Customer Info 1.B –9440163282 TEST DATA DOCUMENT Project Name Reviewed by Module Name Created By Reviewed on Created on Sl. Brundavancolony7/G-3   Manual Testing   55 .Name pava Verify Cancel 2 Password ganesh Stephttp://192.1.1.suresh_240878@yahoo.Name Ramakrishna Stepwith Valid data Koteswararao 5 Koti.168.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.0 Url 1 /Customer Info 1.0 Step.0 Url 1 /Customer Info 1.com Suresh. Test Case Step Data Data generated Comments No.168.0 Customer 3 Info_Admin_ Step.Name pava TC04_ 2 Password ganesh Customer Ramu 4 Info_Admin_ Sita Verify Insert C.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.No.0 TC03_ Url 1 /Customer Info 1.1.U.-5/G C.

0 Url 1 /Customer Info 1.Suresh.0 Step.0 Url 1 /Customer Info 1.1. 9440163282 suresh_240878@ E-mail yahoo.com Step1 Url http://192.No.DOB 05/25/1976 4 C. Brundavanacolony Step7/G-3 4 C. Brundavancolony7/G-3 Step.Ph.U. +91-9440163282 suresh_240878# E-mail yahoo.Name pava 2 Password ganesh C.No.0 /Customer Info 1.168.No.168.DOB 05/25/1976 4 C.0 Step.com  Sl.Ph.C.Addr.C.Name pava 2 Password ganesh Sai C.DOB 25/10/1976 C.com Stephttp://192.168.U.Name Koteswararao C.DOB 05/25/1976 C.0 Step.1.Name pava 2 Password ganesh C.1.com Stephttp://192. Brundavancolony7/G-3 Step.Name Koteswararao C.B –9440163282 suresh_240878@yahoo.Addr. 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. No.Addr.0 Url 1 /Customer Info 1. 9440163282 suresh_240878@ E-mail yahoo.0 Manual Testing 8 56 .168.No.com Stephttp://192. 9440163282 suresh_240878@ E-mail yahoo.1.U.Ph.Ph.Name Saisarvanibug Brundavancolony7/G*3 C.

9440163282 Manual Testing   57 .Name Koteswararao C.Name Password C.0 Url /Customer Info 1. No. C.Name C.com http://192.0 U.No.No.B –9440163282 Sl.DOB C.com Suresh. Test Case Name Verify Cancel Step Data Name required Step2 Step4 Step1 Step2 Step5 U.1.168.Ph.Name pava Password ganesh C. 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.suresh_240878@yahoo.DOB 05/25/1976 C.Ph.Addr.

During Test Case execution Testers are receiving modified build from the developers. Traceability Matrix Template Project Name Prepared By Prepared on Sl.B –9440163282 suresh_240878@yahoo.com  Review on Test Cases After completion of Test Case preparation. Testers are receiving initial build from the development people. Testers required a valid negotiation / communications with developers like as below.Suresh. 58 Manual Testing . (RTM) RTM defines the mapping between requirements and Test Cases. 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. To receive any type of build from the developers. No. 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. Test lead is mapping Test Cases with Requirement Traceability Matrix Document.

B –9440163282 Developers COMMON REPOSITORY / SOFT BASE 1.A.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.0 3.0 2.com Suresh.T Manual Testing   Golden Build Sign off 59 .

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

If Yes: It is reproducible.com Suresh.suresh_240878@yahoo. 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. Defect Report Format 1) Defect ID Unique for future reference. 2) 3) 4) Summary Brief description of the defect. If No: It is not reproducible. Status Status of the defect. 5) 6) Manual Testing   61 .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. attach test procedure. attach test procedure along with snap shots. Testers are reporting mis-matches to development Teas as “Defect” in Defect Report Document. They are (2) types (i) New–Reporting for first time. b. Features The name of the feature / functionality in which defect. a.

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.com  7) Severity (Seriousness with respect to Testers) It means seriousness of the defect with respect to Tester or seriousness of the functionality. 9) 10) 11) 12) 13) 62 Manual Testing .Suresh. 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.B –9440163282 suresh_240878@yahoo. 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. Resolved on Date and Time Resolution Type: Acknowledgment from the developers for the reported defect.

What is Build Internal period? The time gap between two consequent builds is called as Build Internal period.suresh_240878@yahoo.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..com Suresh. Dead lock etc. Manual Testing   63 . 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. Showstoppers.

Case Study Modified Build High Severity All P0. LEVEL ‘2’ TESTING After receiving the modified build from the developers. P1. not rejected due to developer need more information about that defect.B –9440163282 suresh_240878@yahoo. P2 Test Cases Enhancement All P0. P2 Test Cases 64 Manual Testing . 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. some P1. P1. P2 Test Cases Medium Severity All P0. Duplicate: The defect is rejected due to defect is previously accepted defect. & Selected P2 Test Cases Low Severity Some P0 & Selected 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.Suresh. Deferred: The defect is postponed to next version / release.

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

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