Challenges in Manual and Automation Testing by threesixtylogica1


More Info
									   Challenges in Manual and Automation Testing
Whether it is manual testing or test framework automation, the challenges are galore thanks to
the enhanced focus on end-user aspirations and emerging security challenges. The complexity of
the software testing process has gone up manifold with increased demand for enhanced and
hassle-free performance of applications across a variety of spectrums and users separated by
technological and geographical divisions. Advent of smart handheld and installed devices and
consumers conscious of next-generation suave experience have made testing experts share the
concern and challenges faced by developers.

Manual Testing Vs Test Automation

Manual testing is the process of detecting defects in software applications through manual
methods. It needs extensive use of human involvement for every bit of the process to operate and
report. The testing engineers double up as analyzers and examiners and also don the hat of end
users to ensure the correct behavior of software application.

On the other hand, test automation is the use of special software to control the execution of tests
and the comparison of actual results with predicted results. It differs from the manual testing for
minimal use of human resource and maximum use of the automation tools, such as Winrunner,
Selenium, Canoo, Webload, Loadrunner, etc.

Manual Software Testing and Major Challenges

Timeliness and Schedule: In today’s business environment, where market introduction fast
gives an unprecedented edge, both developers and testing experts are hard pressed to wind up
under a tight schedule. Working to deliver in time facing an unrealistic imposed project end dates
is likely to have adverse consequences. However, the testing team must be well equipped with
resources to face timeliness challenges successfully without compromising on the quality and the
delivery schedule.

Risk Management: Manual testing is resource intensive and must be backed by adequate support
plan. Any half-way diversion or withdrawal as well as paucity of resources and expertise may
impact the entire application testing result. The software testing teams should be vigilant from
the starting and prepared with advance mitigation plans to prevent and overcome critical
resource loses.

Requirements: Fulfilling exact requirements is a big challenge. Client has a steadfast policy and
many a time inputs supplied lack adequate explanation. There may be also communication gaps.
Above all diagnosing the minute end-user functional and performance requirements in distinct
age and cultural user groups prove to be a big challenge for test teams.

Human Attention: The human resources employed during the software testing process confront
with challenges at a variety of levels. First, employing the right experts and sustaining their
efforts throughout the project. Second, making the right support and expertise available to the
test expert. Third, ensuring right human focus throughout the process despite tedious and
stressful testing requirements and schedule.
Writing Correct Test Cases: A key requirement, writing good test case is also a challenge. Test
case/Test script is a set of variables under which a tester decides whether an application is
working properly. Good test case make application better and it can work as a guide to other
testers too. It is important for testers to think beyond the test cases and to generate more test

Test Automation and Major Challenges

Object Identification: While recording the operation on application QTP tries to captures the
properties to identify each set uniquely. First, it concentrates on mandatory properties to identify
the objects uniquely, if it is not possible it concentrates on assistive properties and again if it's
not possible, it capture the ordinal identifier like index, location, creation time and store it in a
file. It is called object repository file. Using this QTP identifies the objects or windows.
However, it requires expertise to ensure that the process proceeds on the right track and you are
to hit the bull’s eye.

Data Base Automation: Whether instrumentating your database development with a continuous
integration process or automating the deployment of your database changes to test or production
environments, database automation holds a major challenge. With a lack of a one solution for all
problems, application testing experts often stuck in reinventing a variation of the same wheel and
repeat the same mistakes time and again.

The most common data base automation challenges include

Deploying database changes without downtime
Managing branch database development
Managing embedded procedural code
Creating reliable database state with large volumes of data

Test Data Management: Preparing and managing the test data is one of the most important tasks
during the software testing. It is one of the first and crucial phases for web services testing.
During the testing process, GH test scripts act as a template to which teams drive test data
irrespective of the environment against which tests are executed. There are many ways to collect
data, from logs, from sample messages extracted from the Server logs, from Test data
Repositories, and from Database, and the process must have been programmed to do the same.

Risk Management: The testing automation process is not entirely free from risks. Unless the
automation and its tools are customized to your exact requirements, the test results may vary.
There should be a back-up plan for monitoring and sustaining the testing process.

Cross browser testing: Cross-browser testing refers to examining the ability of a website or a
web application to function in environments that provide its required features and to degrade
gracefully when features are absent. Programming the test automation to reflect diverse browser
compatibility is always a big challenge.


To top