Scribd
Upload
22 views

Test Automation Use cases and Principles

Uploaded by

Ishita Agarwal
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
22 views

Test Automation Use cases and Principles

Uploaded by

Ishita Agarwal
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Test

Automation
Use cases
and Principles
Test automation is usually considered as the means of
reducing the costs and/or increasing the scope of
regression testing (i.e. testing in order to ensure that
changes introduced as the result of coding new features

Test did not break old functionality).

Automati Thus, the same tests have to be executed against the


same functionality for each new release, and it makes

on
sense to prepare test scripts that will do this work
automatically.

Overview This works best if the regression library can be broken


down into a large number of relatively simple isolated
test scenarios. Each scenario should consist of several
steps,
It is critically important to identify
correctly only those test scenarios
Targets of which are suitable for automation.

Test
Automati In General, the automation team uses
manual test scenarios as the basis for
on automated test scripts, which can be a
simple process when using a UI screen
manipulation framework
• Example: HP Quick Test Pro or Borland Silk Tes
• Enter search criteria and click
“Search” button;

For example, if you want to test a • Read and verify the results list;
search engine within a web site, e.g., we may check the number or
you will have a scenario consisting the results or specific pages that
of the following steps: must be returned;

After one has implemented such a


scenario, automated testing of
• Iterate through obtained links
thousands of test cases becomes
and verify that they work.
possible by just selecting different
search criteria.
For test automation, it is critical that the
environment is completely controlled by
the automated test scenarios

If it is not, automated scripts will not be


stable enough to achieve the benefits of
automation as compared to manual testing.

Ideally, all system components and data


should be controlled by automated tests.
Test automation can also be useful f
When testing is focused around business logic or business rules;

Test If one controls the test environment, including all of its external
feeds, connections and data storages;
automation
is When the system is exposed via an API or a network connection
with a specific protocol;

recommende When it is possible to develop a few simple scenarios with many


d: variations of input parameters to cover the main system
functionality.

Test automation is not recommended when the testing is


concentrated on the UI.
Test Script Development Environment

The Usually, testers use tools to develop and


Componen execute automated test scripts.
• One of the standard tools is the HP Quick Test Pro
ts of Test Utility, which allows the development of test
scenarios using VBScript language.
Automatio • Another example is FIX/API testing tools.
• These tools allow developing automated tests
n Solution using the FIX protocol or a custom API.
• They also allow preparing test scenarios that
involve the invocation of the web services,
responses validations and generic java actions
Test scripts contain the logic of
tests.

Test They can be either programs or


Scenario spreadsheets defining the steps of
the testing process.

s
Test scripts should be kept in a
human readable format, because
QA or business analysts should be
able to read and understand them.
Test data is a crucial part of all automated test
suites and comprises the following:

Prepared
• Different securities and their parameters;
• Different trader accounts and their settings;
• Market Data all securities featuring in the test scenario;

Test • Other thing which may affect trading business logic

Automated tests are heavily dependent on test

Input data.
• Part of it can be stored in Excel spreadsheets within the test

Data
script.
• The test script developer is responsible for maintaining
accurate and consistent test data.
• Another part of test data is stored within databases; the
person running the test script is responsible for maintaining
this data, including appropriate user accounts,
UI Controllers are Unstable
Common There are two major problems with this
Problems approach.

with Test • Firstly, scripts developed with this technology are


tied in to the current version of the trading
desktop’s UI and can easily be broken when the
Automati latter is upgraded.
• Secondly, there are many different UI frameworks

on (such as ActiveX, .NET forms), against which UI


controllers often freeze or crash. Therefore the
scripts developed on such tools may require
significant maintenance and execution effort.
Test Environment is Unstable

• Sometimes it is difficult to run automated tests,


because the test environment is unstable.
• Tests fail for no obvious reason due to
environment problems.

Test Execution is Too Slow

• End-to-end order management test libraries


contain thousands of test cases. If you use UI
controller tools (such as QTP), it may take a few
minutes to execute each test case, and only one
script per workstation can be run.
• As a result, to execute the whole regression
library, a significant amount of time and/or
hundreds of workstations may be required.

You might also like