Test Automation and Test Driven Development

Running head: TEST AUTOMATION AND TEST DRIVEN DEVELOPMENT
TEST AUTOMATION AND TEST DRIVEN DEVELOPMENT
Name of the student:
Name of the university:
Author Note:

TEST AUTOMATION AND TEST DRIVEN DEVELOPMENT1
Table of Contents
1.0 Introduction..........................................................................................................................2
2.0 Intention and Content of Article..........................................................................................2
3.0 Conclusion............................................................................................................................5
4.0 References............................................................................................................................7

TEST AUTOMATION AND TEST DRIVEN DEVELOPMENT2
1.0 Introduction
Test Driven Development is depicted as the programming practice that involves the
procedure of providing instructions to the developers in respect to the write significant new
codes if the procedure of the automation test fails. This procedure will prevent the duplicate
writing of the codes. The concept of TDD deals with the fact that the significant code is
written as well as tested for the detection of any type of failure while the codes are in
execution. This will apparently avoid the code duplication and this is due to the fact that
significant small amount of code is written at a particular time. This will help the tests to pass
in a significant time thus adhering the correctness of the code. The further part of the report
will deal with the significant discussions that are required to understand the concept of test
automation and its associated methodologies.
2.0 Intention and Content of Article
The significant intention of the article is to depict the overall concept of the test
driven methodology related to the testing of the written codes. There was a methodology that
was used before the introduction of this type of concept that is identified as the Test Tool.
This tool processes the executable parts of a written code thus adhering the mistakes with the
proper communication in regards to the other components associated with the code. This is
carried out by the tool using interfaces that are identified to be common. This test tool was
provided with a name that is defied to be Daily Test [1]. This tool has the capability to
execute significant scripts that possess simple compounds along with the loads of component,
thus sending them a sequence of significant requests thus helping them to execute the
commands. But the tool was found to be limited in many aspects, the most important being
the fact that there was no proper integration in respect to the development processes. Thus, it