Software Testing _FAQs

7/27/2019 Software Testing _FAQs

1/15

1. What is Quality management?

That aspect of the overall management function that determines and implements the qualitypolicy.

2. what is quality control?

The operational techniques and the activities used to fulfill and verify requirements of quality.

3. what is quality audit?

A systematic and independent examination to determine whether quality activities and relatedresults comply with planned arrangements and whether these arrangements are implementedeffectively and are suitable to achieve objectives.

4. what is quality assurance?

All those planned or systematic actions necessary to provide adequate confidence that a productor service is of the type and quality needed and expected by the customer.

5. what is metric?

A standard of measurement. Software metrics are the statistics describing the structure orcontent of a program. A metric should be a real objective measurement of something such asnumber of bugs per lines of code.

6. what is quality circle?

A group of individuals with related interests that meet at regular intervals to consider problems orother matters related to the quality of outputs of a process and to the correction of problems or tothe improvement of quality.

7. what is localisation testing?

This term refers to making software specifically designed for a specific locality.

8. whatis independent testing group?

A group of people whose primary responsibility is software testing.

9. what is gorilla testing ?

Testing one particular module, functionality heavily.

10. what is gray box testing ?

A combination of Black Box and White Box testing methodologies, testing a piece of software

against its specification but using some knowledge of its internal workings.

11. what is functional specification?

A document that describes in detail the characteristics of the product with regard to its intendedfeatures.

12. what is functional decomposition?

A technique used during planning, analysis and design; creates a functional hierarchy for thesoftware.


2/15

13 .what is exhaustive testing?

Testing which covers all combinations of input values and preconditions for an element of thesoftware under test.

14. what is equivalance partitioning?

A test case design technique for a component in which test cases are designed to executerepresentatives from equivalence classes.

15. what is euivalance class?

A portion of a components input or output domains for which the components behavior isassumed to be the same from the components specification.

16. what is endurance testing?

Checks for memory leaks or other problems that may occur with prolonged execution.

17. what is depth testing? A test that exercises a feature of a product in full detail.

18. what is dependency testing ?

Examines an applications requirements for pre-existing software, initial states and configurationin order to maintain proper functionality.

19. what is defect?

Non conformance to requirements or functional / program specification

20. what is debugging ?

The process of finding and removing the causes of software failures.

21. what is datadriven testing?

Testing in which the action of a test case is parameterized by externally defined data values,maintained as a file or spreadsheet. A common technique in Automated Testing.

22. what is data flow diagram?

A modeling notation that represents a functional decomposition of a system.

23. what is cyclomatic complexity?

A measure of the logical complexity of an algorithm, used in white-box testing.

24. what is conversion testing?

Testing of programs or procedures used to convert data from existing systems for use inreplacement systems.

25. what is context driven testing?

The context-driven school of software testing is flavor of Agile Testing that advocates continuousand creative evaluation of testing opportunities in light of the potential information revealed andthe value of that information to the organization right now.


3/15

26.what is conformance testing ?

The process of testing that an implementation conforms to the specification on which it is based.Usually applied to testing conformance to a formal standard.

27. what is concurrency testing ?

Multi-user testing geared towards determining the effects of accessing the same application code,module or database records. Identifies and measures the level of locking, deadlocking and use ofsingle-threaded code and locking semaphores.

28. what is code coverage?

An analysis method that determines which parts of the software have been executed (covered)by the test case suite and which parts have not been executed and therefore may requireadditional attention.

29.what is code complete?

Phase of development where functionality is implemented in entirety; bug fixes are all that areleft. All functions found in the Functional Specifications have been implemented.

30. what is cause effect graph?

Graphical representation of inputs and the associated outputs effects which can be used todesign test cases.

31. what is capture or relay tool?

A test tool that records test input as it is sent to the software under test. The input cases storedcan then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

32. what is breadth testing?

A test suite that exercises the full functionality of a product but does not test features in detail.

33. what is branch testing ?

Testing in which all branches in the program source code are tested at least once.

34. what is boundary value analysis?

BVA is similar to Equivalence Partitioning but focuses on corner cases or values that areusually out of range as defined by the specification. his means that if a function expects all valuesin range of negative 100 to positive 1000, test inputs would include negative 101 and positive1001.

35. what is boundary testing?

Test which focus on the boundary or limit conditions of the software being tested. (Some of thesetests are stress tests).

36. Binary portability testing?

Testing an executable application for portability across system platforms and environments,usually for conformation to an ABI specification.


4/15

37. what is baseline?

The point at which some deliverable produced during the software engineering process is putunder formal change control.

38. basic path testing?

A white box test case design technique that uses the algorithmic flow of the program to designtests.

39. what is automated testing?

Testing employing software tools which execute tests without manual intervention. Can beapplied in GUI, performance, API, etc. testing.

The use of software to control the execution of tests, the comparison of actual outcomes topredicted outcomes, the setting up of test preconditions, and other test control and test reportingfunctions.

40. what is diff b/w smoke and sanity testing?

Smoke Testing is non-exhaustive software testing, ascertaining that the most crucial functions ofa program work, but not bothering with finer details.

Sanity Testing is a cursory testing,it is performed whenever a cursory testing is sufficient toprove the application is functioning according to specifications. This level of testing is a subset ofregression testing. It normally includes a set of core tests of basic GUI functionality todemonstrate connectivity to the database, application servers, printers, etc.

41. what is agile testing?

Testing practice for projects using agile methodologies, treating development as the customer oftesting and emphasizing a test-first design paradigm.

42. what is ad hoc testing?

A testing phase where the tester tries to break the system by randomly trying the systemsfunctionality. Can include negative testing as well.

43. what is scenario?

A scenario defines the events that occur during each testing session. For example, a scenariodefines and controls the number of users to emulate, the actions to be performed, and themachines on which the virtual users run their emulations.

44. what is the diff b/w QC and QA?

Quality assurance is the process where the documents for the product to be tested is verifiedwith actual requirements of the customers. It includes inspection, auditing , code review , meetingetc.

Quality control is the process where the product is actually executed and the expected behavior isverified by comparing with the actual behavior of the software under test. All the testing types likeblack box testing, white box testing comes under quality control.Quality assurance is done beforequality control.

45. what is the diff b/w manual and automation testing?

This answer is quite simple, Manual is when user needs to do many things based on the testcase specified, say like click some tab and check if the tab is working fine or click on a particular

URL and check if the web site specified opens.


5/15

The above stuff can also be done automatically, i.e. through some automated tools likeWinrunner , Silk Test etc the things can be automated , so user just has to trigger the tool and thetool will take care of executing , only thing needed is we need to know how to make the testcasesautomated through that tool which is not very difficult.

46. what is L10 Testing?

L10 Testing is Localization Testing, it verifies whether your products are ready for local marketsor not.

47.what is I18N Testing?

I18N Testing is Internationalization testing

Determine whether your developed products support for international character encodingmethods is sufficient and whether your product development methodologies take into accountinternational coding standards.

48. what makes a good software engineer?

A good test engineer has a test to break attitude, an ability to take the point of view of thecustomer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful inmaintaining a cooperative relationship with developers, and an ability to communicate with both

technical (developers) and non-technical (customers, management) people is useful. Previoussoftware development experience can be helpful as it provides a deeper understanding of thesoftware development process, gives the tester an appreciation for the developers point of view,and reduce the learning curve in automated test tool programming. Judgement skills are neededto assess high-risk areas of an application on which to focus testing efforts when time is limited

49. how do you perform integration testing?

First, unit testing has to be completed. Upon completion of unit testing, integration testing begins.Integration testing is black box testing. The purpose of integration testing is to ensure distinctcomponents of the application still work in accordance to customer requirements. Test cases aredeveloped with the express purpose of exercising the interfaces between the components. Thisactivity is carried out by the test team.

Integration testing is considered complete, when actual results and expected results are either inline or differences are explainable/acceptable based on client input

5O. what is quality assurance?

Software QA involves the entire software development PROCESS - monitoring and improving theprocess, making sure that any agreed-upon standards and procedures are followed, and ensuringthat problems are found and dealt with. It is oriented to prevention.

51. what is documentation change management?

Documentation change management is part of configuration management (CM). CM covers thetools and processes used to control, coordinate and track code, requirements, documentation,problems, change requests, designs, tools, compilers, libraries, patches, changes made to themand who makes the changes

52. what is the role of documentation on QA?

Documentation plays a critical role in QA. QA practices should be documented, so that they arerepeatable. Specifications, designs, business rules, inspection reports, configurations, codechanges, test plans, test cases, bug reports, user manuals should all be documented. Ideally,there should be a system for easily finding and obtaining of documents and determining whatdocument will have a particular piece of information. Use documentation change management, ifpossible


6/15

53. what is SEI,CMM,CMMI,ISO,IEEE and ANSI?

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, now called the CMMI (Capability Maturity Model Integration),developed by the SEI. Its a model of 5 levels of process maturity that determine effectiveness indelivering quality software. It is geared to large organizations such as large U.S. DefenseDepartment contractors. However, many of the QA processes involved are appropriate to anyorganization, and if reasonably applied can be helpful. Organizations can receive CMMI ratingsby undergoing assessments by qualified auditors.

Level 1 - characterized by chaos, periodic panics, and heroic efforts required by individuals tosuccessfully complete projects. Few if any processes in place; successes may not be repeatable.

Level 2 - software project tracking, requirements management, realistic planning, andconfiguration management processes are in place; successful practices can be repeated.

Level 3 - standard software development and maintenance processes are integrated throughoutan organization; a Software Engineering Process Group is is in place to oversee softwareprocesses, and training programs are used to ensure understanding and compliance.

Level 4 - metrics are used to track productivity, processes, and products. Project performance ispredictable, and quality is consistently high.

Level 5 - the focus is on continouous process improvement. The impact of new processes andtechnologies can be predicted and effectively implemented when required.

ISO = International Organisation for Standardization - The ISO 9001:2000 standard (whichreplaces the previous standard of 1994) concerns quality systems that are assessed by outsideauditors, and it applies to many kinds of production and manufacturing organizations, not justsoftware. It covers documentation, design, development, production, testing, installation,servicing, and other processes. The full set of standards consists of: (a)Q9001-2000 - QualityManagement Systems: Requirements; (b)Q9000-2000 - Quality Management Systems:Fundamentals and Vocabulary; (c)Q9004-2000 - Quality Management Systems: Guidelines forPerformance Improvements.

To be ISO 9001 certified, a third-party auditor assesses an organization, and certification istypically good for about 3 years, after which a complete reassessment is required. Note that ISOcertification does not necessarily indicate quality products - it indicates only that documentedprocesses are followed.

IEEE = Institute of Electrical and Electronics Engineers - among other things, creates standardssuch as IEEE Standard for Software Test Documentation (IEEE/ANSI Standard 829), IEEEStandard of Software Unit Testing (IEEE/ANSI Standard 1008), IEEE Standard for SoftwareQuality Assurance Plans (IEEE/ANSI Standard 730) etc

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 (AmericanSociety for Quality).

Other software development/IT management process assessment methods besides CMMI andISO 9000 include SPICE, Trillium, TickIT, Bootstrap, ITIL, MOF, and CobiT.

54. what is clear box testing?

Clear box testing is the same as white box testing. It is a testing approach that examines theapplications program structure, and derives test cases from the applications program logic.

55..what is closed box testing?

Closed box testing is same as black box testing. Black box testing a type of testing that considers

only externally visible behavior. Black box testing considers neither the code itself, nor the innerworkings of the software.


7/15

56..what is open box testing?

Open box testing is same as white box testing. It is a testing approach that examines theapplications program structure, and derives test cases from the applications program logic.

57. what is security testing ?

Application vulnerabilities leave your system open to attacks, Downtime, Data theft, Datacorruption and application Defacement. Security within an application or web service is crucial toavoid such vulnerabilities and new threats.While automated tools can help to eliminate manygeneric security issues, the detection of application vulnerabilities requires independentevaluation of your specific applications features and functions by experts. An external securityvulnerability review by Third Eye Testing will give you the best possible confidence that yourapplication is as secure as possible.

58. what is stress testing?

Stress Testing is a form of testing that is used to determine the stability of a given system orentity. It involves testing beyond normal operational capacity, often to a breaking point, in order toobserve the results. For example, a web server may be stress tested using scripts, bots, andvarious denial of service tools to observe the performance of a web site during peak loads. Stresstesting a subset of load testing. Also see testing, software testing, performance testing.

59. what is compatibility testing?

One of the challenges of software development is ensuring that the application works properly onthe different platforms and operating systems on the market and also with the applications anddevices in its environment.Compatibility testing service aims at locating application problems byrunning them in real environments, thus ensuring you that your application is compatible withvarious hardware, operating system and browser versions.

60. what is capture play back tool?

A test tool that records test input as it is sent to the software under test. The input cases storedcan then be used to reproduce the test at a later time.

61. what is acceptance testing?

User acceptance testing (UAT) is one of the final stages of a software project and will often occurbefore the customer accepts a new system.Users of the system will perform these tests which,ideally, developers have derived from the User Requirements Specification, to which the systemshould conform.Test designers will draw up a formal test plan and devise a range of severitylevels. The focus in this type of testing is less on simple problems (spelling mistakes, cosmeticproblems) and show stoppers (major problems like the software crashing, software will not runetc.). Developers should have worked out these issues during unit testing and integration testing.Rather, the focus is on a final verification of the required business function and flow of thesystem. The test scripts will emulate real world usage of the system. The idea is that if thesoftware works as intended and without issues during a simulation of normal use, it will work justthe same in production.Results of these tests will allow both the customers and the developers tobe confident that the system will work as intended.

62. what is compatibility testing?

One of the challenges of software development is ensuring that the application works properly onthe different platforms and operating systems on the market and also with the applications anddevices in its environment.Compatibility testing service aims at locating application problems byrunning them in real environments, thus ensuring you that your application is compatible withvarious hardware, operating system and browser versions.

63. what is fuzz testing?

Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a programto a source of random data. If the program fails (for example, by crashing, or by failing in-built


8/15

code assertions), then there are defects to correct. The great advantage of fuzz testing is that thetest design is extremely simple, and free of preconceptions about system behavior.

64. what is top down testing?

An approach to integration testing where the component at the top of the component hierarchyis tested first, with lower level components being simulated by stubs. Tested components arethen used to test lower level components. The process is repeated until the lowest levelcomponents have been tested.

65. what is bottom up testing?

An approach to integration testing where the lowest level components are tested first, then usedto facilitate the testing of higher level components. The process is repeated until the componentat the top of the hierarchy is tested.

66.what is LCSAJ?

LCSAJ: A Linear Code Sequence And Jump, consisting of the following three items(conventionally identified by line numbers in a source code listing): the start of the linearsequence of executable statements, the end of the linear sequence, and the target line to whichcontrol flow is transferred at the end of the linear sequence.

65. what is big bang testing?

Integration testing where no incremental testing takes place prior to all the systems componentsbeing combined to form the system.

66..what is effort variance?

Effort variance = (Actual effort - Planned Effort)/Planned effort * 100

67. how do we calculate schedule vaiance?

Schedule variance = (Actual time taken - Planned time) / Planned time * 100

68. what is general testing process?

The general testing process is the creation of a test strategy (which sometimes includes thecreation of test cases), creation of a test plan/design (which usually includes test cases and testprocedures) and the execution of tests.

69. How do you create test strategy?

The test strategy is a formal description of how a software product will be tested. A test strategy isdeveloped for all levels of testing, as required. The test team analyzes the requirements, writesthe test strategy and reviews the plan with the project team. The test plan may include test cases,conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.

Inputs for this process:

A description of the required hardware and software components, including test tools. Thisinformation comes from the test environment, including test tool data.

A description of roles and responsibilities of the resources required for the test and scheduleconstraints. This information comes from man-hours and schedules.

Testing methodology. This is based on known standards.

Functional and technical requirements of the application. This information comes from

requirements, change request, technical and functional design documents.


9/15

Requirements that the system can not provide, e.g. system limitations.Outputs for this process:

An approved and signed off test strategy document, test plan, including test cases.

Testing issues requiring resolution. Usually this requires additional negotiation at the projectmanagement level.

70. How do you create a test plan /design?

Test scenarios and/or cases are prepared by reviewing functional requirements of the releaseand preparing logical groups of functions that can be further broken into test procedures. Testprocedures define test conditions, data to be used for testing and expected results, includingdatabase updates, file outputs, report results. Generally speaking

Test cases and scenarios are designed to represent both typical and unusual situations thatmay occur in the application.

Test engineers define unit test requirements and unit test cases. Test engineers also executeunit test cases.

It is the test team who, with assistance of developers and clients, develops test cases andscenarios for integration and system testing.

Test scenarios are executed through the use of test procedures or scripts.

Test procedures or scripts define a series of steps necessary to perform one or more testscenarios.

Test procedures or scripts include the specific data that will be used for testing the process ortransaction.

Test procedures or scripts may cover multiple test scenarios.

Test scripts are mapped back to the requirements and traceability matrices are used to ensure

each test is within scope.

Test data is captured and base lined, prior to testing. This data serves as the foundation forunit and system testing and used to exercise system functionality in a controlled environment.

Some output data is also base-lined for future comparison. Base-lined data is used to supportfuture application maintenance via regression testing.

A pre-test meeting is held to assess the readiness of the application and the environment anddata to be tested. A test readiness document is created to indicate the status of the entrancecriteria of the release.

Inputs for this process:

Approved Test Strategy Document.

Test tools, or automated test tools, if applicable.

Previously developed scripts, if applicable.

Test documentation problems uncovered as a result of testing.

A good understanding of software complexity and module path coverage, derived fromgeneral and detailed design documents, e.g. software design document, source code andsoftware complexity data.


10/15

Outputs for this process:

Approved documents of test scenarios, test cases, test conditions and test data.

Reports of software design issues, given to software developers for correction.

71. what is test methodologies?

One software testing methodology is a three step process of

Creating a test strategy;

Creating a test plan/design; and Executing tests.

This methodology can be used and molded to your organizations needs.

72. what is technical analyst?

Technical Analysts perform test assessments and validate system/functional test requirements.Depending on the project, one person may wear more than one hat. For instance, Test Engineersmay also wear the hat of a Technical Analyst.

73. what is test cinformation manager?

Test Configuration Managers maintain test environments, scripts, software and test data.Depending on the project, one person may wear more than one hat. For instance, Test Engineersmay also wear the hat of a Test Configuration Manager.

74. what is database administrastor?

Database Administrators, Test Build Managers, and System Administrators deliver currentsoftware versions to the test environment, install the applications software and apply softwarepatches, to both the application and the operating system, set-up, maintain and back up testenvironment hardware. Depending on the project, one person may wear more than one hat. Forinstance, a Test Engineer may also wear the hat of a Database Administrator

75. what is system administrator?

Test Build Managers, System Administrators, Database Administrators deliver current softwareversions to the test environment, install the applications software and apply software patches, toboth the application and the operating system, set-up, maintain and back up test environmenthardware. Depending on the project, one person may wear more than one hat. For instance, aTest Engineer may also wear the hat of a System Administrator.

76. what is test build manager?

Test Build Managers deliver current software versions to the test environment, install theapplications software and apply software patches, to both the application and the operatingsystem, set-up, maintain and back up test environment hardware. Depending on the project, oneperson may wear more than one hat. For instance, a Test Engineer may also wear the hat of aTest Build Manager.

77. what testing roles are standard on most testing project?

Depending on the organization, the following roles are more or less standard on most testingprojects: Testers, Test Engineers, Test/QA Team Lead, Test/QA Manager, System Administrator,Database Administrator, Technical Analyst, Test Build Manager and Test Configuration Manager.Depending on the project, one person may wear more than one hat. For instance, Test Engineersmay also wear the hat of Technical Analyst, Test Build Manager and Test Configuration Manager.


11/15

78. what is test engineer? A Test Engineer is an engineer who specializes in testing. Testengineers create test cases, procedures, scripts and generate data. They execute testprocedures and scripts, analyze standards of measurements, evaluate results ofsystem/integration/regression testing. They also

Speed up the work of your development staff;

Reduce your risk of legal liability;

Give you the evidence that your software is correct and operates properly;

Improve problem tracking and reporting;

Maximize the value of your software;

Maximize the value of the devices that use it;

Assure the successful launch of your product by discovering bugs and design flaws, beforeusers get discouraged, before shareholders loose their cool and before employees get boggeddown;

Help the work of your development staff, so the development team can devote its time to buildup your product;

Promote continual improvement;

Provide documentation required by FDA, FAA, other regulatory agencies and your customers;

Save money by discovering defects early in the design process, before failures occur inproduction, or in the field;

Save the reputation of your company by discovering bugs and design flaws; before bugs anddesign flaws damage the reputation of your company.

79.what is test /QA team lead?

The Test/QA Team Lead coordinates the testing activity, communicates testing status tomanagement and manages the test team

80. what is acceptance testing?

Acceptance testing is black box testing that gives the client/customer/project manager theopportunity to verify the system functionality and usability prior to the system being released toproduction. The acceptance test is the responsibility of the client/customer or project manager,however, it is conducted with the full support of the project team. The test team also works withthe client/customer/project manager to develop the acceptance criteria.

81. what is comparison testing?

Comparison testing is testing that compares software weaknesses and strengths to those ofcompetitors products.

82. what is recovery /error testing?

Recovery/error testing is testing how well a system recovers from crashes, hardware failures, orother catastrophic problems.


12/15

83. what is security/penetration testing?

Security/penetration testing is testing how well the system is protected against unauthorizedinternal or external access, or willful damage. This type of testing usually requires sophisticatedtesting techniques.

84. what is installation testing?

Installation testing is the testing of a full, partial, or upgrade install/uninstall process. Theinstallation test is conducted with the objective of demonstrating production readiness. This testincludes the inventory of configuration items, performed by the applications System

Administration, the evaluation of data readiness, and dynamic tests focused on basic systemfunctionality. Following installation testing, a sanity test is performed when necessary.

85. what is load testing?

Load testing is testing an application under heavy loads, such as the testing of a web site undera range of loads to determine at what point the system response time will degrade or fail.

86. what is performance testing?

Performance testing verifies loads, volumes and response times, as defined by requirements.Although performance testing is a part of system testing, it can be regarded as a distinct level of

testing.

87. what is sasity testing?

Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to provethe application is functioning according to specifications. This level of testing is a subset ofregression testing. It normally includes a set of core tests of basic GUI functionality todemonstrate connectivity to the database, application servers, printers, etc.

88. what is end to end testing?

End-to-end testing is similar to system testing, the *macro* end of the test scale; it is the testing a

complete application in a situation that mimics real life use, such as interacting with a database,using network communication, or interacting with other hardware, application, or system.

89. what is regression testing ?

The objective of regression testing is to ensure the software remains intact. A baseline set ofdata and scripts is maintained and executed to verify that changes introduced during the releasehave not undone any previous code. Expected results from the baseline are compared to resultsof the software under test. All discrepancies are highlighted and accounted for, before testingproceeds to the next level.

90. what is system testing?

System testing is black box testing, performed by the Test Team, and at the start of the systemtesting the complete system is configured in a controlled environment. The purpose of systemtesting is to validate an applications accuracy and completeness in performing the functions asdesigned. System testing simulates real life scenarios that occur in a simulated real life testenvironment and test all functions of the system that are required in real life. System testing isdeemed complete when actual results and expected results are either in line or differences areexplainable or acceptable, based on client input.Upon completion of integration testing, system testing is started. Before system testing, all unitand integration test results are reviewed by SWQA to ensure all problems have been resolved.For a higher level of testing it is important to understand unresolved problems that originate atunit and integration test levels.

91. what is integration testing?


13/15

Upon completion of unit testing, integration testing begins. Integration testing is black box testing.The purpose of integration testing is to ensure distinct components of the application still work inaccordance to customer requirements. Test cases are developed with the express purpose ofexercising the interfaces between the components. This activity is carried out by the test team.Integration testing is considered complete, when actual results and expected results are either inline or differences are explainable/acceptable based on client input.

92. what is usability testing ?

Usability testing is testing for user-friendliness. Clearly this is subjective and depends on thetargeted end-user or customer. User interviews, surveys, video recording of user sessions and

other techniques can be used. Test engineers are needed, because programmers anddevelopers are usually not appropriate as usability testers

93. what is functional testing?

Functional testing is black-box type of testing geared to functional requirements of an application.Test engineers should perform functional testing.

94. what is parallel/audit testing?

Parallel/audit testing is testing where the user reconciles the output of the new system to theoutput of the current system to verify the new system performs the operations correctly.

95. what is incremental integration testing?

Incremental integration testing is continuous testing of an application as new functionality isrecommended. This may require that various aspects of an applications functionality areindependent enough to work separately, before all parts of the program are completed, or thattest drivers are developed as needed. This type of testing may be performed by programmers,software engineers, or test engineers.

96. what is unit testing?

Unit testing is the first level of dynamic testing and is first the responsibility of developers andthen that of the test engineers. Unit testing is performed after the expected test results are met ordifferences are explainable/acceptable.

97.what is white bix testing?

White box testing is based on knowledge of the internal logic of an applications code. Tests arebased on coverage of code statements, branches, paths and conditions.

98. what is black box testing?

Black box testing is functional testing, not based on any knowledge of internal software design or

code. Black box testing is based on requirements and functionality.

99. what is good code?

A good code is code that works, is free of bugs and is readable and maintainable. Organizationsusually have coding standards all developers should adhere to, but every programmer andsoftware engineer has different ideas about what is best and what are too many or too few rules.We need to keep in mind that excessive use of rules can stifle both productivity and creativity.Peer reviews and code analysis tools can be used to check for problems and enforce standards.

100. what is configuration management?

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


14/15

101. what is an inspection?

An inspection is a formal meeting, more formalized than a walk-through and typically consists of3-10 people including a moderator, reader (the author of whatever is being reviewed) and arecorder (to make notes in the document). The subject of the inspection is typically a document,such as a requirements document or a test plan. The purpose of an inspection is to find problemsand see what is missing, not to fix anything. The result of the meeting should be documented in awritten report. Attendees should prepare for this type of meeting by reading through thedocument, before the meeting starts; most problems are found during this preparation.

Preparation for inspections is difficult, but is one of the most cost-effective methods of ensuringquality, since bug prevention is more cost effective than bug detection.

102. What is validation?

Validation ensures that functionality, as defined in requirements, is the intended behavior of theproduct; validation typically involves actual testing and takes place after verifications arecompleted

103. what is verification?

Verification ensures the product is designed to deliver all functionality to the customer; it

typically involves reviews and meetings to evaluate documents, plans, code, requirementsand specifications; this can be done with checklists, issues lists, walkthroughs and inspectionmeetings.

104. How is testing affected by object oriented programming?

Well-engineered object-oriented design can make it easier to trace from code to internal designto functional design to requirements.

While there will be little affect on black box testing (where an understanding of the internal designof the application is unnecessary), white-box testing can be oriented to the applications objects. Ifthe application was well-designed this can simplify test design.

104. How can it be known when to stop testing?

This can be difficult to determine. Many modern software applications are so complex, andrun in such an interdependent environment, that complete testing can never be done.Common factors in deciding when to stop are: Deadlines (release deadlines, testing deadlines, etc.)

Test cases completed with certain percentage passed

Test budget depleted

Coverage of code/functionality/requirements reaches a specified point

Bug rate falls below a certain level

Beta or alpha testing period ends

106. What is test case?

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.


15/15

Note that the process of developing test cases can help find problems in the requirements ordesign of an application, since it requires completely thinking through the operation of theapplication. For this reason, its useful to prepare test cases early in the development cycle ifpossible.

107. What is diff b/w gui map and gui map file?

The GUI map is actually the sum of one or more GUI map files. There are two modes fororganizing GUI map files. Global GUI Map file: a single GUI Map file for the entire application.GUI Map File per Test: Winrunner automatically creates a GUI Map file for each test created.

GUI Map file is a file which contains the windows and the objects learned by the Winrunner withits logical name and their physical description.

108. If the object does not have the name then what will be the logical name?

If the object does not have a name then the logical name could be the attached text.

109. What are the reason that Winrunner fail to identify an object in the gui?

Winrunner fails to identify an object in a GUI due to various reasons. The object is not a standardwindows object. If the browser used is not compatible with the Winrunner version, GUI Map Editorwill not be able to learn any of the objects displayed in the browser window.

110. What is the use of test detector software?

TestDirector is Mercury Interactive software test management tool. It helps quality assurancepersonnel plan and organize the testing process. With TestDirector you can create a database ofmanual and automated tests, build test cycles, run tests, and report and track defects. You canalso create reports and graphs to help review the progress of planning tests, running tests, andtracking defects before a software release.

111. Explain Winrunner testing process?

Winrunner testing process involves six main stages

1. Create GUI Map File so that Winrunner can recognize the GUI objects in the application beingtested

2. Create test scripts by recording, programming, or a combination of both. While recording tests,insert checkpoints where you want to check the response of the application being tested.

3. Debug Test: run tests in Debug mode to make sure they run smoothly

4. Run Tests: run tests in Verify mode to test your application.

5. View Results: determines the success or failure of the tests.

6. Report Defects: If a test run fails due to a defect in the application being tested, you can reportinformation about the defect directly from the Test Results window.

Software Testing _FAQs

Documents

Transcript of Software Testing _FAQs