Testing Interview Questions
 
Q: What is load testing?
Ans : Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions and to determine weather it can handle peak usage periods.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is Performance testing?
Ans : Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions on the timing of a single transaction.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Explain the Load testing process?
Ans : Step 1: Planning the test. Here, we develop a clearly defined test plan to ensure the test scenarios we develop will accomplish load-testing objectives. Step 2: Creating Vusers. Here, we create Vuser scripts that contain tasks performed by each Vuser, tasks performed by Vusers as a whole, and tasks measured as transactions. Step 3: Creating the scenario. A scenario describes the events that occur during a testing session. It includes a list of machines, scripts, and Vusers that run during the scenario. We create scenarios using LoadRunner Controller. We can create manual scenarios as well as goal-oriented scenarios. In manual scenarios, we define the number of Vusers, the load generator machines, and percentage of Vusers to be assigned to each script. For web tests, we may create a goal-oriented scenario where we define the goal that our test has to achieve. LoadRunner automatically builds a scenario for us. Step 4: Running the scenario. We emulate load on the server by instructing multiple Vusers to perform tasks simultaneously. Before the testing, we set the scenario configuration and scheduling. We can run the entire scenario, Vuser groups, or individual Vusers. Step 5: Monitoring the scenario. We monitor scenario execution using the LoadRunner online runtime, transaction, system resource, Web resource, Web server resource, Web application server resource, database server resource, network delay, streaming media resource, firewall server resource, ERP server resource, and Java performance monitors. Step 6: Analyzing test results. During scenario execution, LoadRunner records the performance of the application under different loads. We use LoadRunner's graphs and reports to analyze the application's performance.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: When do you do load and performance Testing?
Ans : We perform load testing once we are done with interface (GUI) testing. Modern system architectures are large and complex. Whereas single user testing primarily on functionality and user interface of a system component, application testing focuses on performance and reliability of an entire system. For example, a typical application-testing scenario might depict 1000 users logging in simultaneously to a system. This gives rise to issues such as what is the response time of the system, does it crash, will it go with different software applications and platforms, can it hold so many hundreds and thousands of users, etc. This is when we set do load and performance testing.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What are the components of LoadRunner?
Ans : The components of LoadRunner are The Virtual User Generator, Controller, and the Agent process, LoadRunner Analysis and Monitoring, LoadRunner Books Online.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What Component of LoadRunner would you use to record a Script?
Ans : The Virtual User Generator (VuGen) component is used to record a script. It enables you to develop Vuser scripts for a variety of application types and communication protocols.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What Component of LoadRunner would you use to play Back the script in multi user mode?
Ans : The Controller component is used to playback the script in multi-user mode. This is done during a scenario run where a vuser script is executed by a number of vusers in a group.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is a rendezvous point?
Ans : You insert rendezvous points into Vuser scripts to emulate heavy user load on the server. Rendezvous points instruct Vusers to wait during test execution for multiple Vusers to arrive at a certain point, in order that they may simultaneously perform a task. For example, to emulate peak load on the bank server, you can insert a rendezvous point instructing 100 Vusers to deposit cash into their accounts at the same time.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is a scenario?
Ans : A scenario defines the events that occur during each testing session. For example, a scenario defines and controls the number of users to emulate, the actions to be performed, and the machines on which the virtual users run their emulations.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Explain the recording mode for web Vuser script?
Ans : We use VuGen to develop a Vuser script by recording a user performing typical business processes on a client application. VuGen creates the script by recording the activity between the client and the server. For example, in web based applications, VuGen monitors the client end of the database and traces all the requests sent to, and received from, the database server. We use VuGen to: Monitor the communication between the application and the server; Generate the required function calls; and Insert the generated function calls into a Vuser script.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Why do you create parameters?
Ans : Parameters are like script variables. They are used to vary input to the server and to emulate real users. Different sets of data are sent to the server each time the script is run. Better simulate the usage model for more accurate testing from the Controller; one script can emulate many different users on the system.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is correlation? Explain the difference between automatic correlation and manual correlation?
Ans : Correlation is used to obtain data which are unique for each run of the script and which are generated by nested queries. Correlation provides the value to avoid errors arising out of duplicate values and also optimizing the code (to avoid nested queries). Automatic correlation is where we set some rules for correlation. It can be application server specific. Here values are replaced by data which are created by these rules. In manual correlation, the value we want to correlate is scanned and create correlation is used to correlate.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: How do you find out where correlation is required? Give few examples from your projects?
Ans : Two ways: First we can scan for correlations, and see the list of values which can be correlated. From this we can pick a value to be correlated. Secondly, we can record two scripts and compare them. We can look up the difference file to see for the values which needed to be correlated. In my project, there was a unique id developed for each customer, it was nothing but Insurance Number, it was generated automatically and it was sequential and this value was unique. I had to correlate this value, in order to avoid errors while running my script. I did using scan for correlation.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Where do you set automatic correlation options?
Ans : Automatic correlation from web point of view can be set in recording options and correlation tab. Here we can enable correlation for the entire script and choose either issue online messages or offline actions, where we can define rules for that correlation. Automatic correlation for database can be done using show output window and scan for correlation and picking the correlate query tab and choose which query value we want to correlate. If we know the specific value to be correlated, we just do create correlation for the value and specify how the value to be created.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is a function to capture dynamic values in the web Vuser script?
Ans : Web_reg_save_param function saves dynamic data information to a parameter.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: When do you disable log in Virtual User Generator, When do you choose standard and extended logs?
Ans : Once we debug our script and verify that it is functional, we can enable logging for errors only. When we add a script to a scenario, logging is automatically disabled. Standard Log Option: When you select Standard log, it creates a standard log of functions and messages sent during script execution to use for debugging. Disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled Extended Log Option: Select extended log to create an extended log, including warnings and other messages. Disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled. We can specify which additional information should be added to the extended log using the Extended log options.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Explain the Configuration of your systems?
Ans : The configuration of our systems refers to that of the client machines on which we run the Vusers. The configuration of any client machine includes its hardware settings, memory, operating system, software applications, development tools, etc. This system component configuration should match with the overall system configuration that would include the network infrastructure, the web server, the database server, and any other components that go with this larger system so as to achieve the load testing objectives.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: How do you identify the performance bottlenecks?
Ans : Performance Bottlenecks can be detected by using monitors. These monitors might be application server monitors, web server monitors, database server monitors and network monitors. They help in finding out the troubled area in our scenario which causes increased response time. The measurements made are usually performance response time, throughput, hits/sec, network delay graphs, etc.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: If web server, database and Network are all fine where could be the problem?
Ans : The problem could be in the system itself or in the application server or in the code written for the application.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: How did you find web server related issues?
Ans : Using Web resource monitors we can find the performance of web servers. Using these monitors we can analyze throughput on the web server, number of hits per second that occurred during scenario, the number of http responses per second, the number of downloaded pages per second.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: How did you find database related issues?
Ans : By running “Database” monitor and help of “Data Resource Graph” we can find database related issues. E.g. You can specify the resource you want to measure on before running the controller and than you can see database related issues
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is the difference between Overlay graph and Correlate graph?
Ans : Overlay Graph: It overlay the content of two graphs that shares a common x-axis. Left Y-axis on the merged graph show's the current graph's value & Right Y-axis show the value of Y-axis of the graph that was merged. Correlate Graph: Plot the Y-axis of two graphs against each other. The active graph's Y-axis becomes X-axis of merged graph. Y-axis of the graph that was merged becomes merged graph's Y-axis.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: How did you plan the Load? What are the Criteria?
Ans : Load test is planned to decide the number of users, what kind of machines we are going to use and from where they are run. It is based on 2 important documents, Task Distribution Diagram and Transaction profile. Task Distribution Diagram gives us the information on number of users for a particular transaction and the time of the load. The peak usage and off-usage are decided from this Diagram. Transaction profile gives us the information about the transactions name and their priority levels with regard to the scenario we are deciding.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What does vuser_init action contain?
Ans : Vuser_init action contains procedures to login to a server.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What does vuser_end action contain?
Ans : Vuser_end section contains log off procedures.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is think time? How do you change the threshold?
Ans : Think time is the time that a real user waits between actions. Example: When a user receives data from a server, the user may wait several seconds to review the data before responding. This delay is known as the think time. Changing the Threshold: Threshold level is the level below which the recorded think time will be ignored. The default value is five (5) seconds. We can change the think time threshold in the Recording options of the Vugen.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is the difference between standard log and extended log?
Ans : The standard log sends a subset of functions and messages sent during script execution to a log. The subset depends on the Vuser type Extended log sends a detailed script execution messages to the output log. This is mainly used during debugging when we want information about: Parameter substitution. Data returned by the server. Advanced trace.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Explain the following functions: - lr_debug_message
Ans : The lr_debug_message function sends a debug message to the output log when the specified message class is set. lr_output_message - The lr_output_message function sends notifications to the Controller Output window and the Vuser log file. lr_error_message - The lr_error_message function sends an error message to the LoadRunner Output window. lrd_stmt - The lrd_stmt function associates a character string (usually a SQL statement) with a cursor. This function sets a SQL statement to be processed. lrd_fetch - The lrd_fetch function fetches the next row from the result set.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Types of Goals in Goal-Oriented Scenario
Ans : Load Runner provides you with five different types of goals in a goal oriented scenario: The number of concurrent Vusers The number of hits per second The number of transactions per second The number of pages per minute The transaction response time that you want your scenario
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Analysis Scenario (Bottlenecks):
Ans : In Running Vuser graph correlated with the response time graph you can see that as the number of Vusers increases, the average response time of the check itinerary transaction very gradually increases. In other words, the average response time steadily increases as the load increases. At 56 Vusers, there is a sudden, sharp increase in the average response time. We say that the test broke the server. That is the mean time before failure (MTBF). The response time clearly began to degrade when there were more than 56 Vusers running simultaneously.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is the 'software life cycle'?
Ans : The life cycle begins when an application is first conceived and ends when it is no longer in use. It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is SEI? CMM? ISO? IEEE? ANSI? Will it help?
Ans : • SEI = 'Software Engineering Institute' at Carnegie-Mellon University; initiated by the U.S. Defense Department to help improve software development processes. • CMM = 'Capability Maturity Model', developed by the SEI. It's a model of 5 levels of organizational 'maturity' that determine effectiveness in delivering quality software. It is geared to large organizations such as large U.S. Defense Department contractors. However, many of the QA processes involved are appropriate to any organization, and if reasonably applied can be helpful. Organizations can receive CMM ratings by undergoing assessments by qualified auditors. Level 1 - characterized by chaos, periodic panics, and heroic efforts required by individuals to successfully complete projects. Few if any processes in place; successes may not be repeatable. Level 2 - software project tracking, requirements management, realistic planning, and configuration management processes are in place; successful practices can be repeated. Level 3 - standard software development and maintenance processes are integrated throughout an organization; a Software Engineering Process Group is is in place to oversee software processes, and training programs are used to ensure understanding and compliance. Level 4 - metrics are used to track productivity, processes, and products. Project performance is predictable, and quality is consistently high. Level 5 - the focus is on continouous process improvement. The impact of new processes and technologies can be predicted and effectively implemented when required. Perspective on CMM ratings: During 1997-2001, 1018 organizations were assessed. Of those, 27% were rated at Level 1, 39% at 2, 23% at 3, 6% at 4, and 5% at 5. (For ratings during the period 1992-96, 62% were at Level 1, 23% at 2, 13% at 3, 2% at 4, and 0.4% at 5.) The median size of organizations was 100 software engineering/maintenance personnel; 32% of organizations were U.S. federal contractors or agencies. For those rated at Level 1, the most problematical key process area was in Software Quality Assurance. • ISO = 'International Organisation for Standardization' - The ISO 9001:2000 standard (which replaces the previous standard of 1994) concerns quality systems that are assessed by outside auditors, and it applies to many kinds of production and manufacturing organizations, not just software. It covers documentation, design, development, production, testing, installation, servicing, and other processes. The full set of standards consists of: (a)Q9001-2000 - Quality Management Systems: Requirements; (b)Q9000-2000 - Quality Management Systems: Fundamentals and Vocabulary; (c)Q9004-2000 - Quality Management Systems: Guidelines for Performance Improvements. To be ISO 9001 certified, a third-party auditor assesses an organization, and certification is typically good for about 3 years, after which a complete reassessment is required. Note that ISO certification does not necessarily indicate quality products - it indicates only that documented processes are followed. Also see http://www.iso.ch/ for the latest information. In the U.S. the standards can be purchased via the ASQ web site at http://e-standards.asq.org/ • IEEE = 'Institute of Electrical and Electronics Engineers' - among other things, creates standards such as 'IEEE Standard for Software Test Documentation' (IEEE/ANSI Standard 829), 'IEEE Standard of Software Unit Testing (IEEE/ANSI Standard 1008), 'IEEE Standard for Software Quality Assurance Plans' (IEEE/ANSI Standard 730), and others. • ANSI = 'American National Standards Institute', the primary industrial standards body in the U.S.; publishes some software-related standards in conjunction with the IEEE and ASQ (American Society for Quality). • Other software development process assessment methods besides CMM and ISO 9000 include SPICE, Trillium, TickIT. and Bootstrap.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is 'good design'?
Ans : 'Design' could refer to many things, but often refers to 'functional design' or 'internal design'. Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable, and maintainable; is robust with sufficient error-handling and status logging capability; and works correctly when implemented. Good functional design is indicated by an application whose functionality can be traced back to customer and end-user requirements. (See further discussion of functional and internal design in 'What's the big deal about requirements?' in FAQ #2.) For programs that have a user interface, it's often a good idea to assume that the end user will have little computer knowledge and may not read a user manual or even the on-line help; some common rules-of-thumb include: • the program should act in a way that least surprises the user • it should always be evident to the user what can be done next and how to exit • the program shouldn't let the users do something stupid without warning them.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is verification? validation?
Ans : Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings. Validation typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is 'Software Quality Assurance'?
Ans : Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'. (See the Bookstore section's 'Software QA' category for a list of useful books on Software Quality Assurance.)
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is 'Software Testing'?
Ans : Testing involves operation of a system or application under controlled conditions and evaluating the results (eg, 'if the user is in interface A of the application while using hardware B, and does C, then D should happen'). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should. It is oriented to 'detection'. (See the Bookstore section's 'Software Testing' category for a list of useful books on Software Testing.) • Organizations vary considerably in how they assign responsibility for QA and testing. Sometimes they're the combined responsibility of one group or individual. Also common are project teams that include a mix of testers and developers who work closely together, with overall QA processes monitored by project managers. It will depend on what best fits an organization's size and business structure.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: How can World Wide Web sites be tested?
Ans : Web sites are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for web sites can become a major ongoing effort. Other considerations might include: • What are the expected loads on the server (e.g., number of hits per unit time?), and what kind of performance is required under such loads (such as web server response time, database query response times). What kinds of tools will be needed for performance testing (such as web load testing tools, other tools already in house that can be adapted, web robot downloading tools, etc.)? • Who is the target audience? What kind of browsers will they be using? What kind of connection speeds will they by using? Are they intra- organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)? • What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should animations, applets, etc. load and run)? • Will down time for server and content maintenance/upgrades be allowed? how much? • What kinds of security (firewalls, encryptions, passwords, etc.) will be required and what is it expected to do? How can it be tested? • How reliable are the site's Internet connections required to be? And how does that affect backup system or redundant connection requirements and testing? • What processes will be required to manage updates to the web site's content, and what are the requirements for maintaining, tracking, and controlling page content, graphics, links, etc.? • Which HTML specification will be adhered to? How strictly? What variations will be allowed for targeted browsers? • Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site?? • How will internal and external links be validated and updated? how often? • Can testing be done on the production system, or will a separate test system be required? How are browser caching, variations in browser option settings, dial-up connection variabilities, and real-world internet 'traffic congestion' problems to be accounted for in testing? • How extensive or customized are the server logging and reporting requirements; are they considered an integral part of the system and do they require testing? • How are cgi programs, applets, javascripts, ActiveX components, etc. to be maintained, tracked, controlled, and tested? Some sources of site security information include the Usenet newsgroup 'comp.security.announce' and links concerning web site security in the 'Other Resources' section. Some usability guidelines to consider - these are subjective and may or may not apply to a given situation (Note: more information on usability testing issues can be found in articles about web site usability in the 'Other Resources' section): • Pages should be 3-5 screens max unless content is tightly focused on a single topic. If larger, provide internal links within the page. • The page layouts and design elements should be consistent throughout a site, so that it's clear to the user that they're still within a site. • Pages should be as browser-independent as possible, or pages should be provided or generated based on the browser-type. • All pages should have links external to the page; there should be no dead-end pages. • The page owner, revision date, and a link to a contact person or organization should be included on each page. Many new web site test tools have appeared in the recent years and more than 280 of them are listed in the 'Web Test Tools' section.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: How can Software QA processes be implemented without stifling productivity?
Ans : By implementing QA processes slowly over time, using consensus to reach agreement on processes, and adjusting and experimenting as an organization grows and matures, productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection, panics and burn-out will decrease, and there will be improved focus and less wasted effort. At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and reporting, minimize time required in meetings, and promote training as part of the QA process. However, no one - especially talented technical types - likes rules or bureacracy, and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug-fixing and calming of irate customers.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is 'configuration management'?
Ans : Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes. (See the 'Tools' section for web resources with listings of configuration management tools. Also see the Bookstore section's 'Configuration Management' category for useful books with more information.)
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What's a 'test case'?
Ans : • A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results. • Note that the process of developing test cases can help find problems in the requirements or design of an application, since it requires completely thinking through the operation of the application. For this reason, it's useful to prepare test cases early in the development cycle if possible.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What should be done after a bug is found?
Ans : The bug needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should encapsulate these processes. A variety of commercial problem-tracking/management software tools are available (see the 'Tools' section for web resources with listings of such tools). The following are items to consider in the tracking process: • Complete information such that developers can understand the bug, get an idea of it's severity, and reproduce it if necessary. • Bug identifier (number, ID, etc.) • Current bug status (e.g., 'Released for Retest', 'New', etc.) • The application name or identifier and version • The function, module, feature, object, screen, etc. where the bug occurred • Environment specifics, system, platform, relevant hardware specifics • Test case name/number/identifier • One-line bug description • Full bug description • Description of steps needed to reproduce the bug if not covered by a test case or if the developer doesn't have easy access to the test case/test script/test tool • Names and/or descriptions of file/data/messages/etc. used in test • File excerpts/error messages/log file excerpts/screen shots/test tool logs that would be helpful in finding the cause of the problem • Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common) • Was the bug reproducible? • Tester name • Test date • Bug reporting date • Name of developer/group/organization the problem is assigned to • Description of problem cause • Description of fix • Code section/file/module/class/method that was fixed • Date of fix • Application version that contains the fix • Tester responsible for retest • Retest date • Retest results • Regression testing requirements • Tester responsible for regression tests • Regression testing results A reporting or tracking process should enable notification of appropriate personnel at various stages. For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What makes a good QA or Test manager?
Ans : A good QA, test, or QA/Test(combined) manager should: • be familiar with the software development process • be able to maintain enthusiasm of their team and promote a positive atmosphere, despite • what is a somewhat 'negative' process (e.g., looking for or preventing problems) • be able to promote teamwork to increase productivity • be able to promote cooperation between software, test, and QA engineers • have the diplomatic skills needed to promote improvements in QA processes • have the ability to withstand pressures and say 'no' to other managers when quality is insufficient or QA processes are not being adhered to • have people judgement skills for hiring and keeping skilled personnel • be able to communicate with technical and non-technical people, engineers, managers, and customers. • be able to run meetings and keep them focused
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What are the different modes of recording?
Ans : There are two type of recording in WinRunner. Context Sensitive recording records the operations you perform on your application by identifying Graphical User Interface (GUI) objects. Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is the purpose of loading WinRunner Add-Ins?
Ans : Add-Ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those functions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What are the reasons that WinRunner fails to identify an object on the GUI?
Ans : WinRunner fails to identify an object in a GUI due to various reasons. The object is not a standard windows object. If the browser used is not compatible with the WinRunner version, GUI Map Editor will not be able to learn any of the objects displayed in the browser window.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is meant by the logical name of the object?
Ans : An object's logical name is determined by its class. In most cases, the logical name is the label that appears on an object.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: If the object does not have a name then what will be the logical name?
Ans : If the object does not have a name then the logical name could be the attached text.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is the use of Test Director software?
Ans : TestDirector is Mercury Interactive's software test management tool. It helps quality assurance personnel plan and organize the testing process. With TestDirector you can create a database of manual and automated tests, build test cycles, run tests, and report and track defects. You can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Have you integrated your automated scripts from TestDirector?
Ans : When you work with WinRunner, you can choose to save your tests directly to your TestDirector database or while creating a test case in the TestDirector we can specify whether the script in automated or manual. And if it is automated script then TestDirector will build a skeleton for the script that can be later modified into one which could be used to test the AUT.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What are the different modes of recording?
Ans : There are two type of recording in WinRunner. Context Sensitive recording records the operations you perform on your application by identifying Graphical User Interface (GUI) objects. Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: Explain in brief about the QTP Automation Object Model.
Ans : Essentially all configuration and run functionality provided via the Quick Test interface is in some way represented in the Quick Test automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in Quick Test have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the Quick Test automation object model, along with standard programming elements such as loops and conditional statements to design your program.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is Object Spy in QTP?
Ans : Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object's hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What does it mean when a check point is in red color? what do u do?
Ans : A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
Q: What is the Diff between Image check-point and Bit map Check point?
Ans : Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. Quick Test captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space. For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly. You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded). Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
Date submitted :8/8/2009 1:03:38 AM
Submitted by : shabir@myfaithsolution.com
1