Professional Documents
Culture Documents
Asnwers To Advanced Software Testing Interview Questions PDF
Asnwers To Advanced Software Testing Interview Questions PDF
31/08/13 6:55 PM
Page 1 of 13
31/08/13 6:55 PM
Page 2 of 13
31/08/13 6:55 PM
Page 3 of 13
31/08/13 6:55 PM
Page 4 of 13
31/08/13 6:55 PM
cost. Is this test likely to die sooner or later? What events are likely to end it?
3. During its lifetime, how likely is this test to find additional bugs (beyond whatever
bugs it found the first time it ran)? How does this uncertain benefit balance against
the cost of automation?
4. Return of Investment.
Ans: Keyword driven testing:
This requires the development of data tables and keywords, independent of the test
automation tool used to execute them and the test script code that "drives" the application-under-test and the data. Keyword-driven tests look very similar to manual test
cases. In a keyword-driven test, the functionality of the application-under-test is documented in a table as well as in step-by-step instructions for each test. In this method,
the entire process is data-driven, including functionality
The merits of the Keyword Driven Testing are as follows,
- The Detail Test Plan can be written in Spreadsheet format containing all input and
verification data.
- If "utility" scripts can be created by someone proficient in the automated tools
Scripting language prior to the Detail Test Plan being written, then the tester can use
the Automated Test Tool immediately via the "spreadsheet-input" method, without
needing to learn the Scripting language.
- The tester need only learn the "Key Words" required, and the specific format to use
within the Test Plan. This allows the tester to be productive with the test tool very
quickly, and allows more extensive training in the test tool to be scheduled at a more
convenient time.
Demerits of keyword driven testing
The demerits of the Keyword Driven Testing are as follows:
- Development of "customized" (Application-Specific) Functions and Utilities requires proficiency in the tools Scripting language. (Note that this is also true for any
method)
- If application requires more than a few "customized" Utilities, this will require the
tester to learn a number of "Key Words" and special formats. This can be time-consuming, and may have an initial impact on Test Plan Development. Once the testers
get used to this, however, the time required to produce a test case is greatly improved.
http://www.softwaretestingtimes.com/2010/04/asnwers-to-advanced-software-testing.html
Page 5 of 13
31/08/13 6:55 PM
Ans: The architecture of the Test Plan Driven method appears similar to that of
the Functional Decomposition method, but in fact, they are substantially
different:
* Driver Script
* Performs initialization, if required;
* Calls the Application-Specific Controller Script, passing to it the file-names of the
Test Cases (which have been saved from the spreadsheets as a
tab-delimited files);
* The Controller Script
* Reads and processes the file-name received from Driver;
* Matches on Key Words contained in the input-file
* Builds a parameter-list from the records that follow;
* Calls Utility scripts associated with the Key Words, passing the created parameter-list;
* Utility Scripts
* Process input parameter-list received from the Controller script;
* Perform specific tasks (e.g. press a key or button, enter data, verify data, etc.), calling User Defined Functions if required;
* Report any errors to a Test Report for the test case;
* Return to Controller script;
* User Defined Functions
* General and Application-Specific functions may be called by any of the above
script-types in order to perform specific tasks;
Advantages
This method has all of the advantages of the Functional Decomposition method, as
well as the following:
* The Detail Test Plan can be written in Spreadsheet format containing all input and
verification data. Therefore the tester only needs to write this
once, rather than, for example, writing it in Word, and then creating input and verifihttp://www.softwaretestingtimes.com/2010/04/asnwers-to-advanced-software-testing.html
Page 6 of 13
31/08/13 6:55 PM
Page 7 of 13
31/08/13 6:55 PM
Page 8 of 13
31/08/13 6:55 PM
http://www.softwaretestingtimes.com/2010/04/asnwers-to-advanced-software-testing.html
Page 9 of 13
31/08/13 6:55 PM
Page 10 of 13
31/08/13 6:55 PM
Configuration management (CM) is the detailed recording and updating of information that describes an enterprise's computer systems and networks, including all
hardware and software components. Such information typically includes the versions
and updates that have been applied to installed software packages and the locations
and network addresses of hardware devices. Special configuration management software is available. When a system needs a hardware or software upgrade, a computer
technician can accesses the configuration management program and database to see
what is currently installed. The technician can then make a more informed decision
about the upgrade needed.
An advantage of a configuration management application is that the entire collection
of systems can be reviewed to make sure any changes made to one system do not adversely affect any of the other systems.
Ans: Statement coverage in Software Testing - Has each line of the source code been
executed?
Statement coverage is one of the ways of measuring code coverage. It describes the
degree to which the software code of a program has been tested.
All the statements in the code must be executed and tested.
Statement coverage means statement wise we need to give proper test cases.
For your example we need 3 statement coverages test cases are needed. and 2 branch
coverages are needed.
Branch coverage will be on true and false for if statements.
path coverage = branch coverage +1
Ans: Multiple condition coverage metric of software testing
Multiple condition coverage reports whether every possible combination of Boolean
sub-expressions occurs. 100% multiple condition coverage implies 100% condition
determination coverage.
Drawback of this metric is that it becomes tedious to find out the minimum number
of test cases required, especially for very complex Boolean expressions.
Another drawback of this metric is that the number of test cases required can vary to
a large extent among various conditions having similar complexity.
http://www.softwaretestingtimes.com/2010/04/asnwers-to-advanced-software-testing.html
Page 11 of 13
31/08/13 6:55 PM
Page 12 of 13
31/08/13 6:55 PM
http://www.softwaretestingtimes.com/2010/04/asnwers-to-advanced-software-testing.html
Page 13 of 13