Why should I use static testing techniques?
There are several reasons why one should use static testing techniques.
1: One should use static testing techniques because static testing is a bargain, compared to dynamic testing.
2: Static testing is up to 100 times more effective. Even in selective testing, static testing may be up to 10 times more effective. The most pessimistic estimates suggest a factor of 4.
3: Since static testing is faster and achieves 100% coverage, the unit cost of detecting these bugs by static testing is many times lower than detecting bugs by dynamic testing.
4: About half of the bugs, detectable by dynamic testing, can be detected earlier by static testing.
5: If one uses neither static nor dynamic test tools, the static tools offer greater marginal benefits.
6: If an urgent deadline looms on the horizon, the use of dynamic testing tools can be omitted, but tool supported static testing should never be omitted. Reply
Define : Descriptive Programming ?
Descriptive programming is nothing but a technique using which operations can be performed on the AUT object which are not present in theReply
What we normally check for in the Database Testing?
In DB testing we need to check for,
> The field size validation
> Check constraints.
> Indexes are done or not (for performance related issues)
> Stored procedures
> The field size defined in the application is matching with that in the db. Reply
What is the definiton of top down design?
Top down design progresses from simple design to detailed design. Top down design solves problems by breaking them down into smaller, easier to solve subproblems. Top down design creates solutions to these smaller problems, and then tests them using test drivers. In other words, top down design starts the design process with the main module or system, then progresses down to lower level modules and subsystems. To put it differently, top down design looks at the whole system, and then explodes it into subsystems, or smaller parts. A systems engineer or systems analyst determines what the top level objectives are, and how they can be met. He then divides the system into subsystems, i.e. breaks the whole system into logical, manageable-size modules, and deals with them individually. Reply
What is a Recovery Scenario?
Recovery scenario gives us an option to take some action for recovering from a fatal error in the test. The error could range in from occasional to typical errors. Occasional error would be like "Out of paper" popup error while printing something and typical errors would be like "object is disabled" or "object not found". A test case have more then one scenario associated with it and also have the priority or order in which it should be checked. Reply
What does a Recovery Scenario consists of?
> Trigger : Trigger is nothing but the cause for initiating the recovery scenario. It could be any popup window, any test error, particular state of an object or any application error.
> Action : Action defines what needs to be done if scenario has been triggered. It can consist of a mouse/keyboard event, close application, call a recovery function defined in library file or restart windows. We can have a series of all the specified actions.
> Post-recovery operation : Basically defined what need to be done after the recovery action has been taken. It could be to repeat the step, move to next step etc.Reply
What is the future of software QA/testing?
In software QA/testing, employers increasingly want us to have a combination of technical, business, and personal skills. By technical skills they mean skills in IT, quantitative analysis, data modeling, and technical writing. By business skills they mean skills in strategy and business writing. By personal skills they mean personal communication, leadership, teamwork, and problem-solving skills. We, employees, on the other hand, want increasingly more autonomy, better lifestyle, increasingly more employee oriented company culture, and better geographic location. We continue to enjoy relatively good job security and, depending on the business cycle, many job opportunities. We realize our skills are important, and have strong incentives to upgrade our skills, although sometimes lack the information on how to do so. Educational institutions increasingly ensure that we are exposed to real-life situations and problems, but high turnover rates and a rapid pace of change in the IT industry often act as strong disincentives for employers to invest in our skills, especially non-company specific skills. Employers continue to establish closer links with educational institutions, both through in-house education programs and human resources. The share of IT workers with IT degrees keeps increasing. Certification continues to keep helping employers to quickly identify us with the latest skills. During boom times, smaller and younger companies continue to be the most attractive to us, especially those that offer stock options and performance bonuses in order to retain and attract those of us who are the most skilled. High turnover rates continue to be the norm, especially during economic boom. Software QA/testing continues to be outsourced to offshore locations. Software QA/testing continues to be performed by mostly men, but the share of women keeps increasing. Reply
What is Database testing?
Data bas testing basically include the following.
> Data validity testing.
> Data Integritity testing
> Performance related to data base.
> Testing of Procedure,triggers and functions.
for doing data validity testing we should be good in SQL queries. For data integrity testing we should know about referintial integrity and different constraint. For performance related things we should have idea about the table structure and design. for testing Procedure triggers and functions we should be able to understand the same.Reply
How many types of recording facility are available in QuickTest Professional (QTP)?
QTP provides three types of recording methods-
> Context Recording (Normal)
> Analog Recording
> Low Level RecordingReply
What is data driven test?
Re-execution of our test with different input values is called Re-testing. In validate our Project calculations, test engineer follows retesting manner through automation tool.Re-teting is also called DataDriven Test.There are 4 types of datadriven tests.
> Dynamic Input submissiion ( key driven test) : Sometines a test engineer conducts retesting with different input values to validate the calculation through dynamic submission.For this input submission, test engineer use this function in TSL scriipt-- create_input_dialog ("label");
> Data Driven Files Through FLAT FILES ( .txt,.doc) : Sometimes testengineer conducts re-testing depends on flat file contents. He collect these files from Old Version databases or from customer side.
>Data Driven Tests From FRONTEND GREAVES : Some times a test engineer create automation scripts depends on frontend objects values such as
(d) data window
(5) ocx etc.,
> Data Driven Tests From EXCEL SHEET : sometimes a testengineer follows this type of data driven test to execute their script for multiple inputs. These multiple inputs consists in excel sheet columns. We have to collect this testdata from backend tables . Reply