\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Approach to Quality Testing},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2012-01-15 (revised: 15 January 2012)}
\def\TheID{\makeatother }
\def\TheDate{2012-01-15}
\title{Approach to Quality Testing}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Dr.  Drakshaveni  G}

             \affil[1]{  vtu}

\renewcommand\Authands{ and }

\date{\small \em Received: 8 December 2011 Accepted: 2 January 2012 Published: 15 January 2012}

\maketitle


\begin{abstract}
        


Time is the most important resource for any activity. Software development is no exception. With an increase in the competition in the market, it is very essential for the companies to release their products into the market at the earliest with good quality to earn profit. In order to develop the products early, companies implement various techniques like Rapid Application development and implement Agile methodologies like Scrum & Xtreme Programming to obtain tangible and useful features of the software at the earliest. It is just not sufficient to develop the product, it is more important to develop a quality product. But how does one know if the product is of good quality or not? This question is best answered by the Quality Assurance team which Tests the product end to end against requirements and standards. They conduct various kinds of tests and check the behavior of the system/ product in various conditions. If it passes all kinds of tests (which is dependent on the kind of the product or the system), then the QA team assures that the product is fit for use. Hence it is very important for the QA time to be given enough time to test the product/system before it is released into market. But it is difficult to judge as to how much time is required to test a product / system completely. An ideal answer would be "Years". Time is a major constraint in any software activity. Many software projects are time bound. Then how does one ensure that within a given time, the product/system is tested to the level where a confidence can be achieved?The answer is one needs to adopt faster means of testing. Many Testing techniques are available which in help achieving this objective. The major drawback of some of the proved techniques is these techniques are dependent on the kind of the system that is being tested. So what are the other ways available to save time for testing? The answer is in the question itself. One can save some time in optimizing the way of testing itself. If we carefully look into each testing activity, we realize that we can improve these to a great extend to provide maximum output. In this paper, it is intended to showcase one such approach.

\end{abstract}


\keywords{Test Management, Defect tracking, , SDLC MODEL, Test planning.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
esting is an important part of SDLC \hyperref[b0]{[1]}. It is in this phase that the quality of the product is assured. The product is tested in detail against the requirements and standards. This is not as simple as it sounds. There are many phases in a Test life cycle like Test planning, Design, execution etc.  When the Requirements are provided, the requirements are captured in a repository using a suitable convention which is easily understood by the stakeholders. Then it is analyzed for implementation. In this phase static testing techniques are implemented. Once the Analysis is complete, Planning comes into picture. This is a complex phases. It is in this phase that the testing approach is designed based on various constraints defined by the project. The success of Testing is largely dependent on the Test Planning \& Design phase. Once the planning \& Design phase is crossed, then comes the execution i.e. execution of test cases against the requirements and standards. After test execution, the results are analyzed and the quality is measured accordingly. If more test cases / Test scenarios (depending on which one is used) fail, then the product is sent back to the development team to fix the issues. After the issues are fixed, the product is tested again. This process continues till the there are very minimum or no issues detected. If the product is tested and no issues are found, then the product is certified as fit for use.\par
In the above stated model, each phase has its on set of Inputs, processes and outputs. Any testing activity will be incomplete without supporting artifacts. Hence proper documentation is very important. It is not just sufficient that the product is tested for what it has to do. It is equally important to test a product for what it should not do as well. This is the reason that there will be many input conditions that need to be checked for. Hence testing is a time consuming activity. With Time being a constraint, how to complete so many activities in minimum time? What are the ways in which one can execute the testing activities faster? Let's see few of them. 
\section[{II.}]{II.} 
\section[{Description}]{Description}\par
There are many ways through which the testing activities can be optimized. By implementation of these, lot of time can be saved which can be used to execute other activities which yield more result. Few of the most common and useful approaches in this regards are: 1. Transition from Manual to Automation Testing. 2. Usage of good Tools. 3. Forming a team of highly skilled persons.\par
Let's see how the above approaches can help save time and improve the testing quality. 
\section[{a) Transition from Manual to Automation Testing}]{a) Transition from Manual to Automation Testing}\par
Transition from Manual to Automation is beneficial for the features of Automation. Few of them are Reliability, Repeatability, Fast, accuracy and Cost Reduction \hyperref[b1]{[2]}. The Automation tools use Test Script language to develop scripts that imitate user actions.\par
The Test Script Language (like VB Script) is easy to learn and implement. These scripts can be designed to test the applications as a human would do. But the difference is they are faster. They can execute a task as many number of times as instructed without any errors.\par
As an example, if it takes 1 hour to execute 5 test cases, the Automation scripts can do it in 30 min (Depending on the way the script is developed and the application behaviour).Hence those features of the application which are very stable and require repeated testing, can be automated. The Manual testers can use the same time to test other parts of the application where more defects are likely t be found. Hence more testing can be done within available time. Hence the product can be tested better. 
\section[{b) Usage of good Tools}]{b) Usage of good Tools}\par
Usage of tools like Test Management Tools \hyperref[b2]{[3]}, Defect Tracking Tools and Configuration tools, helps in achieving testing objective faster. These tools have templates/ formats which can be used readily. For example, Quality Center (a Test Management Tool) provides a single application for management of requirements, Test cases, execution and defect management. The reports generated from these tools give a single window data of the status of Testing. This can help the project manager decide the quality of the product. Without this, a subjective decision would be required to be taken regarding the quality of the product, which is a risk by itself. If data is required then it would take a considerable time to collect the same and put it in a format which is easily understood by the stakeholders. Many important Testing artifacts can be stored in such tools which provide the inputs at the execution time. In absence of such tools, the testers would have to refer documents from various sources and when the execution is at its peak, this takes lot of time.\par
The defect tracking tools help save some time by intimating the right persons at right time irrespective of their location. Example, if a defect is logged, the developer is intimated instantaneously through a mail or an alert, with all the required details as provided by the tester. In such scenarios, most of the times, the developer need not get in a discussion with the tester to know what the defect is all about. Also he can communicate with other teams instantaneously with the all required information. This saves lot of time. c) Forming a Team of Highly Skilled Persons This is a time tested approach \hyperref[b3]{[4]}. Having team with people who know the application/product/system better are always beneficial. They can help the team members by guiding them in the following areas: a. Implementation of special testing techniques like Orthogonal Array Technique, branch Testing etc b. Usage of Tools in an optimum way. c. Usage of right inputs to test the application d. Understanding the domain and the purpose of each testing phase. e. Understanding the requirements, Test processes, Test Reports etc.\par
In absence of a proper guide, one needs to spend more time in understanding the things. With time constraint, if a tester can't understand the full functionality, the functionality can't be tested properly. This is a risk. And if the defect is found at later stage, it would cost more to the project to fix the same. At the same time, there should be new people in the team who can test the product as an new user would do. They might have a new way to seeing a functionality which might help in testing it better and making it better. Testing is a creative activity which requires a good understanding of the application, domain, Testing principles and new ways to thinking. Hence the team should be a combination of people with such mentality so that optimum testing can be done and more defects can be detected at early state. This way rework can be reduced to some extent and hence the time.  implementation of Automation tools. It is not easy to get people who are well versed in usage of these tools. If they are, then they need to be paid more. This again puts constraint on the project budget. c. Team members need to be trained in usage of the tools which itself consumes time \& money.\par
c) Forming a Highly Skilled Team a. Difficult to judge the expertise in the required area. Complete knowledge cannot be checked in just a couple of interviews.\par
b. Availability of experts employment of such people is bit difficult and as they look for high salaries which puts a constraint on the budget of the project.\par
IV. 
\section[{Proposed solution}]{Proposed solution}\par
Every problem has a solution. Most of the times, the solution to a problem is very much available but with some search. Having seen the difficulties in implementing the time saving techniques, let us see if we can save some time in the testing process itself. For this, we need to understand what a tester does. Here are some of the steps which most of the testers follow: It is possible to help the testers save some time in step 4 stated above. Normally when a discrepancy is observed, a good tester captures the basic information like how the defect was detected, what was the defect, screen shot of the system (if possible) and associated details. Along with execution of the test case, the tester needs to spend some time recreating the defect to confirm the behavior. Lets take an example.\par
Suppose a tester is executing a test case for a web based application. That test case has 12 steps and it takes 20 minutes to execute the test case. When the tester finds that step 6 is failing, he logs a defect in the Defect Tracking Tool. He first needs to capture the screenshot of the application to let the developer know as to what is the defect. Then he needs to write the steps to reproduce the defect. It should be elaborate enough for the developer to understand the steps of re-creation the defect. Then he needs to provide some information like Version of the application tested, date \& time at which the defect was detected, actual result of the step and expected result etc. On an average depending on the expertise of usage f the defect management tool and the application knowledge, it can take somewhere around 10 to 15 minutes to log the defect with all the required details. This is a considerable amount of time when compared to the test case execution time. This does not stop here. As a good practice, all steps of the test case should be executed to be sure that there are no defect goes detected. If there is another defect detected in step 9 of the same test case, again some considerable time and effort should be spent for defect logging. In such a process, the time spent on defect logging is more than the test case execution time itself. 
\section[{( D D D D )}]{( D D D D )}\par
Here is a method which can help reduce the defect logging time so that the tester can use the same time in execution of other important test cases. This is a solution that should be incorporated in the tool form which the test case is being executed.\par
1. Make sure that a test case has only on e scenario. 2. If a step in the test case fails, the tool should capture the following details and store it in a repository a. Screenshot of the application. b.\par
Step description and expected result of all the previous steps in the 'steps to reproduce the defect section' along with expected result of the step that failed so that the developer can fix the code accordingly. c. Time stamp information. (I.e. Date and time on which the defect was observed) d. Version of the application that is being tested (Build number). This information can b entered in some file from where the tool can pick this up. e. The test data that was used while execution of the test case. This information can be captured by making sure that each test case has a unique test data available at the time of execution. This information can be stored in a separate file with Test Data \& Test case mapping so that the tool picks up this information when required. f. Severity of the issue. This should be defined during the test case design for each step. The test case designer should know the impact of failure of the step that is being executed, on the application.\par
The above points are just few of the information that can be captured. Other mandatory information can also be captured.\par
3. Once all the above information is available, the tool should format the information in a way which is easily understood by all stakeholders and should present it to the tester who wishes to log the defect (can be in form of a pop-up window). 4. Depending on the time availability, the tester can review the captured details before submitting the defect or can add extra information, if required.\par
This way the process of defect logging which takes 10 to 15 minutes, can be reduced to just couple of minutes. If a tester executes 15 such test cases, and on an average he detects 4 defects, he can easily save 30 minutes (approximately) which can be used for adhoc testing or execution of some other important test case. If there are 5 testers, who perform a similar job, in the above scenario, 2.5 hours can be saved. 
\section[{V.}]{V.}\par
Advantages of the above method 1. Time saving: The process of defect logging becomes faster. Instead of taking 10 minutes, the defect can be logged in a couple of minutes.\par
2. Since the information that needs to be captured becomes standardized, chances of missing out details are reduced to a great extent. 3. Since the information is captured immediately the timestamp information is more accurate which helps the developers to check the logs as to what exactly happened at that instance of time. 4. This method necessitates that the test case be understandable, logical and complete. This helps the new resources of the team to execute the test case easily (which otherwise would have required more time to execute the same). So considerable time is saved and the tester would feel more comfortable. 5. Along with this, it also necessitates defining the impact f failure of each step, which prevents subjective decision on the assigning the severity to the defect which is to be logged for the failure of that step.  
\section[{Challenges in implanting this method}]{Challenges in implanting this method}\par
Although there are many advantages of this method, there are a couple of drawbacks too. 1. This method calls for use of a tool which can capture all the required information and translate it into useful information as contained in a defect log. This involves time, effort and cost. The project might not have so much time or money to spend on development of such a specialized tool. 2. This method requires defining more details like severity of each step of a test case, capturing unique test data for each test case etc which requires more time and effort. 
\section[{VII.}]{VII.}\par
Where can this method be useful?\par
The approach proposed in this paper can be added in any Test Management Tool which has Test case execution and Defect Management features. This approach will be helpful in testing projects where Defect Finding Rate is high and more test cases need to be executed in a shorter time.  
\section[{Conclusion}]{Conclusion}\par
Testers should be given sufficient time to test the system/ product/application in order to get a good quality product. When there is a time crunch, projects should optimize the way testing is carried out. The method stated in this paper can help the Testing project irrespective of the SDLC model followed, to save reasonable time which can be used for performing other important testing activities. \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Fig. 1}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{fig_3}}\end{figure}
  \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.85\textwidth}}
h. The new resources involved in automation, need to\\
be trained in usage of the tools which itself consumes\\
time \& money.\\
i. Automation can be implemented for those\\
applications which are stable. If the application is not\\
stable, then automaton can't be implemented\\
effectively.\\
b) Tools\\
a. Good Test Management, Defect Tracking \&\\
Configuration Management Tools are costly.\\
b. Availability of resources trained in usage \&\end{longtable} \par
 
\caption{\label{tab_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.85\textwidth}}
VI.\end{longtable} \par
 
\caption{\label{tab_2}}\end{figure}
 			\footnote{© 2012 Global Journals Inc. (US)} 		 		\backmatter   			 
\subsection[{Acknowledgement}]{Acknowledgement}\par
We wish to thank all the authors for the providing the informational support 			  			  				\begin{bibitemlist}{1}
\bibitem[Engineering-Ian and Somerville]{b1}\label{b1} 	 		\textit{},  		 			Software Engineering-Ian 		,  		 			Somerville 		.  		 	 
\bibitem[A very comprehensive book on the testing techniques]{b2}\label{b2} 	 		\textit{A very comprehensive book on the testing techniques},  				 	 
\bibitem[Johnson and Ho]{b3}\label{b3} 	 		‘Incorporating Performance Testing in Test-Driven Development’.  		 			M Johnson 		,  		 			Maximilien Ho 		,  		 			M 		,  		 			Williams 		,  		 			L 		.  	 	 		\textit{IEEE Software}  		 	 
\bibitem[Testing Common Body of Knowledge]{b0}\label{b0} 	 		\textit{Testing Common Body of Knowledge},  		 	 
\end{bibitemlist}
 			 		 	 
\end{document}
