Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

How to write a Batch script and Batch Framework?

Answer Posted / pratichi

1>The test script modularity framework requires the creation
of small, independent scripts that represent modules,
sections, and functions of the application-under-test. These
small scripts are then used in a hierarchical fashion to
construct larger tests, realizing a particular test case.

Of all the frameworks I'll review, this one should be the
simplest to grasp and master. It's a well-known programming
strategy to build an abstraction layer in front of a
component to hide the component from the rest of the
application. This insulates the application from
modifications in the component and provides modularity in
the application design. The test script modularity framework
applies this principle of abstraction or encapsulation in
order to improve the maintainability and scalability of
automated test suites.

2> Test Driver frameworks "drive" the replay of scripts. For
example, the SAFS framework uses keywords in plain text
files rather than a matrix of function calls.

This makes it faster and easier to use test tools because they:

1. Provide common functions for error detection, logging,
etc. not provided by test tools. Because the framework's
functions automatically performs validations on every object
within every action without additional coding, many hours of
script coding and debugging is avoided. For example, the
WRSAFS framework includes the CSO libraries of functions for
WinRunner users

2. Provide complete examples. For example, WRSAFS
installation enables a complete test of the "flight"
application that is WinRunner's sample application.

3. Define de-facto naming conventions for common
environment variables, functions, messages, and other
terminology.

4. Make test specs independent of the test tool. Another
tool can potentially be substituted for WinRunner because
rather than making calls to the unique syntax of each tool's
API, the framework processes generic keywords in plain text
files. Otherwise, test scripts crafted for one test tool are
usually useless for use in competitive tools.

5. Allow testing work to begin sooner. Unlike
capture/playback, which requires the application to be
operational, the framework's three-layer test specification
hides low-level details. During application design, when use
cases are known, Test Analysts can define "what" to test
(the "high-level" test cycles) without knowing the scripting
language. When specific application variable names are
known, analysts can define test suites with specific values.
"How" the application's gui map and scripts implement the
action keywords is done as the application matures.

6. Enables testing work to progress in a structured,
top-down, distributed approach by several specialists
working separately.

Unlike tracing function calls within many pages of
test script code, keyword test specs don't have extraneous
programming characters, so they are easier to follow what is
being tested. This makes it easier to have separate
(several) script programmers working on different parts of
the app, making the test project easier to scale larger.

This makes for a much more manageable process to plan
and track.

7. Use of public domain frameworks distributes the work.
For example, here are the recent changes to the framework
source:
* ANSI wide character support

Is This Answer Correct ?    0 Yes 1 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

I want to know about satyam manual testing questions

1836


What is the Diff between Code Walkthrough & Code Review? What is the diff between walkthrough and inspection? What is meant by GUI Testing?

2107


List the considerations in developing testing methodology

6704


What is Registry?

2094


Tell some examples of bug severity and bug priority?

1075


Please can any one tell me 1).Types of reports 2).Types of Meetings.

1835


Define what is a critical bug.

1174


Write the 10 high test cases for making video call/face time

8249


structure of an incident report is covered in stand for software test document IEEE 829 and is called as?

2736


functional testing test cases for transfer funds ?

1660


What is big bang approach?

1369


1.What is configuration Management? 2. Explain Impact Analysis 3. Explain Peer Review 4. what i kickoff phase of Formal Review. 5. Whatv are the phases of fundamental test process. 6. what is state transition testing. 7. what is LCSAJ 8. Test conditions are derived from where?

2003


How do you go about testing a project?

2015


please anyone let me know the -ve testing of Excel sheet?

9602


what does 80hz refresh rate indicates?

2891