Proceedings of the SMART-2016, IEEE Conference ID: 39669

5th International Conference on System Modeling & Advancement in Research Trends , 25th _27'h November, 2016
College of Computing Sciences & Information Technology, Teerthanker Mahaveer University, Moradabad , India

Agile Approach for Software Testing Process

Rijwan Khan I, Akhilesh Kumar Srivastava2 and Dilkeshwar Pandey 3
1Departmentof Computer Engineering, ABES Institute of Technology, NH-24, Vjjay Nagar, Ghaziabad, India
2 Department of Computer Engineering, ABES Engineering College, NH-24, Vjjay Nagar, Ghaziabad, India
3Department of Computer Engineering, ABES Institute of Technology, NH-24, Vjjay Nagar, Ghaziabad, India
E-mail: lrjjwankhan786@gmail. [email protected]@abesit.in

Abstract-As per the finding of Agile development, • In most of the Software industries, development
Testing is recognized not to be a separate phase, but an team refers incremental approach rather than
integral part of Software Development with the Coding. sequential one. Incremental and rapid cycle' s
"Whole-team" approach is being used by Agile team to
methods are used in agile development. It leads
"baking quality in" to the Software Product. Agile team
containing the Testers, who lend their expertise in eliciting
slowly towards the incremental method but also
examples of desired behavior from customers. They release generating on previous functionality. The
collaborate with the development team that guide Coding, to thorough testing in this process ensures all issues
turn those into executable specifications. Testing and Coding are addressed in next iterations.
is being performed incrementally and iteratively, until it • More stress is laid on people and interactions
provides enough value to release to production each feature instead of processes and tools. Testers,
building up is made. It covers different types of testing. It developers and customers consistently coordinate
quadrants provide a helpful taxonomy which help teams in with each other. This coordination describes
identifying and planning the testing need [3,4).
awareness of requirements to the tester for the
Keywords: Agile Testing, Software Engineering, Software
Testing, Software Development features being developed during a specific
iterations and can isolate the discrepancy
I. INTRODUCTION between system and its requirements.
The methodologies of software development life • A live Software is preferable inspire of the
cycle follow sequential models or are iterative in nature detailed documentations. Agile methodology
just like waterfall model. With the simple testing, software works on the fact of point to point i.e. face to face
development is most complex task, sequential models communication and collaborations with teams
cannot efficiently adapt the changes those occurs during working in pairs. Relying on the fact of extensive
communication, with customers along with team
development. This disadvantage has been removed with
members, the project does not require
the agile testing process which is based on the iterative
comprehensive requirement document.
methodologies and overcome the disadvantages of
sequential models. • Customer collaboration is in more consideration
in comparison to contract negotiation. Customer
involvement is an important part in Agile
process. The developers immediately seek
suggestion on requirements from the customer
for better clarification.
• Responding to change is of more consideration in
comparison to extensive planning. Extreme
programming lays emphasis on changing the plan
to accommodate any changes in assumptions
instead offorcefully following the original plan.

11. B AC KGRO UND

Software testing forms an important part of process
which helps improving quality of the product. Companies
Fig. I: Agile Process are contributing much of their investment in testing the
The main difference between these two methods, software. All Software companies are spending a huge
Agile software testing and traditional testing amount of money and their time on testing activities.
methodologies are as follows: Report for the testing process shows that more than 50%

Copyright © SMART-2016 ISBN: 978-1-5090-3543-4 3

Authorized licensed use limited to: University of West London. Downloaded on March 18,2024 at 12:38:41 UTC from IEEE Xplore. Restrictions apply.
5th International Conference on System Modeling & Advancement in Research Trends, 25th _27'h November, 2016
College of Computing Sciences & Information Technology, Teerthanker Mahaveer University, Moradabad , India

of the total cost of project/ application is devoted to

software testing.
Agile method which is one of the highly practiced
methodologies, consider in all the industries nowadays.
Scott W. Amber, conducted a survey and according to
their survey more than 69% industries are using agile
projects and he fmd that the success rate of Agile is 82%
for co-located teams and 72% for non-co-Iocated teams [1 ,
2, 5].
Agile is an approach to develop the high quality
Software and fulfill all the customer requirements with a
self-organized team for delivering cost effective Software
with a time frame also meets users all requirements. The
software developed with Agile techniques delivered very
quickly to the customer and as it is an iterative process
checks all the errors and defects with the challenges in the Fig. 2: Software Testing Life Cycl e
requirements. With the customer development team makes IV. AGILE METHODOLOGY
some changes and float the Software to the customer, he
suggested the improvement and incorporated in the Agile Testing is one kind of the Software testing
Software/program. A number of books, studies and papers practice used more than waterfall model. Agile testing
pertaining to this area have been published and we intend follows the statutes of the Agile manifesto, also treating
to refer to these in order to guide us with the research Software developer as a new comer to solve the problems
work. properly.
Agile testing is that which involves testing from the
Ill. SOFTWARE TESTING PROCESS customer' s side as early stage. Early stage testing is also
called unit testing.
Software Testing is a process for verification and Agile works on incremental method. So in
validation of the software, it is a process to guaranty incremental method the developing Software have to be
execution of error free and bugs free tested at each stage means after some development it has
Software/applications. been tested with the customers and this type of testing is
An Agile model designed to meet all business and also done using automated acceptance testing. Automated
technical requirement. This model can be implemented acceptance testing minimizes the manual work. In agile
with same characteristics, when implemented will work as process the manual testing for whole Software will not
expected. work. Doing the manual testing leads towards the buggy
Software Testing identifies defects, errors and flaws software in agile testing, so it is not possible to test the
in the program/Software. These defects, errors and flaws entire built Software manually.

I.
must be fixed during the software testing process. When
some changes are applied in the program then again these Clitnllfilibllitr
Software should be tested again and again until all the
defects are found and fixed in the Program/Software. Test
activities are controlled and reported on testing process
"-Ill
and the status of the software under test.
During test planning important defects are carried out
Agile
by reviewing the requirements and design documents. The lifecycle
testing team removes these defects but cannot improve the R!lease
lO Marke1
quality of the software. All the improvements should be
documented during the coding phase in the Software
development such that before testing all the improvements
are incorporated in the system. Software Architecture and
designers design a good model if they receive all the Fig. 3: A gile Life Cycle
improvements in a defmed time frame. Testing before Agile Modeling (AM) is a very effective modeling
coding can improve the design of the Software/ and documentation for practice-based methodology for
Application. software based system. Agile Modeling (AM) can be

4 Copyright © SMART-2016 ISBN: 978-1-5090-3543-4

Authorized licensed use limited to: University of West London. Downloaded on March 18,2024 at 12:38:41 UTC from IEEE Xplore. Restrictions apply.
 Agile Approach for Software Testing Process

applied on software projects in an effective and at a very • Environment. For developing project/program all
high level. It consists of principles, values and practices the guidelines should available with all the
for modeling Software. required tools, Hardware and Software.
Agile methodology, a conceptual framework for
Software development, face to face interaction with the VI. FEATURES AND COMPARISON OF AGILE
METHODOLOGIES
customer promotes iterative development method
throughout the project life cycle. TABLE I: FEATURES AND COM PARIS ION OF AGILE
There is no need of written documents in Agile Method Key Points Special Features Identified
method as it focuses on one-to-one communication over Name Weakness
written documentations. Agile team can make very little ASD Adaptive in From web of Rather than the
nature, iterative interconnected software practice,
written documents as compare to waterfall or V model. development, individuals an ASD is conceptual.
Agile methods emphasizes on working Software as the collaboration. emergent order is
primary measure of progress. Often agile teams work in a created. Organiztions
single open office with developer team and customers. are adaptive in nature.
DSDM All web It is first kind ofturly When DSDM is
The Agile team includes testers, Software architectures, appl ications are agile software available only some
software developers, testers and managers (Iow and high controls by RAD development method, specified member of
level). The result is in criticism of Agile methods for being and very much for developing it use the the development
undisciplined. usefull for prototyping model, team have allow to
DSDM. user has different roles access white papers
like advisor, and deal ing with
V. AGILE UNIFIED PROCESS
ambassador and acutual method .
Scott Amber developed a simplified version of IBM visionary.
XP Team is very Redesign and While individual
Rational Unified Process (RUP) called Agile Unified small in size, can refactoring the whole practices are suitable
Process (AUP). Agile approach gives a simple, very easy build daily, system to improve its for various
and good understanding method for developing the Customer driven perfomance and its situations, complete
Software/applications which are true with RUP. Agile development reponsiveness. view & management
practices are given
Unified Process (AUP) include test driven development secondary attention
(TDD), Agile Change Management (ACM), Agile SCRUM Self-organizing Enforce a paradigm Scrum details is
Modeling and database refactoring for enhancing development, shift from "defined and specific how to
productivity. small and repeatable" to the " new manage the 30-days
Independent team product development release cycle, the
Unlike the RUP, the AUP has only seven disciplines. with 30-days view of Scrum" acceptance and
Model. To understand the process of any organization release cycle. Integration tests are
and development team addresses the problem domain not detailed
found during study of business process. Development FDD Ooject oriented Model is design with Focus on design and
components, it is simplicity and system implementation
team also proposes a solution for solving the problem. So
totalS step implemented by only. supporting
the proposed solution takes a form of model for the process. features, object approaches are
problem. modelling. required as well.
• Implementation. This model transforms into GSD Graphical system A HLL, real-time The design works as
design relies on processor, FPGA logic, a super-set of
executable code by the development team and open modular I/O and any electronic system-
perform a very basic testing called unit testing. connectivity . intellectual property level (ESL) design
• Test. A Check that system works as per the required .
design is called validation and verified that all the AUP Using agile Applies agi le AUP is not usefull
techniques, it is techniques along with for all your needs to
requirements are met and perform an objective very easy to test-driven be tailoring.
evaluation to ensure quality of the Software/ understand and development (TDD),
program. developing the Agi le Modeling, agile
• Deployment. To check that it is ready to deliver business model. change management,
and database
and make it available to the end users. refactoring that
• Configuration Management. Project artifacts are improves productivity.
managed and accessed. Artifact versions are Kanban It is a visual Use models and Every member of
tracked over time and also controlled and process scientific methods for the organization, be
management improving it individual
managed by the team. system that collaboratively. evolve employee or
• Prqject Management. Directs all the activities of iterates what is to experimentally. manager shou Id be
the projects and also managing risks, directing be prod uced, motivated for the
when to be Leadership.
people, also coordinating with the people outside
produced, and
the project to ensure that the project will be how much to be
developed in time and within the budget. produced.

Copyright © SMART-2016 ISBN: 978-1-5090-3543-4 5

Authorized licensed use limited to: University of West London. Downloaded on March 18,2024 at 12:38:41 UTC from IEEE Xplore. Restrictions apply.
5th International Conference on System Modeling & Advancement in Research Trends, 25th _27'h November, 2016
College of Computing Sciences & Information Technology, Teerthanker Mahaveer University, Moradabad , India

VII. AGILE TESTING METHODOLOGY IN INDUSTRIES and disadvantages, it depends upon the organization which
model to choose.
In Industries, Agile testing is getting used frequently
If customer changes its requirements frequently and is
nowadays as it involves customer collaborations and
asked to deliver the Software on short period of time with
short week cycles. It makes the project speed fast due to
skilled resources then it is beneficial to choose Agile
all these features. It is best methodology as it removes the
based testing model while in other hand Waterfall model
disadvantages of Waterfall Model and V-Model.
can used when requirement is clear, projects are large and
It is best model for project where requirements are
developers have sufficient time. If projects are very large,
changing and project scope is not clear. Due to the
requirements change and proper validation is required in
frequent involvement of customer at every step also
each phase then in that case tester uses "V-Model" .
increases confidence and satisfaction of customer in end
But, we can say due to tight timelines and customer
product and decreases chances of defect in future. As
high expectations, now a day' s Agile Testing
client interaction is involved in each and every cycle so
Methodology is best methodology which industry should
end product getting delivered after every cycle is
adopt for delivering the projects.
according to the requirements.
Agile testing also decreases cost of project as working REFERENC ES
product is getting delivered after each cycle in increments
[ I] K. Beck, Embracing change with Extreme Programming. IEEE
so chances of getting defect will become very less in Computer, Vol. 32, Issue 10 October 1999.
future. Also, this methodology increases QA and Build [2] J. Stapl eton, Dynamic systems development method - The method
team confidence and communication. in practice. Addi son Wesley 1997
So, Agile currently is new and one ofthe most getting [3] K. Beck, Extreme Programming explained: Embrace change.
used to methodology due to its advantages, less delivery Reading, Mass., Addi son-Wesley, Novl6, 2004
cost and other features in Industry nowadays. [4] L. Ri sing and N. S. Janoff, The Scrum software development
process for small teams, IEEE Software, Issue 17,pp. 26-32, 2000
VIII. CONCLUSION [5] K. Schwaber and M. Beedl e, Agil e Software Development with
Scrum, Upper Saddle River, NJ, Prentice - Hall, 1st Editi on, Oct
Waterfall, V-Model & Agile model are chosen for 2001
development of the software. Each has its own advantages

6 Copyright © SMART-2016 ISBN: 978-1-5090-3543-4

Authorized licensed use limited to: University of West London. Downloaded on March 18,2024 at 12:38:41 UTC from IEEE Xplore. Restrictions apply.