Topic: Automated Testing tools making testing easier

Message

Will automated testing tools make testing easier? 

Ans:Possibly.  For small projects, the time needed to learn
and implement them may not be worth it unless personnel are already 
familiar with the tools.  For larger projects,
or on-going long-term projects they can be valuable.

A common type of automated tool is the 'record/playback' type.
For example, a tester could click through all combinations
of menu choices, dialog box choices, buttons, etc. in an
application GUI and have them 'recorded' and the results
logged by a tool.  The 'recording' is typically in the form of
text based on a scripting language that is interpretable by the
testing tool. Often the recorded script is manually modified and 
enhanced.  If new buttons are added, or some underlying code in 
the application is changed, etc. the application might then be
retested by just 'playing back' the 'recorded' actions, and
comparing the logging results to check effects of the changes.
The problem with such tools is that if there are continual
changes to the system being tested, the 'recordings' may have to
be changed so much that it becomes very time-consuming to
continuously update the scripts. Additionally, interpretation and 
analysis of results (screens, data, logs, etc.) can be a difficult 
task. Note that there are record/playback tools for text-based 
interfaces also, and for all types of platforms.

Another common type of approach for automation of functional testing
is 'data-driven' or 'keyword-driven' automated testing, in which the 
test drivers are separated from the data and/or actions utilized in testing
(an 'action' would be something like 'enter a value in a text box').  Test 
drivers can be in the form of automated test tools or custom-written 
testing software. The data and actions can be more easily maintained - such 
as via a spreadsheet - since they are separate from the test drivers.  
The test drivers 'read' the data/action information to perform specified 
tests.  This approach can enable more efficient control, development, 
documentation, and maintenance of automated tests/test cases.

Author	Message
vidhya Senior Member Joined: 24Mar2007 Online Status: Offline Posts: 114	Topic: Automated Testing tools making testing easier Posted: 25Mar2007 at 10:40pm
	Will automated testing tools make testing easier? Ans:Possibly. For small projects, the time needed to learn and implement them may not be worth it unless personnel are already familiar with the tools. For larger projects, or on-going long-term projects they can be valuable. A common type of automated tool is the 'record/playback' type. For example, a tester could click through all combinations of menu choices, dialog box choices, buttons, etc. in an application GUI and have them 'recorded' and the results logged by a tool. The 'recording' is typically in the form of text based on a scripting language that is interpretable by the testing tool. Often the recorded script is manually modified and enhanced. If new buttons are added, or some underlying code in the application is changed, etc. the application might then be retested by just 'playing back' the 'recorded' actions, and comparing the logging results to check effects of the changes. The problem with such tools is that if there are continual changes to the system being tested, the 'recordings' may have to be changed so much that it becomes very time-consuming to continuously update the scripts. Additionally, interpretation and analysis of results (screens, data, logs, etc.) can be a difficult task. Note that there are record/playback tools for text-based interfaces also, and for all types of platforms. Another common type of approach for automation of functional testing is 'data-driven' or 'keyword-driven' automated testing, in which the test drivers are separated from the data and/or actions utilized in testing (an 'action' would be something like 'enter a value in a text box'). Test drivers can be in the form of automated test tools or custom-written testing software. The data and actions can be more easily maintained - such as via a spreadsheet - since they are separate from the test drivers. The test drivers 'read' the data/action information to perform specified tests. This approach can enable more efficient control, development, documentation, and maintenance of automated tests/test cases.
	MBA Examination papers Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Automated Testing @ OneStopTesting