Detailed Analysis: Test Automation & TDD Experience Report

This report provides an analysis of an experience report on introducing test automation and test-driven development (TDD) within a department at Ericsson AB. The focus is on component-level testing and the implementation of a test automation tool alongside TDD practices. The approach differs from traditional Extreme Programming (XP) by writing tests for components exchanging XMLs rather than individual methods. The report details the implemented test automation tool, its architecture using C++, and the structured approach for isolating components during testing. It also highlights the benefits of using a standard language like C++ for test case development. The analysis emphasizes the importance of robust component interfaces, structured programming guidelines for test cases, and addresses the challenge of integrating older functionality without existing tests. The conclusion points to a reduction in project lead time with the adoption of this approach, while also suggesting areas for further standardization in test case writing. Desklib provides access to this and other solved assignments.

Running head: INTRODUCTION TO TEST AUTOMATION
INTRODUCTION TO TEST AUTOMATION
Name of the Student
Name of the Organization
Author Note

1
INTRODUCTION TO TEST AUTOMATION
Introduction
The article will be identifying as well as presenting a kind of approach for the specific
component-level testing of the software which in a lower cost way can be moving the
detection of the defect much earlier within the procedure of the development (Damm,
Lundberg and Olsson 2005). A particular department at the Ericson AB has introduced a tool
for the automation of the test for a specific testing of the component level in two different
projects altogether with the specific kind of concept of the TDD. TDD is basically a practice
where the code of the test has been well written before the code of the product. The approach
which will be implemented will be greatly differing from the way TDD is utilised in the
specific Extreme programming and in that it has been known that several tests are well
written for several modules which are exchanging XMLs instead of writing various tests for
each and every process in several classes. This report will be actually describing the
automated tool of the test which has been implemented.
Body
As the main purpose of the actual basic test is to properly test all the various
components in the remoteness, the simple tool which is required is mainly for attaching to all
the interfaces of the components.
It is not at all preferable for the enhancement of the DailyTest instead of the
development of a full new tool is actually that for making a DailyTest very much powerful, it
must be becoming a language of the programming.
Instead of enhancing the test tool which has been existing, there is the requirement for
developing a new kind of tool utilising a language which will be greatly standard. TDD tools
are utilised normally in the Extreme Programming and they have been not at all proper as
they are operating upon a level of method. As Basic Test is seen to be needing a kind of
integration which will be very much tough with the architecture of the product, all the various
tools of test which are developed by all the commercial vectors are very much tough to utilise
for this specific purpose since they will be needing certain kind of interface that will be
linking to all the various components for testing. Such a kind of adaption will be involving

2
INTRODUCTION TO TEST AUTOMATION
several additional costs and much more essentially, such kinds of tools will be putting various
constraints which will be unwanted upon specifically how several tests will be actually
executed or rather monitored. This basically united with the particular fact that it is somewhat
inexpensive to particularly design and improve a tool within the house whenever the
architecture of the product will be possessing very high testability.
The department is required to be choosing a kind of language for writing all the cases
of test. All the various huge advantages of utilising the languages of the standard script, like
for an example, Visual Basic or rather JavaScript are all that several programmers greatly
tend towards being very much less prone to any kind of errors as compared to whenever
utilising all the various languages of system programming. The department has finally chosen
C++ as their language for the test case. The cases of test are properly written in the similar
kind of language as that of the product code and here all the various developers have been
able to take great advantage of all the several tools of programming which have been
available already.
After taking the decision of developing a basic test tool which will be in-house with
the language C++ as the language for the test case, the department has finally opted for
utilising the specific kind of structure-driven particular approach whenever any tool is to be
designed. The tool will be actually isolating the specific component for testing from several
cases of the test through various functions of utility and wrappers. Additionally, the tool will
be comprising of various commands for particular handling various states of component and
also for obtaining as well as sending various requests. All the various actions are known to be
controlled by this specific tool and during the process of implementation, the tool will be
comparing each of either sent or rather obtained request with the predictable result of it and
then finally the outcome is logged in the file of XML. All the various requests of XML are
actually produced from all of the corresponding data type definitions. The department has
finally opted XML as the format of the output as it is already utilised as a standard format of
data in all of their products. XML is considered to be a very much standard format to which
all the various tools as well as parsers can be properly attached very much easily.
The strategy of the test is actually to capture all the various outputs as well as inputs
of each and every components. The tests are seen to be exactly representing the outer design
of each of the constituent. This even led to several test cases that can be easily serving as a
specific part of the documentation of the design and thereby substituting some of the other

3
INTRODUCTION TO TEST AUTOMATION
design which has become very much old. This will be actually providing with a much more
detailed design. The Basic Test Concept has been involved with all the various levels of the
process. The full new activity “Basic Test Design” is actually when all the various developers
have been able to properly construct all the various test cases of the components and it will be
involving both the inspection as well as the implementation of several test cases.
There is only a single thing which has been left behind which is basically a kind of
standard for writing various test cases. Otherwise, the department will be observed to be
ending up with various kinds of tests which will be much tough to understand as well as
maintain which will be finally leading towards the loss of several benefits with the
automation of test. Tests must be following certain guidelines for the specific kind of
programming which will be structured such that they will be becoming very much easy to
both maintain as well as understand. There is one challenge which must be addressed by the
department is the implementation of the concept of the new Basic Test and hence all the
various components will be containing a huge amount of older functionality which do not
possess such kinds of tests.
Conclusion
The department of Ericsson has been able to introduce a full new tool of test
automation which has been included with some other approach to the TDD. With such a kind
of approach to the development which is actually test driven, several component interfaces
which are robust will be making the automation of test very much easier. The actual
characteristic of this specific tool is that it particularly utilises C++ as the creators are very
much familiar with it. It is very much influential as compared to the script language and all
the various originators can be taking a lot of advantage of various tools of programming. All
the various aspects are to be considered whenever the test automation is to be implemented.
All the various developers that have utilised the specific concept have been able to estimate
that the lead time of project will be decrementing a lot for each of the version of the project
that will be actually utilising it.

4
INTRODUCTION TO TEST AUTOMATION
References
Damm, L.O., Lundberg, L. and Olsson, D., 2005. Introducing test automation and test-driven
development: An experience report. Electronic Notes in Theoretical Computer Science, 116,
pp.3-15.