Page | 1

AGILE TESTING
METHODOLOGY
ISM-6124 HOT TOPIC REPORT

Agile testing methodology

Page | 2

Natarajan Mohan
(U63758370)

Table of Contents
1. Introduction
1.1 Agile Approach
3
1.2 Traditional Approach
3
2. Traditional versus Agile methodology
4
3. Agile Testing Methodology
5
4. Restriction of Conventional QAs in Agile Environment
6
5. Agile Architecture
7
5.1 Iterations in Agile approach
10
5.1.1 Timeframe in agile approach
11
5.1.2 Candidate/Committed stories
12
5.1.3 Velocity of the story
12
5.1.4 Product Releases
12
6. Undoing the Traditional Approach
14
7. Verification and Validation model
14
8. Scripting test for Defects
15

Agile testing methodology

Page | 3

9. Different testing processes in agile testing

16
9.1 Exploratory testing
16
9.2 Scrum Process testing
17
9.3 Lean and Kanban testing
18
9.4 Extreme Programming (XP)
19
10. Agile in large scale projects
20
11. Pros and Cons Of Agile Method
21

1.Introduction
1.1 Agile Approach
In present situations, it is hard to give completely or exhaustively
determine the requirements at the beginning of task. Keeping in mind the
end goal to maintain in such environment the best arrangement is to
adjust an approach that adjusts and develops as the customer's apparent
and/or real needs change amid the advancement process.
As
programming improvement gets to be more perplexing, conventional
models can't proficiently adjust to the consistent and various changes
that happen. Light-footed methodology which is the agile methodology
became somewhat renowned in 1990's to conquer the issues confronted
by customary methodology. In Agile Process, the requirements are not
created and tried overall, yet conveyed and tried in little lumps. Spry
testing takes after the standards of lithe programming advancement,
which includes all the parts the useful coordinated group alongside
Agile testing methodology

Page | 4

master analyzers, to guarantee the business worth needed by the client is

conveyed at general interims. Not at all like Water Fall model, here end
clients, engineers and analyzers work in a synchronous way to accomplish
the target. Prerequisites which are the requirements by the client and
their usefulness are examined, then refined between the team by Product
Analysts at the start of each Testing Life Cycle. Agility in this methodology
is because of its esteem driven methodology, there is great of individual
abilities as opposed to on documentation. For such systems significant
measure of time is used on execution instead of arranging.

There are numerous methodologies for coordinated innovation, for

example, Extreme Programming, Lean and Kanban approach, SCRUM,
Dynamic Systems Development Method (DSDM). Exteme Programming is
a standout amongst the most broadly utilized methodologies.

1.2 Traditional approach

Conventional programming improvement technology utilize a
necessity configuration assemble form and are thought to be the
customary approach to create programming. Conventional technologies
are focused around an arrangement of steps that must be characterized
and reported in detail; this methodology does not help progressions of
requirements. They are obviously determined at the start of the task and
less change in the requirements is normal. The complete framework must
be known at begin. Environment is unsurprising and legitimate arranging
instruments can be utilized to discover better arrangements. Along these
lines it is likewise called as Plan driven methodology.
First and foremost of the product improvement utilizing customary
strategy, plan for the undertaking must be chosen. In the first stage,
complete framework is to be examined and outlined. Examiners or
analyzers foresee and make great programming structural planning. After
that, an expectation a model is to be made by utilizing different
specification languages like Argo UML. The genuine usage and coding is
then done by the designers, accordingly appearing the model. Each
methodology is reported and logged accurately. Obligations between
colleagues are imparted and conveyed through archives. Requirements
Agile testing methodology

Page | 5

must be detailed and marked by the clients and advancement group first
and foremost itself.
In short, environment that
advancement procedure is:

is

best

for

customary

programming

When all the prerequisites are generally characterized.

No change in the prerequisites pointed out or not very many

progressions to necessities at the later phase of programming
improvement.

We can precisely anticipate the essential errands and their spans.

Actually, environment where Plan Driven methodology would be hazard

are:

Continuous changes in the requirements.

Accommodating new necessities would be lumbering, as whole

process needs to be taken after once more.

In Software Industry, since it is hard to define all the necessities at

start.

2.Traditional versus Agile

methodology
The key contrasts in the agile and customary strategies are as takes
after:
In agile technique, advancement is incremental though in
conventional strategy it is successive. Programming is created in an
incremental style.
These little additions are based on past modules with extra features.
Each one release is altogether tried, which guarantees that all concerns
are tended to in the following emphasis. Accordingly an exhaustive unit
testing and integration testing is carried out at each one stage.
In this methodology individuals are more vital instead of methods or
tools. Client's engineers and the analyzers are all considered one faction.
Agile testing methodology

Page | 6

The principle point of such nearly teamed up collaboration is to diminish

the holes in the middle of analyzers and engineers so intensive testing is
conveyed without any mistaken assumptions.
Documentation is not given more need in coordinated technique as
contrasted with working programming model. As more eye to eye
correspondence is done correspondence is given more criticalness.
Customers are considered as the piece of development group so
there is no agreement arrangement yet client coordinated effort is
utilized. At any point if there are any inquiry and uncertainty in the mind
of the person who develops, the uncertainty is instantly elucidated from
the client.
Agile system blossoms with mayhem though Traditional
methodology blossoms with deliberate methodology. A larger number of
accentuates is given to change than orderly approach in Agile procedure.

3. Agile Testing Methodology

One most imperative phase of programming advancement cycle is
trying. Agile programming improvement concentrates on people and
collaboration, solid joint effort with clients, lastly with brief and continuous
deliverance of profitable program which works absolutely fine. The test
group and the development group are not formally divided. People who
design work in sets, with one individual creating the cases for testing and
the other working out the modules functionalities. The process starts
without any formal outline record. The particulars are as a rule in
manifestation of stories, with each cycle the stories are taken advances
and refined. No actual test arrangements are produced. The testing is
essentially focused around the assignments for peculiarity advancement.
The coding group gets prompt criticism from the group that tests. Hence
by permitting the test group to make the snappy start sample pieces
gives the coding group a point of view about genuine utilization of the
application piece. As should be obvious Agile testing needs a more liquid,
a persistent methodology with development and product administration is
needed.

Agile testing methodology

Page | 7

Core Qualities of Agile Tester

To have plans for testing and product deliverables at all times since at
any given point another specification may emerge .
Tester ought to have great information of the frameworks model
prior to testing it.
Write test events and keep a solution record.
Create automated test plans and also unit test cases.
Testing is made as straightforward as could be expected under the
circumstances.
An agile analyzer considers warnings as true lapses and it gives
helpful blunder messages.
Look into and study all test scenarios and record it.

4. Restriction of Conventional Quality

Assurance's in Agile Environment
An Agile cycle blossoms with progressions and confusions. Lightfooted requests that dynamic requirements ought to be invited even in
later phases of the software building activity. Test outline and other
quality assurance exercises utilize the specifications that are completed in
the development period. Furthermore in the event that they will change
the requirements and which will in the long run change these records then
it will question the customary method for doing testing.
Additionally, in customary -plan driven cycle, Quality Assurance is
typically the last action before a settled release date. On the off chance
that the same is followed in Agile also numerous arranged QA exercises
may get crushed from the calendar, bargaining item quality. Delivering a
Agile testing methodology

Page | 8

functioning piece of program to clients as soon as possible and

consistently with a fast discharging cycle is an definitive need of the agile
cycle. It is a challenge for testing procedure, on the grounds that, that
there is a risk factor that it will put settled due dates for testing exercises
when the release phases are quick and that does not permit expanding
the time taken for testing if a larger number of imperfections are found
than evaluated. They can't send them once again to settle, in light of the
fact that the time to be taken for testing is planned well in advance and
they have to deliver an item on a predefined date.
The eye-eye discussion of designer and client additionally makes a few
difficulties for testing exercises. Since these exercises depends on the
archiving of the results, and this archives likewise have some data about
the test outcomes. In the event that they have a nearby coordinated
effort then that data will be in the minds of the clients and the designers.
In this way, it can make a few difficulties for testing in this technique.
They say that, the main measure of advancement is the functioning
program. Along these lines, it implies that testing can't be an entire
independent stage at the end of the iteration in light of the fact that it
should give comes about at the earliest opportunity, that the created item
is a working program or not.
One more check is the guideline of straightforwardness. This implies,
the measure of task which is not done ought to be expanded. Along these
lines, this standard obviously can wipe out the testing exercises from the
procedure, on the grounds that the testing exercises don't specifically
increase the value of the code .
In agile technique, testing is carried out by both designers and clients,
unit and integration testing is carried out by engineers while clients do
the acceptance testing. At the same time a decent programming testing
obliges proficient abilities, on the grounds that it is an inventive and
cannily difficult undertaking. An expert analyzer is obliged to do this
expert task, so the tasks can be performed successfully and proficiently.

Agile testing methodology

Page | 9

5.Agile Architecture
The Agile System Architecture of the Agile process beginning from
potential undertakings to the final phase is as shown:

The structural planning tells about the starting emphasis and the
useful cycles included in the Software Development process of agile
Agile testing methodology

P a g e | 10

technology. The starting cycles is for prerequisites building. The Product

group investigate the client criticism, proposals, in light of which they
concoct a cluster of requirements. Amid the starting cycle stage
conceptualizing happens and these necessities are examined, changed,
calibrated. These refined specifications are transferred to the helpful
cycles as introductory bunch of prerequisites. Out of these refined
specifications, a rundown of prerequisites that are more in priority,
isrecognized and selected for the first cycle in the productive emphasis
stage. The agile testing procedure architecture is depicted below:

Agile testing methodology

P a g e | 11

The graph portrays the life cycle of the testing phase of agile
approach. At first the specifications flow in as stories, A reliance upon
deformities or occurrences is made and the release is changed. The
quality assurance groups who are responsible for planning with tests
are then allocated the stories.

Agile testing methodology

P a g e | 12

5.1 lterations in agile approach

The first Iteration involves
the
requirements be analyzed by
development and testing groups. Requirement testing is carried out. In
the event that there are any disparities in the necessities, it is recognized
in this stage. At that point they are adjusted appropriately and the
procedure takes after. Once the specifications are properly defined, the
group that is involved with building the code begins to code and the Test
traceability matrix (TTM) and Test scenario matrix (TSM) is planned by the
group that is supposed to test. Test traceability matrix is similar to test
conditions which gives the high level test situation while Test scenario
matrix is a genuine experiment that says what has to be done to test a
specific situation.It consists depiction of the test, steps included, the need
of the experiment, first pass or relapse, internationalization obliged or
not, analyzer name. regression test cases are those test cases that speak
to the fundamental usefulness, so as to recognize and utilize them for the
prospective releases. Internationalization alludes to testing the dialect, to
decide whether a specific test must be internationalized or not. The use of
above experiments is that its utilized by the language testing group
which is local, they check in diverse languages, in case that it is stamped
as YES.
A reasonable graph indicating different iterations in agile software
testing approach is depicted under. The arrangement for lteration
planning and release is shown below where in the release is made and
logged. Also it demonstrates different cycles that are included in a release
and how they are blended in order to be released.

Agile testing methodology

P a g e | 13

5.1.1 Timeframe of an agile approach

Most Iterations in the agile methodology can compass from a week to a
month. The usual time allotment for cycle is a couple of weeks. In the
first couple of days of the week one, the specifications are deeply studied
and analyzed and irregularities in them are dealt with. Whatever time is
remaining of the week is used by the the groups independently where
group that is responsible to develop codes the requirements and the
group that is supposed to test begins setting up the Test
TraceabilityMatrix and Test ScenarioMatrix. These Tsms are transferred to
any testing software tool that is utilized by any association. When the
coding part is carried out, which is usually at the end of the week one, if
not then its in the beginning of the second week, group that is concerned
with the testing part is informed about the deployment of the code. The
testing group then begin their job and distinguish critical imperfections.
The deformities identified are followed in the Issuetracker that is put in a
normal storehouse like Sharepoint where everyone could get to the
tracker. The issues are then checked by the Product and development
group. On the off chance that an issue is recognized as a legitimate one,
the group that develops the software does code fixes to redress it. When
the issue is settled by the group that does the development part, testing
group is advised by remarks in the tracker.

Agile testing methodology

P a g e | 14

Testing group retests the issue, on the off chance that it is settled
imprints the issue as altered, in the event it is non altered, checks it as
not altered and then the procedure takes after. This takes place some
time in the middle of week two. Towards conclusion of week two,
everyone who were included, get together over phone or in person and
talk about the process which is the iteration that has been happening for
two weeks and a showcase is carried out . The requirement and
improvement group extension is indicated by the development group and
in like manner testing group demonstrates the testing degree. The issues
which were not fixed are recorded in as defects in qualitycenter and
doled out to the group that develops the product. When, everyone are
fulfilled by the last form of the code, baselining is done and is made
ready to release. This above case is only an illustration of the a two week
long agile process , the quantity of the time period is completely reliant
on kind of requirements, task, and clients or stakeholders. On the off
chance that a requirement has such a variety of issues which arent
addressed and the extension is unclear, then that specific requirement
goes unacknowledged in the showcase call for that iteration. All the
coding activities accomplished for that specific requirement are returned
back and conceded to the approaching cycles else in the most
detrimental possibility next release.

5.1.2Candidate/ Committed stories

Stories are formed as follows :Amid the begining of cycle, the
specifications that are found out are broken down into more modest
nuclear pieces. Every story is mapped to a specification and it has
uniqueid which is the number of the story. The story number and the
story heading help in identifying the stories. They are prioritized in the
introductory phases of cycle as discussed before. Taking into account the
need and speed point (examined in following area), these stories are
stamped as a submitted and candidate stories for a iteration. The idea
driving it as takes after. A submitted story fundamentally is the high
needed one, at any expense it has to be deployed, tested and also
baselined. When all the submitted stories are carried out, if there is
sufficient time and labor, these candidate stories are coded and tried.
Agile testing methodology

P a g e | 15

These stories have generally low need when contrasted with that of
candidate ones. Regularly, candidate and committed is specified after the
title of the story by "cand", "cmtd".

5.1.3 Velocity of the story

This is a numeric value that is designated to story focused around
its intricacy and imperativeness in the cycle. This numeric value is
exceptionally valuable from multiple points of view. This demonstrations
as a primary criteria in choosing what number of stories ought to go in a
cycle. Generally, every cycle has a total velocity point, which means that
the total velocity points of all the stories in the particular cycle must
always sum upto to the total value which is fixed for the cycle. In the
event that the size of the undertaking is huge and timeline is lenghty,
this point is then kept high for the cycle. As soon as a cycle is finished, an
alternate emphasis takes after and set of cycles help a discharge.

5.1.4 Product Releases

This is only migrating the composed code into generation, which
can be utilized by the end clients a while later. In agile approach, releases
generally include a cluster of cycles. The quantity of iterations going into
a release is simply focused around the unpredictability of the
functionalities implicit every cycle and the business necessities.
Legitimate arranging of discharges are carried out. Gatherings are
directed at first to settle on a prospective date of deliverance, number of
designers and analyzers that would be taking a shot at the undertaking,
plan estimation and so on. These gatherings normally keep going for
almost an entire day and the members encompasses thestakeholders,
venture supervisors, designers and QualityAnalysts. The viewpoints chose
in this meeting are not so much the exact ones, it could vary over a time.
The time period of release could be somewhere in the range of couple of
months to a year.
The outline in the following page obviously delineates the agile
approach's iterations. Every one of the free stream in the above outline is
Agile testing methodology

P a g e | 16

a cycle. The iterations that are gathered as a group are situated for the
release. The actual numeric value of the cycles that is going in for a
release is chosen by the group that is responsible for coding ,stakeholders
or clients, and Quality Analyst group.

6.Undoing the Traditional approach

Keeping in mind the end goal which is to achieve most agility, it
obliges a great deal of unlearning to be carried out on the conventional/V
model methodologies. Individuals who have worked longer in the
conventional methodology don't generally have incredible enthusiasm on
Agile procedure. They would prefer not to leave the process that they
have taken after for such a large number of years to be supplanted by
another methodology. The purpose for it is, Agile courses of action are
very unpredictable and they have a tendency to change anytime amid
Agile testing methodology

P a g e | 17

software development life cycle for a particular task. In conventional

approach, there is a different taught group for everything. They have a
total rundown which demonstrates the calendars for each group over a
time with different perspectives like what has to be carried out and when
does it need to be carried out.
Frequently huge associations outsource testing. If there should arise
an occurrence of agile Methodology, all the groups are joined to one
another. Designers and Quality Analysts cooperate to attain great
programming. Additionally, individuals have a wrong idea that testcase
automation is not that required in testing. This is not genuine; automation
of testing has vital impact in Software Testing. Amid agile procedure,
there are three groups working as one, an group that codes, a manual
testing group and automation testing group. The Development group
examines the necessities and begins coding in the initial couple of days of
the cycle. Testing groups additionally break down the prerequisites and
runs a prerequisite testing. The manual testing group begins composing
test traceabilitymatrix and test scenariomatrix, when everyone are happy
with the specifications. In this period, the group that performs the
automation assimilates the stories down in the iterations and chooses
desirable ones for performing the automation. This isn't possible to all of
the accessible stories since it is expensive. This is carried out on stories
whose functionalities are tedious, to produce information to perform
manual testing, to check the applications consistency, and so on. It could
be utilized successfully amid relapse testing times.

7.Verification
model(V-model)

and

Validation

V-Model speaks to verification and validation Model. This model is

utilized in checking and acceptance of the product against components like
client necessities, association's strategies, and so on. Verification is only
checking whether the methodology included in building the last item are
according to association's principles and regulations and complies with the
client's strategies as well. Validation is about assessing the item. In short, the
previous speaks to the procedure included in building the item and the later

Agile testing methodology

P a g e | 18

discusses

the

item.

The above V-Model speaks to the courses of action included in

theagile and conventional approach. The principle contrast among both of
them is in the approval stage where in conventional methodology,
systemintegration testing is carried out, continuous integration and
refactoring is carried out in agile procedure. Overall both the methods
have to some degree comparable kind of V-model.

8. Scripting the tests for defects

The customary methods are those where the testcases are
composed, testing is carried out for each noteworthy deviation in the
conduct of the product from the client's needs; deformity constantly
logged. The stages which the defect is made to go through are New,
Open, Incoding, fixed, retest, closed, rejected and deferred . When the
flaws are made fine /Retest (doled out to QualityAnalyst), QualityAnalyst
simply does the retesting work. Contingent upon the Retestings result,
they close/revive the imperfection. Appropriately the testcases are either
passed or fizzled. There are no fresh tests composed for the flaws in
conventional method since this would mean extra labor and plan used in
documentation, regard and the testcases. In short this would mean a little
Software development life Cycle. Once in a while, they do change controls
in customary methodology for functionalities that are basic.

Agile testing methodology

P a g e | 19

In agile method, the methodology is entirely unexpected in light of

its capability to oblige changes anytime in Software development life
Cycle. Test traceability and scenario Matrices are made amid the first
week of iteration. Notwithstanding that, defects that are basic or have
high need are stamped and testcases are, no doubt made for them. The
testcases are then run when the flaw gets fixed which gives a more
prominent chance to check the conduct of different functionalities after
fix. Thus, there is a fat chance to recognize the defects that are infused
because of the fix; overall these infused deformities must be recognized
in the relapse testing which is the situation in conventional method. This
is one of the explanations for high number of imperfections in
conventional methodology amid regression stage. The testcases that are
composed for defects likewise discover it put automation proving ground
if conceivable.

Testing in agile method can likewise be carried out on non-functional

perspectives, for example- Execution, Burden, Stress and so forth. Test
traceablity matrix and Test scenariomatrix can be composed to test these
functionalities and incorporated to the product that is to release. Each
lteration need not bother with a different story to inspect these nonutilitarian perspectives, a story for the Release would do. Moreover, the
same functionalities in future discharges can be tested by these scripts.
Testing process in agile method focuses all the more on center functional
problems when contrasted with restorative problems. At the termination
of every cycle, engineers attempt their greatest to alter all the
functionally useful issues brought up in the issuetracker and the
corrective issues are conceded to following cycle, however it is made sure
that all the issues are tended to before the release. On the off chance that
they are not able to address any basic issue at the end of an cycle,
imperfections are raised.

9.Different Testing Process in Agile

9.1 Exploratory testing
Agile testing methodology

P a g e | 20

Exploratory testing is centered about the risks involved, and is a

decent supplement to the value centered affirmation tests utilized as a
part of automated unit tests and acceptance testing. The procedure being
very similar to the agile strategy excessively does not give more
significance to the documentation, however throws greater essentialness
to learning. Both agile methodologies and exploratory testing permit
connection to pulverize
choice making, and both empower quick,
maintainable and non-calamitous alters of directions. Exploratory testing
and agile processes, both are pictured as restless, or inventive, both
quality creation of an entirely new process or adjustment of process that
is already present over servile after ideal procedure, and both need
discipline and dependance on expertise of a specialist. Quick criticism in
each one empowers lterative methodologies readiness permitting
lterations crosswise over code plan, Exploratory testing permitting cycles
crosswise over test outline. Both can conceal for a broken task yet not
one or the other is great fix. Exploratory testing and diagnostic testing are
essential skills to bring to a light-footed group, enhancing the nature of
bugs and their depictions.

9.2 Scrum Process Testing

9.2.1 Parts
The testing process in scrum is characterized by numerous roles. All
the roles must be fulfilled by designers amid this process. The roles are
integral and are given by the development engineers andtesters are as
follows: "scrum master," are the project manager; "product owner,"
stakeholders who are supposed to
be utilizing the product, also are
additionally called customers; and "Team," who are responsible with
performing the testing, analysis and report the results. Different roles
incorporate Clients and directors from outside.

9.2.2Launching the process

The procedure starts with a sprint. A sprint is typically a period of
time which is ideally two /four where the engineers use the product
backlog and use it for testing the product. It has all the specifications
pointed out by the clients / customers. It also comprises of a specimen of
Agile testing methodology

P a g e | 21

product that has to be broke down in order to be agreeable with client's

necessities. The product backlog is then set by the product owner and
sent to the group for testing to be performed.

9.2.3Testing the software

The group responsible for testing of the product, tests the product
amid each one sprint. The group is not permitted to change the client
prerequisites amid the sprint backlogs. For a specific sprint the necessity
continue as before. The group and productowner have every day
gatherings amid the sprint, daily meetings and webex are, take place with
no doubt. These gatherings are managed by the Scrum expert. Sprint
arranging sessions (where things are separated among the group) and
sprint review session (where practices are looked into based on which
plans are recommended) are the two structures which these meetings can
take. Engineers likewise also consider the new client solicitations amid
these gatherings that are handled in following sprint cycle.

9.3Lean and kanban testing processes

An lterative dexterous approach initially created by Tom and Mary is
the Lean software development. The Lean Enterprise development is
responsible for bot lean and kanban software development standards and
practices. Lean software development is on productivity and delivering
the value to client i.e the components that convey that value. The
primary standards include: Waste elimination, improve your Learning ,
decision ought to be made as later as could be allowed ,fast conveyance
of module, allowing integrity to be built , group motivation , able to see
the complete picture
Both the processes :Lean and Kanban selects just the really
important features for a framework and thus takes out waste through
such practices , importance ought to be given to those that are chosen,
and convey them in little clusters. It is fixated not only on the rate but
also productivity of advancement lifecycle, and depends on brisk and legit
criticism in the middle of developers and clients. The technique utilizes
the thought of programming being "produced" by means of client appeal.
Agile testing methodology

P a g e | 22

It centers choice making power and capacity on people and little groups,
this is supposed to be speedier and more proficient than hierarchial
stream of control as demonstrated by research, lean is more concentrated
on the proficiency of the utilization of group assets, attempting to
guarantee that everybody is beneficial however much of the time as could
be expected. It focuses on simultaneous work with less group conditions.
It additionally suggests that unit testing is composed in the meantime
when the code is created.
Kanban is a light-footed which is the agile approach which
concentrates on delivery of products continually and not over-burdening
the improvement group. Like whatever other methodology, it is a
procedure which intends to assist groups cooperate all the more
adequately.

Three fundamental standards of this method is:

Picturizing the current workflow(work process)

To have reconnoiter the measure of work in advancement (WIP)

Upgrading and modifying the current workflow

Kanban empowers consistent cooperation and creates

association with learning that is progressive and enhancing.

dynamic

9.4Extreme programming [xp]

Extreme programming was initially explained by Kent beck, This
methodology is a standout amongst the most developed, prominent and
disputable agile techniques.It is a trained plan driven methodology to
deliver excellent programming quickly and ceaselessly. For XP, the
inclusion of clients is high, nonstop volatile nature of the necessities and
ceaseless criticism is one among the primary feature of XP. It advertises
testing persistently, constant arranging, and in proximal cooperation to

Agile testing methodology

P a g e | 23

convey working programming at extremely at frequent interims, normally

every two or three weeks.
The first XP is detailed focused around four exceptionally
straightforward qualities effortlessness, correspondence, criticism, and
fearlessness and with backing of twelve practices:

Carefull Planning
Pair programming
A small Release
User acceptance testing
Test driven development i.e outlining experiments from the starting
Refactoring
Simple design
Doing Continuous lntegration and relapse testing
Ownership of the code
Maintaining legitimate coding models
Metaphor
Evolution at sustainable pace

Here, "Client" is made to work with the

group involved in
development for characterizing and prioritizing micro smaller units of
usefulness alluded as "Client Stories". The advancement group takes care
of gauging, plannning, and conveying the most noteworthy need client
stories as a working deliverable on every lteration. With a specific end
goal to amplify gainfulness, these practices give a profound, system to
guide a group and guarantee program which is high in terms of quality.

10.Large-Scale development
agile techniques

using

In agile activities everybody composes tests and does testing.

Testing is thought to be every colleague's movement. Testing is
viewed as a key measure of both group and individual benefit
Testers worked better as a team with the advancement group.
Working freely will prompted numerous minor straying from
requirements, however very less genuine defects additionally it
Agile testing methodology

P a g e | 24

diminishes the quantity of false surrender reports. Likewise having

everybody testing, clearly wipes out the single analyzer bottleneck .
Developers are included in composing tests which boosts their
mindfulness. Consideration of designer will prompt less absconds,
better code and outline for testability.
Measuement of progress of the ventures is possible. Item estimate
metric: Number of regression test steps run for every emphasis is
ascertained. Any work that is untested is considered to be no work.
All the deformities that are known are corrected in regression
tests.
Agile imperfection administration is straightforward; anybody
could open a deformity and close a deformity in the wake of altering
and running tests. Any individual who discovers a deformity will
allots it to somebody for altering. Indeed engineers could reassign
surrenders without anyone else present. This diminishes overhead
from supervisors.
Fix each deformity at the earliest opportunity. Imperfections oblige
less time to alter. Taking a shot at clean and stable code makes
improvement speedier. It evades overhead of prioritizing and
arranging deformity alters and keeps away from disagreeable client
arrangements to choose which desert to settle.
For extensive scale association there is no understanding of
deformity seriousness for Agile Testing. The main thought is whether
to settle it or not. On the off chance that yes, the deformity are
settled when the expense to alter is least expensive else deformities
are not opened.
Agile advancement totally reclassifies quality certification work
from formal parts to everyday exercises.

11.Pros and Cons of Agile

methodology
11.1 Pros
Agile testing methodology

P a g e | 25

Theres a fast delivery of the clients requirement as stories in

every lterations.
Also a steady correspondence among different groups which
eventually winds up in the creation of a quality item is also done.
Each prerequisite in a cycle is broke down by distinctive set of
groups that are four in number(Product analysts(Stakeholder),
development, QualityAnalyst, Automation) to comprehend its
achievability.
The agile team is likewise extremely adaptable in obliging
progressions. Any little modifiction in prerequisite amid any of the
stages in SDLC can be effectively suited and oversaw. This quality of
agile methodology of adjusting effectively makes it to stand out.
The client gets a chance to see the last item, how it is incorporated
and coordinated with the current framework at each stage. On the
off chance that the product developed is not to his/her desire, it can
be upgraded to match their desire.

11.2Cons
Lack of documentaton is a major drawback in agile methodology
which may prompt loss of numerous important data and forming.
In case, where the purpose of contact at client side is unclear with
the necessities, the terminal product may be a faulty one.
This method obliges a ton of co-appointment between the
colleagues. On the off chance that a colleague is not performing
great, it has a noteworthy impact on the finished item.
It is quite difficult to persuade groups to move to Agile procedure on
the grounds that they have into conventional methodology for quite
a period of time and all of a sudden they don't confide in lesser
traditional methodology.

References
http://www.ambysoft.com/essays/agileTesting.html
http://www.informit.com/articles/article.aspx?p=405513

Agile testing methodology

P a g e | 26
http://www.indicthreads.com/1324/agile-teams-miss-out-by-having-a-narrow-focuson-testing/
http://en.wikipedia.org/wiki/Agile_testing
http://pathfindersoftware.com/wp-content/uploads/Agile-Testing-Flow2.png
http://agiletesting.com.au/
http://msdn.microsoft.com/en-us/library/ff649520.aspx
http://agile-only.com/master-thesis/software-dm/traditional-s-dm
http://www.rbcs-us.com/images/documents/agile%20testing%20challenges.pdf
http://www.quality-assurance-testing.com/category/agile
http://en.wikipedia.org/wiki/Test-driven_development
http://testobsessed.com/wp-content/uploads/2011/04/AgileTestingOverview.pdf
http://www.scrumalliance.org/articles/392-agile-testing-key-points-for-unlearning
http://www.gopromanagement.com/Proactive
%20Testing_vs_Conventional_Reactive_Software_Testing.pdf

Agile testing methodology