Transcript
Page 1: Complete guide to manual  testing@uma

MANUAL TESTING

1) Q. Why did you choose testing ?

Ans: 1) Scope of getting the job is very very high.

2) No need of depend upon any technology.

3) Testing is going to be there forever.

4) I want consistence through out my life.

2) Q. What exactly we need to get a job?

Ans: 1) Stuff

2) Communication skills [reading+ writing + speaking+ lesion]

3) Confidence

4) Dynamism

3) Q. Why explicitly the test engineers are been recruiting in to the software companies?

Ans: 1) Once person cannot perform two tasks efficient at a time.

2) Sentimental attachments.

4) Q. Who can get testing job?

Ans: Any graduate who is creative can get testing job very easily

5) Q. Why explicitly the testing engineers are been recruited into the software companies?

Ans: 1) One person can’t perform two task efficiently at a time.

2) Sentimental Attachment.

PROJECT:-

Project is something that is developed based on the particular customers requirements and used by that particular customers only.

1

Page 2: Complete guide to manual  testing@uma

PRODUCT:-

Product is something that is developed base on the companies specification and used by the multiple customers.

NOTE:- The company will decide the specification by picking the common requirements of customer.

6) Q.Classical definition of quality?

Ans: Quality is defined has justification of all the requirements of a customer in a product.

NOTE: Quality is not defined in the product it is defined in the customer mind.

DEFECT: Defect is defined as deviation from the requirements.

7) Q. Latest definition of quality?

Ans: Quality is defined as not only the justification of the requirements but also presence of the value [value ..means ..user friendly]

8) Q. What is testing?

Ans: Testing is a process in the defects are Identified, Isolated[separately],Subject for Rectification[sending] Ensure that the product is defect free in order to produce a quality product in the end and hence customer satisfaction.

9)Q. What is bidding the project?

Ans: Bidding the project is defined as request are proposal, estimation and signing off(official-agreement).

KICK OF MEETING :- Kick off meeting is the initial meeting conducted in the software company soon after the project is signed off in order discuss the overview of the project once select project manager for that project.

Us ally

High level management [HLM]

Project managers [PM]

Quality managers [QM]

Technical managers [TM]

Development leads & Test leads

2

Page 3: Complete guide to manual  testing@uma

Will be involved in this meeting Apart from them many times customer representations also

Will be involved in this meeting.

NOTE:- Apart from this meeting any other start up meeting in also called as “kick off meeting”.

PIN [ Project Initiation Note]:- PIN It is a mail prepared by the project manager and sent the CEO of software company as well as to all of his core team members in order to intimate then that they are about to start the actual project activities.

CEO=Chief Executive Officer

COO=Chief Of Officer

SDLC [Software Development Life Cycle]:-

It contains 6 Phase

Initial or Requirement Phase

Analysis Phase

Designed Phase

Coding Phase (or) Programming phase

Testing Phase

Deliver and maintenance Phase

Initial or Requirement Phase:-

Task:-Interacting with the customer and gathering the requirements.

Roles:- i) Business Analyst [BA]

ii) Engagement manager [EM]

Process:- First of all the Business Analyst can Appointment . from the customer, collects the template from the company meet the customer an the appointment date gathers the requirements with the help of the template and come back to the company with the requirement documentary.

The Engagement manager will go through the requirements document. If at all he finds any extra requirements hence he will deal with the excess cast of project. If it is any confession of requirements then the will ask the consult team to develop the prototype he

3

Page 4: Complete guide to manual  testing@uma

will demonstrates to the customer gather the clean requirements and finally hand over the requirements document to the business analyst.

Proof:- Proof of this phase is “Requirements Document”.

This document is called with different name in different companies

FRS (Functional Requirements Specification)

CRS (Client or Customer Requirements Specification)

URS (User Requirements Specification)

BDD (Business Design Document)

BD (Business Document)

BRS (Business Requirement Specification)

NOTE:-Some companies may maintains two documents in the initial phase, one is for High level business flow information and the other in for Detail function information.

But some companies may maintains both the intimation in a single document.

Template:- Template in a predefined format which is used for preparing the document easily and perfectly

Prototype:- Prototype is a roughly and rapidly developed model which is used is for demonstration to the customer in order to gather the clear requirement and also to win his confidence of the customer.

Analysis phase:-

Task:-

Feasibility study

Tentative planning

Technology selection & Environment conformation

Requirement analysis

Roles:-

System Analyst [SA]

Project Manager [PM]

Team &Technical Manager [TM]

4

Page 5: Complete guide to manual  testing@uma

Process:-

Feasibility study:- (possibility) It is a detailed study conducted on requirement in order to conform whether all of those requirements are possible with in the given time budget and resources are not.

Tentative planning (Temporary):- The resource planning as well as scheduling will be temporary planned section.

Technology selection & Environment conformation:- The list of all the technologies that are required to accomplish this project successfully will be enlisted as well as the client environment will be conformed here in this section.

Requirement analysis:- The list of all the requirements that are required by the company like human resource , software and hardware to accomplish that project ,successful will be enlisted and mentioned here in this section.

Proof: The proof document if the analysis phase is SRS (System Requirement Specification )

Designed Phase:-

Task:- i) High Level Designing [HLD]

ii) Low Level Designing [LLD]

Roles:- i) Chief architect (CA) : is responsible for high level designing.

ii) Technical Lead (TA): is responsible for low level designing.

Process:- The chief architect will divided whole project into modules ,by drawing some diagrams using a language UML(Unified Modeling Language)

The technical lead will divided the modules into sub modules by drawing some diagrams using the same UML.

Apart from this takes GUI design also will be done in this phase.

Some time pseudo code also will be developed in this phase.

Proof:- The proof document of this phase is TDD (Technical Design Document)

Pseudo code:-It is set of English statement which used for developing in the actual code very easily and comfortably.

5

Page 6: Complete guide to manual  testing@uma

Coding Phase:-

Task:- coding (or) programming

Roles:-Developers (or) programming

Process:- The developers will develop the actual source code with the support of technical design document as well as by following the coding standards.

Example for coding standards:

Proper indentation

Color coding.

Proper commenting.

Proof:- The proof document of the coding phase SCD (Source Code Document).

Testing phase:-

Task:- Testing

Roles:- Test engineers

Process:-

Test engineers will receive the requirement document and will start understanding the requirement.

While understanding the requirement if at all the get any doubt then they will list out all the doubt in the requirements clarification note and will send it to the author of the requirement doubt BA(Business Analyst).

Once the clarification are given if still more clarification are required then they will conduct a review meeting and will get all the clarification.

Once all the requirement are clearly understood then they will take the Test case template and will write the test cases.

Once the 1st Build is released they will execute the test cases.

If at all any defects are found they will list out then in the defect profile and will send it to the development department .

Once the next Build is released they will re execute the required test case.

If at all any more defect are found they will update the defect profile and will send it to the development department.

6

Page 7: Complete guide to manual  testing@uma

Once the next Build is released the same process will be continued.

This process will be continued again and again till the product is defect free.

Proof:- The proof the testing phase is Quality Product .

Test Case:- If is an Idea of test engineer to test something based on the requirements.

Delivery & Maintains Phase:-

Delivery:-

Task:- Hand overring the application to the client .

Roles:- Deployment Engineers or Installation Engineers

Process:- Deployment engineers will go to the clients place , install the application into the original customer ,Environment and finally hand over’s the software to the customer.

Proof:- The final official argument made between the company and the customer is the proof document this phase.

Maintains:- Once the customer start using the application if at all any problem occurs then that problem will become the task ,based on the task corresponding roles will be appointed ,these roles will define the process, solves the problem and final get the Application latter.

Some customer many request for continuo’s maintenance in that situation the company will send a team of member to the customer place continuously in order to take care of that software.

Q. where exactly testing comes in to picture?

Which sort of testing you are expecting?

How many sort or testing are there?

Ans:- They are two sort of testing

i) Un convectional testing.

ii) Convectional testing.

Un convectional testing:- It is a sort of testing in which the quality assurances people. Will check each and every role in the organization in order to conform weather they are doing their work according to the companies proper guidelines are not. Right form the staring of the SDLC to the end of it.

7

Page 8: Complete guide to manual  testing@uma

Convectional testing:- It is a sort of testing in which the test engineers will check the developed application (or) its related parts are working according to the expectation or not from the coding phase to the end of the “SDLC”

Methods of the testing (or) testing techniques:-

Basically there are two methods of testing.

i) Black Box testing.

ii) White Box Testing (or) Glass Box Testing (or) Clear Box Testing

Black Box Testing:- It is a method of testing in which one will perform testing only on the Functional part of an application with out on the having the knowledge of structural part.

Usually the black box Test engineers will perform it.

White Box Testing:- It is a method of testing in which one will perform testing on the Structural part of an application .

Usually developers (or) White box testers will perform it.

Gray Box testing:- It is a method of testing in which one will perform testing on both the functional part as well as the structural part of an application.

Usually the test engineers who have the knowledge of structural part will perform it.

Levels of Testing:-

There are five levels of testing

Unit level testing.

Module level testing.

Integration level testing.

System level testing.

User acceptance level testing.

Unit level testing:-

Unit:- Unit is defined as smallest part of an application.(program)

In this stage the white box testing will test each and every developed program and also the combination of programs.

8

Page 9: Complete guide to manual  testing@uma

Module level testing:-

Module:- Module is defined as a group of related features to perform a major task in the application.

In this stage the Black box test engineers will test the functional part of the module.

Integration level testing:- In this stage the developers of will develop some interface(linking program) in order to integrate the modules this interface will be tested by white box testers. Developers will follow any one of the approaches white integration the module.

Top down approaches

Bottom up approaches

Hybrid approaches (or) Sand rive approached

Big-Bang approaches

Top down approaches:- In this approaches the parent modules will be developed first and then the corresponding child modules will be developed and integrated.

STUB:- While integrating the modules in top down approach if at all any mandatory modules are missing then that mandatory modules will be replace with a temporary program.

9

Page 10: Complete guide to manual  testing@uma

Bottom up approach:- In this approached the child modules will be developed first and will be integrated to the corresponding parent modules.

DRIVER:- While integrating the module in bottom up approached if at all any mandatory modules is missing then that modules is replaced with a temporary program “DRIVER”

Hybrid approach (or) San drive approach:- This a mixed approach of Both top down and bottom up approaches.

10

Page 11: Complete guide to manual  testing@uma

Big-Bang approach:- In this approach one will wait till all the modules are developed and finally will integrate then at a time.

System level testing:-

System:- Once the software application is installed in to an environment then as a whole we will call it as a system.

In this stage the block box test engineers will conduct many type of testing like load testing, performance testing, stress testing, comparability testing, system integration testing……..ect.

System integration testing:- It is a type of testing in which on will perform some action on module and check for the reflections in all the related are as of the application.

User acceptance level testing:- In this stage the block box test engineer will perform testing on the user desired areas in the presence of accept the application happy.

Environment:-

Environment defined as group of hardware compounds with some basic software (OS) where one can install the Presentation Logic, Business Logic, Data Base Logic.

[or]

Environment defends as combinations of three layer that is Presentation Layer, Business Layer, Data Base Layer. Where once can install the Presentation Logic, Business Logic, Data Base Logic.

11

Page 12: Complete guide to manual  testing@uma

Type Of Environment:-

Stand Alone Environment (or) One Tier Architecture.

Client Sever Environment (or) Two Tier Architecture.

Web Based Environment (or) Three Tier Architecture.

Distributed Environment (or) N-Tier Architecture.

Stand Alone Environment (or) One Tier Architecture:-

In this environment only one tier will be there. Presentation layer, business layer, data base layer will be present in the same tier.

When ever the application need to be used by single user at time then environment will be suggested.

Client Sever Environment (or) Two Tier Architecture:- In this environment two tier will be there .one is for client and another is for data base server. Presentation layer and the business layer will be available is each and every client and the data base player will be present in data base server.

When ever the application need be used single premises and there is no problem with the security of the. Business logic as well as the application need accessed very fast lye then this environment be suggested.

12

Page 13: Complete guide to manual  testing@uma

Web Based Environment (or) Three Tier Architecture:- In this environment three tier will be there one is for clients, the middle is one is for application sever and the other is for data base sever. presentation layer available in the client business layer will be available in the application server. data base sever.

When ever the application need to be used all over the world by limited numbers of user and wounds the business logic will be secured and function updaters to be easily them the in environment can be suggested.

13

Page 14: Complete guide to manual  testing@uma

WEB SERVER:- Web server is a software which provides web services to the client.

EX:- IIS(Internet Information Services)

Distributed Environment (or) N-Tier Architecture:-This environment is same as web environment more the one application sever is introduced in separate hers in order to distributed the load and increase the performance.

When ever the application needs to be use by huge number of user then this environment can be suggested.

THIN CLIENT:- If at all the client machine is having only the .presentation logic then it is know as thin client.

THICK CLIENT:- If at all the client machine is having both presentation logic as well as business logic then it is known as thick client.

APPLICATION:- It is a Presentation Layer, Business Layer, Data Base Layer.

SOFTWARE DEVELOPMENT PROCESS MODELS:-

Waterfall Model

Prototype Model

Evolutionary Model

Spiral Model

Fish Model

V-Model

14

Page 15: Complete guide to manual  testing@uma

Waterfall Model:-

Phase Activity Outcome

UNIT TEST

INT .TEST

MOD TEST

SYS TEST

UAT

Advantages:- It is a simple model and easy to implement.

Project Monterey and maintains is very easily.

Draw Back:- Can’t accept the new requirements in the middle of the process.

15

INTIAL

ANALYAIA

DESIGN

CODING

TESTING

DELIVER & MAINENENCE

BRS

SRS

TDD,GUI

UTR

ITR

MTR

STR

UATR

DELIVERY TO CLIENT

REQ & GATHERINGNG

SYS, DESIGN

S/W DESIGN

IMPLIMENTATION

BLOCK BOX TESTING

Page 16: Complete guide to manual  testing@uma

Prototype Model:-

Advantage:- when ever the customer is not clear with his requirement. Them this is best suitable model

Draw Back:- Is not a compiled develop process model.

It’s a still time consumer model.

Company should where the cost of prototype

User may limit requirement by sticking into the project.

16

UN CLEAR REQ.

PROTOTYPE

S/W PROTOTYPE

H/W PROTOTYPE DEMO TO CLIENT

DEMO TO CLIENT

REQ. ARE REFINEDBRS DOC. BASE LINED

CLIENT ENVIRONMENT CONFORMATION

SRS DOC. BASED LINED

Page 17: Complete guide to manual  testing@uma

Evolutionary Model:-

APPLICATION

BASE LINE

Advantage:- when ever the customer is evolution the requirement then this is the Best suitable model

Draw Back:- time consuming model

Costly model

Deed lines can’t properly define.

No transference.

Project monetary any maintenance is very difficult.

17

INITIAL REQ.

DEVELOP

APPLICATION USER VALEDATION

FEED BACK WITH NEW REQ.

USER ACCEPT

NO

YES

Page 18: Complete guide to manual  testing@uma

Spiral Model:-

1) DEINING THE OBJECTVES /WORK ANALYSIS/CONSTRAINTS

4)REFINIG &

PLANNING 2) RISK ROOT

FOR THE NEXT CYLE CAUSE

ANALYSIS

ESTIMATION

3) IMPLEMENATION CONTINGENCIES

Advantage:- When ever the project highly risk based then this is the best suitable model.

Draw Back:- Time consuming model.

Costly model.

Risk root cause analysis is nota easy task.

18

Page 19: Complete guide to manual  testing@uma

Fish Model:-

REQ ANAYSIS DESIGN CODING DELIVERY MAI-GATHERING SYSTEM Testing Maintan

SRS HLD SCD

BRS REVIEW LLD BLOCK Box Testing

Test S/W

SRS REVIEW TDD REVIEW WHIT BOX TESTING Changes

Advantage:- As both the verification are done the outcome will be a quality product.

Draw Back:- Time consuming.

Costly model.

V-Model:-

Verification Validation

INITIAL & BRS PREPARING PROJECT PLANNINGANALYIS SRS PREPARING TEST PLANNING

DESIGN & TDD DESIGN PHASE TESTING CODING SCD PROGRAM PHASE TESTING

TESTING S/W BUILD SYSTEM TESTING TEST MANAGEMT PROCESS USER ACCEPTANCE TESTING

DEVIVER & PORT TESTINGMANINTENANCE S/W EFFICIENCY DRE= A TEST S/W CHANGS A+B

A= Defects found by the testing team.B= Defects raised by the customer.Advantage:- As both the verification and validation is done and test management process is maintained. The outcome will be quality product.Draw Back:- It is time consuming model. It is a costly model.

19

Page 20: Complete guide to manual  testing@uma

Verification:- Verification is a process of checking whether the product is being developing in a right manner or not.

Validation:- Validation is a process of checking whether the develop product is right or not.

TYPE OF TESTING:-

Build acceptance testing (or) Build verification testing (or) Sanity testing

Regression testing

Re testing

Half- testing

B-testing

Static testing

Dynamic testing

Instillation testing

Compatibility testing

Exploratory testing

End-To-End Testing

Security testing

Usability testing

Reliability testing

Mutation testing

Adhoc testing

Build acceptance testing (or) Build verification testing (or) Sanity testing:-20

Page 21: Complete guide to manual  testing@uma

It is a type of testing in which one will conduct overall testing one the released build in order to conform where the proper of not for conducting detailed testing

In this type of testing us ally they check the following.

i) Weather the build can be properly installed in to environment or not

ii) Weather one can navigate to all the pages of the application or not.

iii) Weather all the important feature are available or not.

iv) Weather all the requirement connections are properly established or not.

In some company they will call this types of testing as Smoke testing also but in some companies they say that just before releasing the build the developer will check weather the build is proper or not i.e. know as Smoke testing.

Once the build is released the testing engineers will once again check weather the build is proper or not i.e. knows as BAT (or) BVT (or) sanity testing.

Regression testing:- It is a type of testing in which one will perform testing on the ready testing functionality again and again us allay it is done in two servicers.

i) When even some defects are identified raised to the development department once the next build is released the testing engineers will check the defect functionality as well as the related functionality once again.

ii) When ever some new feature are added i.e. the application next build is released to the testing department then the test engineers will check all the related feature’s of those new feature’s once again.

NOTE: - Testing new features for the first time not regression testing.

Some companies may do Random testing at the end that also will fall under regression testing only.

Retesting: - It is a type of testing in which one will perform testing on the same functionality again and again with multiple sets of data in order come to a conclusion weather the functionality is working fine or not.

NOTE:-

21

Page 22: Complete guide to manual  testing@uma

i) Regression testing starts form the 2nd build and continue up to the last build.

ii) Re testing starts from the 1st build and continuous up to the last build.

iii) During regression testing also re testing will be conducted that is the reason some people even call it as Re and Regression testing.

Half testing: - It is a type of testing user accepting testing conducting in the soft ware company by the test engineers just before the delivery.

B-testing: - It is a type of testing user accepting testing conducting in the client place either by the end user (or) by the third party testing experts just before actual implementation of a application.

Static testing: - It is types of testing in which one will perform testing on the application on its related factors without perform any action.

EX: - GUI testing, Document testing, code--------------ect

Dynamic testing: - It is types of testing in which one will perform testing on the application on its related factors by perform some action.

EX: - retesting, functionality testing…….ect.

Instillation testing :- It is a type of testing in which one will trey to instillation the application by following the guide ling provided in the deployment document in order to conform whether those guidelines really suitable for instillation the application comfortable (or) not.

Compatibility testing:- It is type of testing in which one will install the application into multiple environment prepared with different .combation in order to check .whether it is suitable with those environment (or) not.

Monkey testing: - It is type of testing in which one will intentionally perform some action in order to check stability of the application.

Port testing: - It is type of testing in which one will install the application into the original customers environment and check whether it is comprisable with that environment (or) not.

Exploratory testing:- It is type of testing in which Do many expert will check the functionality of the application which out having the knowledge of requirement just by parallel exploring the functionality.

Exploratory: - Have in the base knowledge of some concept doing something and more about it is knows as exploratory.

22

Page 23: Complete guide to manual  testing@uma

End-To-End testing: - It is type of testing in which one will perform testing on all the end to end sceneries of the application.

Ex:- login

Balance enquiry ----10,000

With draw -------3,000

Balance stmt ----------7,000

Logout

Security testing:- It is type of testing in which one will perform testing on the application in order to conform whether it is properly protected (or)not.

i) Authentication testing : It is a type of security testing in which one will enter different combination of user names and password .and check whether only authorized people are able to access the application (or)not.

ii) Direct URL testing: It is type of security testing in which one will enter the direct URL’s if secured pages and check whether they access (or) not.

URL [Uniform Resource Location]

iii) Fire wall leakage testing (or)User realized testing :- It is type of testing in which one will enter into the application as a authorized user and will try to access bye and his limited in order to conform whether he can access (or)not.

Usability testing:- It is type of testing in which one will check the user friendly of the application.

Reliability testing (or) Socking testing:- It is type of testing in which one will use the application continues for long period of time in order to set the stability of the application.

Mutation testing:- It is type of testing in which one will perform testing on the application or its related factors after doing some changes to them.

Adhoc testing:-It is a type of testing in which one will perform testing on the application in the there own style after understanding requirement very clearly.

Us ally this type of testing will be encouraged after formal testing.

SOFTWARE TESTING LIFY CYCLE (STLC):- STLC contain 6 phase

i) TEST PLANNING

23

Page 24: Complete guide to manual  testing@uma

ii) TEST DEVELEPOMENT

iii) TEST EXECUTION

iv) RESULT ANALYSIS

v) BUG TRACKING

vi) REPORT

Test planning:- Test plan is strategic document which contains some information that describes how to perform testing on that application in a effective ,efficient and optimized way.

Plan:- Plan is a strategic document which contain some information that describe how to perform task in a effective, efficient and optimization.

Optimization:- Optimization is a process are utilizing the available resources to their level best and getting the maximum possible out put.

Index of test plan (or) Contents of test plan:-

1.0) Introduction

1.1) objective

1.2) reference document

2.0) Coverage testing

2.1) features be testing

2.2) features not be testing

3.0) Test strategic

3.1) levels of testing

3.2) type of testing

3.3) test design techniques

3.4) configuration management

3.5) test metrics

3.6) terminology

3.7) automation plan

3.8) list of automated tools

24

Page 25: Complete guide to manual  testing@uma

4.0) Base criteria

4.1) acceptance criteria

4.2) suspension criteria

5.0) Test deliverables

6.0) Test environment

7.0) Resources planning

8.0) Scheduling

9.0) Staffing and training

10.0) Risk and consistencies

11.0) Assumption

12.0) Approval information

1.0) INTRODUCTION:-

Objective: - Purpose of the document will be clearly described here in this section.

Reference document:- The list of the document that are referred will preparing this documents will be listed out here in this section

EX: - SRS, Project plan

2.0) COVERAGE TESTING:-

Features are tested: - The list of all the features with in the scope which are to be tested will be listed out here in this section.

Features not be tested:- The list of all the features that are not planed for testing will be listed out here in this section.

EX:- i) Out of scope features

ii) Low risk features

iii) Features that are planed to be incorporated in feature

iv) Features that are skipped based on the time constrains.

3.0) TEST STRATEGE:- (defines)

25

Page 26: Complete guide to manual  testing@uma

Test strategic is an organization level term which is common for all the project in that organization.

Test Plan:- Test plan is a project level term which is specific for that project only.

Level of testing: - the list of all the levels of testing that are maintained in the company will be listed out here in this section.

Type of testing: - The list of all the type of testing that all perform in that company will be listed out here in this section.

Test design techniques: - The list of all the techniques that used in that company while designing test cases will be listed out here in this section.

EX: - BVA, ECP

Configuration management:-

Test Metrics: - The list of all the metrics that are maintained on the company doing the test process will be listed out here in this section.

Ex: - Defect Metric

Test case Metric

Terminology: - The list of all the terms used in that company along with their meaning will be listed out here in this section.

Automation plan: - The list of all the areas that are planned for automation in that company will be listed out here in this section.

List of automated tools: - The list of all the automated tools that are used in that company will be listed out here in this section.

4.0) Base criteria:-

Acceptance criteria: - When to stop testing will be clearly described in this section.

26

Page 27: Complete guide to manual  testing@uma

Suspense criteria: - When to suspense testing will be clearly described here in this section.

5.0) Test deliverables: - The list of all the document that are to be developed of delivery doing testing process testing process will be mentioned here on this section.

6.0) Test environment:-The details of environment that is about to be used for testing will be clearly mentioned here in this section.

7.0) Resource planning:- Who has to do what will be clearly described here in this section.

8.0) Scheduling (or) Time planning:- The starting dates and ending dates of each and ever task will be clearly planed and mention in this section.

9.0)Staffing and training:- To accomplish that project sues fully if at all any staff requirement and if at all any training requirement then that detailed will be clearly mention here in this section.

10.0) Risk and Continence:- This list of all the potential risk and continence solution plan will be clearly mentioned here in this section.

Ex:- Employee may leave the company the middle of the project?

Ans. Employee need to mint on benched.

Unable to de clearly project with in the deadline project?

Ans. Proper plan insurance.

Costumer may impose the deadline?

Ans. What not be tested should planned.

Unable to test all the feature with in the given time?

Ans. Priority based the execution.

11.0) Assumptions: - The listed of all the think that are be assumed by the test engineer will be clearly mentioned here in this section.

12.0) Approached information:- Who has approval this document when it is approval will be clearly described in this section.

ii)Test development phase:-

Requirement Documentation

27

Page 28: Complete guide to manual  testing@uma

L USE CASES

Use cases:- Use case describes of the functionality of certain application terms of action response.

Login

i) Functional requirement

ii) Special requirement

Functional requirement:-

Login screen should contain user name, password connect to fields login, clear, cancel button.

Connect fields is not mandatory but it should be allow user to select the data base option when ever require.

Upon entering valid user name, password and clicking on login button corresponding page must be displayed.

Upon entering in to any of the fields and clicking on clearly button all the fields must be cleared and courser should he display in the user name.

Upon clicking on cancel button login screen must be closed.

Special requirement:-

28

HLI

L L I

SCREEN SHORT

User Name

Password

Login Clear

Cancel

Page 29: Complete guide to manual  testing@uma

Initial when ever the login page invoked login and when ever and clear button is disabled.

Cancel button must be all ways enable.

Upon entering some information in to and of the fields clear button must be enabling.

Upon entering some information in to both user name and password field’s login button must be enabling.

Tabbing order must be user name, password, connect to, login, clearer, cancel.

Use case template:-

i) Name of the use case

ii) Brief description of the use case

iii) Action in valued

iv) Special requirement

v) Pre condition

vi) post condition

Vii)Flow condition

Use Case Document:-

Name of the use case:-

i) Name of the use case: Login use case

ii) Brief description the use case: This use case describes the functionality of all the features present in the login screen.

iii) Actors involved: Normal user and Add mine user.

iv) Special requirement: two types

Explicitly requirement

Implicitly requirement

Explicitly requirement:- The requirement the explicitly given by the customer are know as explicitly requirement.

Implicitly requirement: The requirement that are analyzed by the business analyst which will add some value to the application with out disturbing any of the original customer requirements.

Explicitly requirement:-

29

Page 30: Complete guide to manual  testing@uma

Install when ever the login page invoked login and clear button is disables.

Cancel button must be any way enable.

Open entering some information into any the field’s clear button must be enabling.

Upon entering some information into both user name and password field’s login button must be enable.

Tabbing order must be user name password connect to login clear cancel.

Implicitly requirement:-

Open entering invalid user name valid password and click on login button the following error message must be displayed. “Invalid user name please try again”.

Upon entering valid user name in valid password and click on login button following error message must be displayed. ”invalid password please try again”

Upon entering invalid user name invalid password and click on login button following error message must be displayed. ”invalid user name and password please try again”

Initial when ever the login screen is invoked the curser must be display on the user name fields.

Precondition:- login screen must available.

Post condition:- Either home page (or) add mine and error message for invalid user.

Flow of events:- Two types

i) Main flow

ii) Alternative flow

Main flow:-

Action

Actors invoke the application. Actors entrees valid user name valid password and click on login button. Actors entrees valid user name valid password select a data base also and click on login

button. Actors entrees invalid user name valid password and click on login button. Actors entrees invalid password valid user name and click on login button. Actors entrees invalid user name invalid password and click on login button. Actors entrees some information into any of the field and click on clear button. Actors click on cancel button.

30

Page 31: Complete guide to manual  testing@uma

Response

Application display the login screen with the following fields user name, password, connect to, login, clear, cancel.

Authentication, application display either home page (or)admin page depending upon the actor entered.

Authentication, application display either home page (or)admin page depending upon the actor entered with the mentioned data base connections .

Go to Alternative flow Table 1 (Invalid user name) Go to Alternative flow Table 2 (invalid password) Go to Alternative flow Table 3 (invalid user name and password). Go to Alternative flow Table 4 (clear click). Go to Alternative flow Table 5 (cancel click).

31

Page 32: Complete guide to manual  testing@uma

Alternative flow Table 1:-

Action

Actors enters invalid user name valid password and click on login button.

Alternative flow Table 2:-

Actors enters in valid password valid user name and click on login button.

Alternative flow Table 3:-

Actors enters invalid user name invalid password and click on login button.

Alternative flow Table 4:-

Actors enter some information into any of the fields and click on clear button.

Alternative flow Table 1:-

Actors click on the cancel button.

32

Page 33: Complete guide to manual  testing@uma

Response

Authentication, Application displace, the following error message invalid user name please try again.

Authentication, Application displace, the following error message invalid password please try again.

Authentication, Application displace, the following error message invalid user name and invalid password please try again.

Application clears all the fields’ login screen and displaces the cursor in the user name fields.

Application clicks the login screen.

Guide line to be followed by test engineers soon after the receive the document :-

Identify the module to which the use case belong to?

Ans: Security module

Identify the functionality of the use case with respect total functionality ?

Ans : Authentication .

Identify the functionality point and prepare the functionality point document?

Ans: Where ever user perform some actions on the application that is called functional point.

Identify the input requirement to perform testing ?

Ans: Valid and invalid user name and password .

Identify the actors invalid ?

Ans: Normal user and admin user.

Identify the weather the use case linked with any other use case ?

33

Page 34: Complete guide to manual  testing@uma

Ans: Home pager and admin page use case.

Identify the precondition?

Ans: Login screen must be available

Identify the post condition ?

Ans: Either home page and admin user and error.

Understand main flow of the application ?

Understand the alternative of the application?

Understand the special requirement ?

Document the test cases for the main flow ?

Document the test cases for the alternative ?

Document the test cases of special requirement?

Prepare the traceability matrix (or) curser reference matrix?

Functional point :- The point where the user can perform some action in the application is know as functional point.

Testing process related document:-

Traceability matrix :-It is a document which contains table of linking information used for traceability back for the reference in any kind of confusion (or)questionable situation.

EX1:- (CTM) Complete Traceability Matrix.

UCID

3

6

TPID

4

99

TSID

8

86

TCID

10

36

DID

2

3

34

UCD

Use Case Document

FPD

Functional Point Document

TSD

Test Scenario Document

DTCD

Detail Test Case Document

DTD

Defect Point Document

Page 35: Complete guide to manual  testing@uma

20 30 45 55 4

EX2:- RTM ( Requirement Traceability Matrix).

TCID

1

2

3

4

5

REQUIREMENT ID

1.0

1.0

2.0

2.0

3.0

EX3:-DTM(Defect Traceability matrix).

Type of test case:- Test case are broadly divided in 3 types.

i) GUI test case

ii) Functional test case (two types)

a) +Ve test case

b) –Ve test case

iii) Non-Functional test cases

Guide line for the writing GUI test case:-

35

DTD

1

2

3

5

TCID

2.3

4.6

7.5

8.5

Page 36: Complete guide to manual  testing@uma

Any idea a test engineer with which he feels that we can test something with out doing any action will follow under GUI test case.

EX:-

Check for the available of all the object .

Check for the consistence for the object.

Check for the allayment of the object

If at all the customer requirement are given.

Check for the spelling and grammar.

Guide line for the writing the +Ve test case:-

Test engineer should have +Ve mind set.

He should consider the +Ve flow of the application

He must use only the valid input from the point of the functionality.

36

Page 37: Complete guide to manual  testing@uma

Requir

ement

Test

case Id

C001

C002

C003

C004

C005

Category

+Ve

GUI

GUI

GUI

Prere

quisite

-NA-

-NA-

-NA-

-NA-

Description\Test steps

Invoke the application.

Check for the availability of all the objective in login screen as for the LOT.

Check for the canonistic of all the object in the login screen.

Check for the spelling in the login screen.

Check for the initial

Expected value

Login screen should be display

All the object must be available login screen as for the LOT.

All the Objects must be consistent with each other.

All the spelling must be correct.

Initially the cursor must position in

Test data

LOT

Actual value

Login screen is display.

All the objects available as per the LOT

All the object are consisted with each other

All the spelling are correct.

Initially the cursor position in the connect to fields.

Login, clear, cancel button are to enable.

Clear button is 37

Page 38: Complete guide to manual  testing@uma

LOT(Login Object Table):-

VIT (Valid Input Table )

S.No

1

2

3

4

5

6

User Name

Suresh

Nag

Chiru

Ntr

Venky

Admin

Password

QTP

Amal

Sridevi

Balakrishna

Illu

Admin

Excepted Value

Admin page

Home page

Home page

Home page

Home page

Admin page

Actual Value

Admin page

Nag home page

Chiru home page

Ntr home page

Venky home page

Admin page

Result

Pass

Pass

Pass

Pass

Pass

Pass

38

S.No

1

2

3

4

5

6

Object Name

User name

Password

Connect to

Login

Clear

Cancel

Object Type

Text box

Text box

Combo box

Button

Button

Button

Page 39: Complete guide to manual  testing@uma

IVIT(Invalid Input Table)

S.No

1

2

3

4

5

6

User Name

Sure

Chirutha

Ntr

Nag

Jvreddy

Upendra

Password

Qtp

Sridevi

Balakr

Tab

JVR

Anu

Expected Page

Invalid user name plz tray again

Invalid user name plz tray again

Invalid password plz tray again

Invalid password plz tray again

Invalid password plz tray again

Invalid user name and password plz tray again

Actual Value

Admin page

Plz entry valid user name

Plz entry valid Password

Plz entry valid Password

Plz entry valid User name

Invalid password plz tray again

Result

Fail

pass

pass

Pass

Fail

Fail

Guide line for the writing the –Ve test case :-

Test engineer should have –Ve mind set.

He should consider the –Ve flow of the application

He must at list one invalid input in each set of data.

39

Page 40: Complete guide to manual  testing@uma

Test execution phase:- In this phase test engineer will do the following.

He will perform the action as it is described in the description Colum.

He will observer the actual behavior of the application.

He will document observer value under the actual value Colum.

Result analysis :- In this phase test engineer will compare the expected value with actual values and if both are matching they will decide result as pass other wise fail.

If at all the test if not executed then they will decide the result as blocked.

Bug tracking:- Bug tracking is processes which defect are isolate, identify, and managed.

Defect

1

2

Test case ID

C005

C006

Issue description

Initially the cursor is positioned in the connect to filed .

Initially login and clear button are enable instead of begin display.

Reproducible

Not applicable

Not applicable.

By

Jvr

Jvr

Date

Build

1

1

Version

2.3.6

2.3.6

Defect

Severity

Defect

Priority

Defect

Resolution

Fix

By

Fix date

Fix build

Data

Closer

40

Page 41: Complete guide to manual  testing@uma

3

4

C011

C014

Upon clicking on clear button all the field are clear but the cursor is nit position in the user name filed.

Upon entering user name, password as per DIVT and clicking on login button corresponding error message are not

>Enter some information any of fields.

>click on clear button.

>observe that all the fields are cleared but the cursor is not display in the user name.

>Enter user name DVIT.

>Enter the password DVIT.

>Click on login

Jvr

Jvr

1

1

2.3.6

2.3.6

41

Page 42: Complete guide to manual  testing@uma

5

6

C015

C016

display as per the DIVT.

Upon entering some information

Only into user name field (or) only into password filed login button is enabled misted of display.

button

>observe that corresponding error message is not display the DVIT.

>Enter some only into user name filed only into the password filed.

> observe that login button is enable instead of being display.

Jvr

Jvr

1

1

2.3.6

2.3.6

42

Page 43: Complete guide to manual  testing@uma

DIVIT(Defect Invalid Input Table)

S.No

1

2

3

User Name

Suresh

Uma

Uprndra

Password

QTP

Jvr

Anu

Expect

Plz enter valid user name

Plz enter valid user name &password

Plz enter valid user name &password

Actual Value

Plz enter valid user name

Plz enter valid user name

Plz enter valid user name

Defect ID:- The sequence of the defect no will be mentioned her in this section.

Test case ID:- The test case id based on the which defect is found will be mentioned her in this section.

Issue Description:- What exactly the defect is will be clearly described here in this section.

Reproducible stops:- The list of all the step which are followed by the test engineer in order to identify the feature will be mention here in this section.

Defection By:- The name of test engineer who has the defect are defect in this section.

Defection Date:- The date are on which will be mention her in this section.

Defection Build:- The build number in which the defect will be mention in this section.

Defection Version:- The version number in which the defect is found will be mention in this section.

Severity:- Severity describes the severity of the defect severity is classified in to 4 types.

Fatal (or) s1 (or) sev1 (or) 1.

Major (or) s2 (or) sev2 (or) 2.

Minor (or) s2 (or) sev3 (or) 3.

43

Page 44: Complete guide to manual  testing@uma

Suggestion (or) s4(or)sev4 (or)4.

Fatal:- It at all the related to the navigational block on available by of main functionality then such type of problems are treated as fatal defects.

EX:-

Major defect:- If at all the problem are related to the working the major functionality them such type of problem are treated a major defect.

EX:-

Minor Defect :-If at all the problem some related to the and feel of the application then such type of problem are treated as minor defect.

Ex:-

44

Page 1

Page2

Page3

Page4

Not opening

Val1

Val2

Result Add

Val 1

Val 2

Result

10

20

-10

add

Val 1

Val 2

Result

BAD

Page 45: Complete guide to manual  testing@uma

Suggestion :- If at all the problem are related to the value of the application then such type of problems are treated as suggestion.

Ex:- +Ve

Not user friendly message

User friendly

message

Priority :- Priority describes the sequence in which defect need to be rectify.

Priority is classified in to 4 types.

i) Critical (or) pri 1(or) p1

ii) High (or) pri 2(or) p2

iii) Medium (or)pri 3(or)p3

iv) Low (or) pri 4(or) p4

Generally the fatal defect will be given critical priority, major defect will be given, high priority, minor defect will be given medium priority, but dependence on the situation priority will be changed.

Low severity high priority case:-

When ever there is a customer visit all the look and feel defects will be given highest priority even though they are less serious.

High severity low priority case:-

When ever some part of model if development, reminding part is testing department, the test engineer will raise that part is fatal issue but the development will given low priority given it.

45

$

Invalid entry please tray again

Invalid entry please enter +Ve integer

Page 46: Complete guide to manual  testing@uma

Bug life cycle:-

No

Yes

Build 1 Build 2

Yes No

New:- When ever the defect is newly identified by the test engineer then the status is new.

Open:- When ever the developer the accepts then

Deferred:- When ever the developer the accepts the defect but wants some time for rectifying the defect the will set the status is deferred.

Fixed:- When ever the defect is rectified the developer will set the status as fixed.

Reopened and Close:- Once the next build released the test engineer will check whether defect is relay rectified (or)not if at all they feel relay rectified then they will set the status as closed other wise reopened.

46

Requirement

Developer

Application

Is defect really rectification

If defect

Stop the testing

Is it really a defect

Rectification

Open

ClosedRe opened

New

Hold

Rejected

As per design

Testing Fixed

YesNo

Page 47: Complete guide to manual  testing@uma

Hold:- When ever the developer is configured to accept or reject the defect they will set the status is hold.

When ever the defect is hold status as they will be a meeting on that defect (Triage meeting) and if at all consoled as a defect the developer will open it other wise the tester will closed it.

Rejected:-When ever the developer is conformed it is not a defect there he will status is rejected.

When ever the defect is rejected status the test engineer will once again check if at all he also feels it is a not a defect then he will set the status as closed other he will reopened.

As per design:- (it is a rare case only)

When ever the developer feels the tester has raised the defect with out having knowledge of latest requirement then he will check the status as As per design.

When ever the defect in as per design status the test engineer will go to the new requirement if at all he also feel it is as per design only then he will set the status is closed other wise reopened.

Reporting phase:-

Classical Bug reporting process :-

Test lead Develop lead

Tester Developers

Draw Back:-

Redundancy

Time consuming

No transparency

47

Page 48: Complete guide to manual  testing@uma

No security

Common repository oriented bug repotting process:-

Test lead Common repository Develop lead

Bug tracking tool oriented Bug Reporting process :-

Common repository

Bug tracking tools :- Bug tracking tool is soft ware application which can be accessed only by the etherized people which provides all the facility for bug tracking tools.

EX:- Bug zilla, issues tracking

Test closer Activity :- This a finely activity done in the process the test summary report which contain some following information .

No.of cycles execution.

Devotion in of each cycle.

48

BTT

Page 49: Complete guide to manual  testing@uma

No.of test case are execution in which cycle.

No.of test case are passed are failed .

No.of defect are found in each cycle and extra.

Way of testing:- there or two type.

i) Manual testing.ii) Automation testing.

Manual testing:- Manual testing is a process in which all the phase of software testing life cycle like test planning, test development, test execution, result analysis, bug tracking and report or accomplish successful manually with human efforts.

Draw back of manual testing:-

Time consuming.Less accuracy.Tiredness.Simulations action are all most impossible .Con’t repeat the same task again and again with some interest.More no.of human resources are required.

49

Page 50: Complete guide to manual  testing@uma

50


Recommended