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

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

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

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

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.com Suresh.” 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 –9440163282 Programmers are checking the completeness and correctness of the Test. Manual Testing   7 . Programmers are interconnecting to form a system. The verification of main module without coming to some of the Sub-Modules is called as Top-Down Approach.suresh_240878@yahoo. it works like as under constructive Main Module. it works like as under constructive Sub Module. Driver is also known as Calling Program. To estimate the interface between programs or modules programmers are conducting Integration Testing. “Conducting test on Sub-Modules without testing on Main Module is called Bottom-up Approach. it is also called as Called Program. a) Top-Down Approach. 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. They are (4) Types of approaches. The verification of Sub-Modules without coming from 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.

CASE STUDY Case 1: Top-down approach is followable. 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”.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.Suresh. This approach is not suitable for large modules. when the customer’s requirements are clear and the architecture structure of the system is changing.B –9440163282 suresh_240878@yahoo. Case 3: Hybrid 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. when the customer’s requirements are constituent of clear. when the application build consists less number of modules or less number of interconnections. 8 Manual Testing . Case 4: Bigbang Approach is followable. Case 2: Bottom-up approach is followable.

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

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

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

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

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

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

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

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

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

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

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

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

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 . Validation To check whether the developed product is right or not. In V-Model V stands for “Verification and Validation”. Software Testing The “Verification and Validation” of a Software is called Software Testing.com Suresh. Verification To check whether the people are developing right product or not.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.

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

The Re-execution of selected test or modified build.B –9440163282 Re-Testing. 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.com Suresh.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. to check is there any side effects occurred or not on dependent functionalities by modifying reported defects or by adding new requirements.A. 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. Case 1: The repeating of same test for more than one time with multiple data is called as “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

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

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

suresh_240878@yahoo. 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. 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. In measurements there are (3) types such as (1) Quality Assessment Measurement (2) Test Management Measurement (3) Process Capability Measurement. 12) Training Plan: The required training secession to the Testing team to understand about the project.B –9440163282 8) Defect tracing & Reporting. 10) Change & Configuration Management How to handle change request from the customer and how to store the documents for future reference. Manual Testing   29 .

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

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

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

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

it should return meaningful message) 3) Validation Test Cases: Test Cases that are required to validate business rules or field validation. Thinks to remember while designing the Test Cases. 4) Functional Test Cases. b) Tab keys should be implemented for all input objects from left to right in downward direction. 2) Test Case should be complete. 2) Usability Test Cases To verify ease of use of application build screens. Ex: a) Default cursor should be present at the first field. c) Shortcut keys should be implemented for all menu operation.B –9440163282 suresh_240878@yahoo. Images etc.Suresh. 3) No duplicate Test Case should b written. TEST DESIGN TECHNIQUES They are mainly (5) types of design techniques. Ex: Font Size. 3) Validation Test Cases. 2) Usability Test Cases. Text alignment. 4) Functional Test Cases: Test Cases that are required to validate the functionality. TEST CASE TYPE 1) User Interface 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. 1) User Interface Test Cases To verify the look and Feel of application build screens. (1) Boundary Value Analysis (BVA) (2) ECP (Equal Class Partition) (3) Error Guessing (4) Decision Tables (5) State transition. 34 Manual Testing .. 1) Test Case should be simple and clear.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.com Suresh.suresh_240878@yahoo. Range from 4 to 12 characters. Mandatory. 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. 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.

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

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

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

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

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

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

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

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

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.com  7) Severity (Seriousness with respect to Testers) It means seriousness of the defect with respect to Tester or seriousness of the functionality. 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.Suresh. Suggested to fix Suggestions to developer to fix the defects By Developers Fixed By: Name of the Programmer who fixed the defect.B –9440163282 suresh_240878@yahoo. 9) 10) 11) 12) 13) 62 Manual Testing . Approved by Signature of the Team Lead / Project Lead.

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

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

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

B –9440163282 suresh_240878@yahoo. (ii) Known issues 66 Manual Testing .Suresh. At development site. It consists of (2) issues such as (i) User Manual. At customer site. By Real customer. Signoff After completion of User Acceptance Testing and corresponding modifications. 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).com  User Acceptance Testing After completion of “Test Closure” the Project Manager collects feedback from the customers on developed software through “User Acceptance Testing”. By Model customer. Software Product.

Sign up to vote on this title
UsefulNot useful