ABSTRACT

In Software Industry software development and testing the software

became a major concern. Due to the importance of the testing phase in a software
development lifecycle,
testing has been divided into graphical user interface (GUI) based testing, logi
cal testing, unit testing, integration
testing, etc.GUI Testing has become very important as it provides more sophistic
ated way to interact with
the software. The complexity of testing GUI increased over time. The testing nee
ds to be performed in a
way that it provides effectiveness, efficiency, increased fault detection rate a
nd good path coverage. To
cover all use cases and to provide testing for all possible (success/failure) sc
enarios the length of the test
sequence is considered important. Intent of this paper is to study some techniqu
es used for test case
generation and process for various GUI based software applications.
The world's increased dependence on software-enabled
systems has raised major concerns about software reliability
and security. New cost-effective tools for software quality assurance
are needed. In the software development life cycle it has been proven that the s
oftware testing phase is
one of the most critical and important phase . In general, the
software testing phase takes around 40-70% of the
effort, time, and cost. This area is well researched
over a long period of time. Unfortunately, while many
researchers have found methods of reducing time and
cost during the testing process, there are still a
number of important related issues that need to be
researched. This project work introduces a new high level
test case generation process with a requirement
prioritization method to resolve the following
research problems: unable to identify suitable test
cases with limited resources, lack of an ability to
identify critical domain requirements in the test case
generation process and ignore a number of generated
test cases. This project work presents an automated test
generation technique, called Requirement-based Software Integration Test Automat
ion.

When integrating different system components, the interaction

between dierent features is often error prone. Typically
errors occur on interruption, concurrency or disabling/
enabling between dierent features. Test case generation for
integration testing struggles with two problems: the large
state space and that these critical relationships are often
not explicitly modeled. The approach presented in this paper
is to use task models to describe the interaction between
environment and system. This restricts the possible
state space to a feasible size and enables the generation of
task sequences, which cover the critical interaction scenarios.
These task sequences are too abstract for testing the SystemUnder-Test (SUT), due to missing input- and expected output
behavior. To overcome the dierent abstraction levels,
the tasks are mapped to component behavior models. Based
on this mapping, task sequences can be enriched with additional

information from the component models and thereby

executed to test the SUT.