Q.1 Quality principles of Total Quality Management(TQM)? Q.6 Ellaborate different view on quality 1) Customer- Based definition of Q.

er- Based definition of Q.12 State and explain any 5 principles of software testing. Ans: Following
- i. Develop Constancy of purpose of definition and deployment of various Quality- Quality product must have “Fitness for use” and mu st meet are the principles of software testing: - • Define the expected output or result
initiatives. ii. Adapting to new philosophy of managing people/stakeholders customer needs, expectations and help in achieving customer satisfactions for each tests case executed, to understand if expected and actual output
by building confidence and relationships.-> Management must adapt to the and possibly customer delight. Any product can be considered as quality matches or not. • Developers should not test their own programs.
new philosophies of doing work and getting work done from its people and products if it satisfies its purpose of existence. 2) Manufacturing- Based Development teams must not test their own products. Blindfolds cannot be
suppliers. iii. Declare freedom from mass inspection of incoming/produced definition of Quality-This definition is mainly derived from engineering removed in self testing. • Inspect the results of each test completely and
output.-> There must be an approach for elimination of mass inspection product manufacturing where it is not expected that the customer knows all carefully. It would help in root cause analysis and can be used to find weak
followed by cost of failure as the way to achieve quality of products because the requirements of the product, and many product requirements are
processes. • Include test cases for invalid or unexpected conditions which are
mass inspection results into huge cost overrun and product produced is of defined by architects and designers on the basis of customer feasible during production. Testers needs to protect the users from any
inferior quality. iv. Stop awarding of lowest price tag contracts to suppliers. feedback/survey. Market research may have to generate requirement unreasonable failure so that one can ensure that the system works properly.
v. Improve every process used for development and testing of products. vi. statement on the basis of perception of probable customers about what
• Test the program to see if it does what it is not supposed to do as well as
Institutionalize training across the organization for all people. vii. features and characteristics of a product are expected by the market. This
Institutionalize leadership throughout organization at each level. viii. Drive approach gives the definition of “Conformance to requirements”. 3) Product- what it I supposed to do. • Avoid disposable test cases unless the program
out fear of failure from employees. ix. Break down barriers between Based definition of Quality- The product must have something that other itself is disposable. Reusability of test case is important for regression. • Do
functions/departments. x. Eliminate exhortations by numbers, goals, similar products do not have. These attributes must add value for the not plan tests assuming that no errors will be found. There must be targeted
targets. xi. Eliminate arbitrary numerical targets which are not supported by customer/user so that they can appreciate the product in comparison to number of defects for testing. • The probability of locating more errors in
processes. xii. Permit pride of workmanship for employees.-> People must competing products. The product must be distinguishable from similar any one module is directly proportional to the number of errors already
feel proud of the work that they are doing, and know how they are products in the market. 4) Value- Based definition of Quality- A product is found in that module. • Initiate actions for correction, corrective action and
contributing to organizational level. This means replacing ‘management by the best combination of price and features or attributes expected by or preventive actions.
objective’ to ‘management by fact’ xiii. Encourage education of new skills required by the customers. The customer must get value for his investment Q.13 relationship between error,defect and failure - Error is a human action
and techniques. Ms. Snehal Tandale Page 4 xiv. Top management by buying the product. The cost of the product has direct relationship with that produces an incorrect result. It is deviation from actual and expected
commitment and action to improve continually. the value that the customer finds in it. More value for the customer helps in value. The mistakes made by programmer is known as an ‘Error’. This could
Q.2 Explain the structure of quality management system ANS: 1) 1 st Tier better appreciation of a product. Many times it is claimed that “People do happen because of the following reasons: - • Some confusion in
(Quality Policy) Quality policy sets the wish, intent and directions by the not buy products, they buy benefits”. 5) Transcendent Quality- To many understanding the requirement of the software • Some miscalculation of the
management about how activities will be conducted by the organization. 2) users/customers, it is not clear what is meant by a “quality product”, but as values • Or/And Misinterpretation of any value, etc. A Defect is a deviation
2 nd Tier (Quality Objective) Quality objectives are the measurements per their perception it is something good and they want to purchase it from the Requirements. A Software Defect is a condition in a software
established by the management to define progress and achievements in a because of some quality present/absent in the product. 2 product which does not meet a software requirement (as stated in the
numerical way. 3) 3 rd Tier (Quality Manual) Quality manual also termed as Q7. Explain salient features of good testing Ans: Good testing involves requirement specifications) or end-user expectations. In other words, a
policy manual is established and published by the management of the following steps: Capture user requirement Intended requirements defined defect is an error in coding or logic that causes a program to malfunction or
organization. Following are the tiers: - 1) Quality processes/ Quality by the users or customer and the implied requirements are to be analyzed to produce incorrect/unexpected result. This could be hardware, software,
procedures/ Work Instructions They are defined at an organization level by and documented by testers so that they write the test scenario and test network, performance, format, or functionality. Failure is a deviation of the
the functional area experts, and at project and function level by the experts cases for these requirements. Capturing user needs User needs includes software from its intended purpose. It is the inability of a system or a
in those areas separately. 2) Guidelines and Standards Ms. Snehal Tandale present, future, process and implied requirements. Elicitation of component to perform its required functions within specified performance
Page 5 They are used by an organization’s project team for achieving quality requirements is to be done by the development organization to understand requirements. Failure occurs when fault executes.
goals for the products and the services delivered to customers. 3) Format and interpret the requirements Design Objective Design objectives state why Q.14 Describe the structure of a testing team. Ans: The common
and templates They are used for tracking a project, function, and particular approach has been selected for building software. Functional organizational structure where both the test group and the development
department information within an organization. requirement, user interface requirement are some of the requirements group report to the manager of the project. In this arrangement, the test
Q.3 How the quality and productivity are related with each other? Ans: mentioned in software design and how can they achieve it. User Interface It group often has its own lead or manager whose interest and attention is
Quality improvement does not talk about product quality only but a process is the way how user interacts with the system. This includes screens, displays focused on the test team and their work. This independence is a great
quality used for making such a product. If the processes of development and and reports generated by the system. User interface should be simple so that advantage when critical decisions are made regarding the software's quality.
testing are good, a bad product will not be manufactured in the first place. the user can understand what he is supposed to do and what the system is The test team's voice is equal to the voices of the programmers and other
It will reduce inspection, testing, rework, cost/price. Thus quality must doing Internal structures Internal structures are mainly guided by the groups contributing to the product. The downside, however, is that the
improve productivity by reducing wastage. Following shows how quality and software designs or standards used for designing and development. It also project manager is making the final decision on quality. This may be fine, and
productivity are related to each other:- 1) Improvement in quality directly talks about reusability Execution of gray box testing of code Testing ensures in many industries and types of software, it's perfectly acceptable. In the
leads to improved productivity. 2) The hidden factory producing scrap, that it works as intended by customer and is prevented from any probable development of high-risk or mission-critical systems, however, it's
rework, sorting, repair and customer complaint is closed. 3) Quality misuse or risk of failure. Execution can only prove that application module sometimes beneficial to have the voice of quality heard at a higher level.
improvements lead to cost reduction. 4) Employee involvement in quality and program works correctly Q.15 Boundary Value Testing • Boundary testing is the process of testing
improvement. 5) Proper communication between management and Q8. What is test strategy? Explain different stages involve in process of between extreme ends or boundaries between partitions of the input
employee is essential. 6) Employees participate and contribute in developing test strategy.. Ans: A test strategy defines the project's testing values. • So these extreme ends like Start- End, Lower- Upper, Maximum-
improvement process. 7) Employees share responsibility for innovation and objectives and the means to achieve them. The test strategy therefore Minimum, Just Inside-Just Outside values are called boundary values and the
quality improvement. determines testing effort and costs. Selecting an appropriate test strategy is testing is called "boundary testing". • Boundary value analysis is a type of
Q.4 Explain continual (continuous) improvement cycle. Ans: PLAN, DO, one of the most important planning task decisions the test manager has. The black box or specification-based testing technique in which tests are
CHECK, ACT 1)PLAN : An organization must plan for an improvement on the goal is to choose a test approach that optimizes the relation between costs performed using the boundary values. • There are four types of Boundary
basis of its vision and mission definition . Planning includes answering of testing and costs of defects. Steps involved in developing test strategies value testing: a) Normal boundary value Testing. b) Robust boundary value
questions such as who, when, where, how etc about various activities. Select and rank test factors for given application Identify the critical test Testing. c) Worstcase boundary value Testing. d) Robust Worst-case
Quality planning as unit level must be in sync with quality planning at various factors for software product under testing. Test factors are analysed and boundary value Testing. Normal Boundary Value Testing: • In the general
organization level. DO : An organization must work in the direction set by prioritized. The trade of decision must be taken consulting the customer application of Boundary Value Analysis can be done in a uniform manner.
the plan. Actual execution of plan can determine whether the results as Identify system development phases and related test factors The critical The basic form of implementation is to maintain all but one of the variables
expected are achieved or not . Plan sets the tone while execution makes the success factors have varying importance depending upon the developing life at their nominal (normal or average) values and allowing the remaining
plan work. ‘Do’ process needs inputs like resources like hardware, software, cycle phase. The test approach changes according to factors influencing the variable to take on its extreme values. Robust boundary value Testing: •
training CHECK : An organization must compare actual outcome of ‘Do’ stage life cycle phase Identify associated risks with each selected test facto in case Robustness testing can be seen as and extension of Boundary Value Analysis.
with reference or expected result which are planned outcomes. It must be if it is not achieved Customer must do trade offs of test factors and poss The idea behind Robustness testing is to test for clean and dirty test cases. •
done periodically to check of the progress is in right proper direction and Identify phase in which risk if not meeting a test factor need to be addressed In addition to the aforementioned 5 testing values (min, min+, nom, max-,
whether the plan is right or not ACT: If any deviations are observed in actual Q.9 List and explain any two approaches of software testing team with its max) we use two more values for each variable (min-, max+), which are
outcomes with respect to planned results. The organization must decide advantages and disadvantages. Ans: Following approaches of software designed to fall just outside of the input range. Worst-case boundary value
actions to correct the situation. One may need to implement corrective and testing • Independent testing team An organization may create a separate Testing: • Boundary Value analysis uses the critical fault assumption and
preventive actions as per the outcome of ‘Check’ testing team with independent responsibility of testing The team would be therefore only tests for a single variable at a time assuming its extreme
Q.5 What is quality? Explain its core component. . Ans: Quality means having people with sufficient knowledge and ability to test the software values. By disregarding this assumption, we are able to test the outcome if
different things to different people at different times, different places and Advantages: Separate test team is supposed to concentrate more on test more than one variable were to assume its extreme value. In an electronic
for different products. It can also be defined as conformance to specification planning, test strategies and approaches There is an independent view about circuit this is called Worst Case Analysis. In Worst-Case testing we use this
and fitness for use. Core Component of Quality Quality is based on Customer the product Disadvantages Separate teams means additional cost for an idea to create test cases. Robust Worst-case boundary value Testing: • If the
Satisfaction • The effect of quality product delivered & used by a customer, organization. Testing teams needs ramping up and knowledge transfer. function under test were to be of the greatest importance we could use a
on his satisfaction and delight is the most important factor in determining Organization needs to keep a check on development and testing team • method named Robust Worst-Case testing which as the name suggests
whether quality has been achieved or not. • It talks about the ability of a Domain expert doing software testing An organization may employ domain draws it attributes from Robust and Worst-Case testing. • Test cases are
product or service to satisfy a customer by fulfilling his/her needs. • experts for doing testing. Domain experts may use their expertise on subject constructed by taking the Cartesian product of the 7-tuple set defined in the
Manufacture must understand the purpose or usage of a product and devise matter for performing such type of testing Advantages: Fitness for use. Robustness testing chapter. Obviously this results in the largest set of test
a quality plan to satisfy the purpose of the product The organisation must Domain may provide facilitation to developers about defects and customer results we have seen so far and requires the most effort to produce.
define Quality parameters before it can be achieved: 1. Define : Defining the expectations. Domain expert understands the scenario faced by actual users Q.16 Equivalence Class Testing: • It is a software test design technique that
product in terms of features, functionalities, attributes & characteristics of a and hence their testing is realistic involves dividing input values into valid and invalid partitions and selecting
product. What should be , could be and must be present in the project 2. Q.10 List and explain different testing skills required by tester. Ans: • Tester representative values from each partition as test data. The use of
Measure: The quantitative measures must be defined as an attribute of must be selected on the basis of available skills and requirements of tools equivalence classes is appropriate in situations like: • When exhaustive
quality of a product. Measurement also gives a gap between what is and its techniques. • If the testers are conversant with a tool, it can help in testing is desired. • When there is a strong need to avoid redundancy. Types
expected by a customer & what is delivered to him when the product is sold. easy entry for a new tool in the organization. Users skills are required for all of equivalence class testing: 1) Weak Normal Equivalence Class Testing. 2)
3. Monitor: There must be a mechanism used by the manufacturer to tools used by the testers. • Programming skills are required when testers Strong Normal Equivalence Class Testing. 3) Weak Robust Equivalence Class
monitor the development, testing and delivering of a product process. 4. have to develop scripts for using the tools for testing. Programming skills are Testing. 4) Strong Robust Equivalence Class Testing. Advantages: •
Control: Control gives the ability to provide desired results & avoid the needed to write scripts in specific language Ms. Seema Vishwakarma Page 8 Equivalence class testing helps reduce the number of test cases without
undesired things going to a customer. 5. Improve: Continuous improvement • System skills are required when application tool needs some configuration compromising the test coverage. • Reduces the overall test execution time
are necessary to maintain ongoing customer satisfaction & overcome the to be made. Good skills related to systems like working with database, as it minimizes the set of test data. Disadvantages: • It does not consider the
possible competitionManagement must lead the organisation through configure and install new tools • Technical skills are needed to understand conditions for boundary value. • The identification of equivalence classes
improvement efforts Management must lead the organization through the prerequisite of tools and testing. Understanding of user manual, design, relies heavily on the expertise of testers
improvement efforts • Management should lead the endeavor of quality requirements are need for usage and troubleshooting Q.17 types of equivalence testing 1. Weak Normal Equivalence Class Testing:
improvement program in the organization by defining vision, mission, Q.11 Explain the lifecycle of software testing. Ans: Except for small programs, In this first type of equivalence class testing, one variable from each
policies, objectives, goals etc. to improve the quality improvement program. systems should not be tested as a single, monolithic unit. Large systems are equivalence class is tested by the team. Moreover, the values are identified
• And the same must be followed by the employees which is called as built out of sub-systems that are built out of modules, which are composed in a systematic manner. Weak normal equivalence class testing is also known
‘cultural change brought in by management’. Continuous process: • It is an of procedures and functions. The testing process should therefore proceed as single fault assumption. 2. Strong Normal Equivalence Class Testing:
older belief that quality can be improved by more inspection, testing and in stages where testing is carried out incrementally in conjunction with Termed as multiple fault assumption, in strong normal equivalence class
rework which leads to the increase in the cost of inspection, segregation, system implementation. The most widely used process consists of five testing the team selects test cases from each element of the Cartesian
failure and reduces the profit margin for manufacturer. • For improving the stages: 1. Unit Testing: Individual components are tested to ensure that they product of the equivalence. This ensures the notion of completeness in
quality and to have a win-win situation for both manufacturer & customer, operate correctly. Each component is tested independently without other testing, as it covers all equivalence classes and offers the team one of each
quality must be produced at the first time and must be improved system components. 2. Module Testing: This involves the testing of possible combinations of inputs. 3. Weak Robust Equivalence Class Testing:
continuously independent components such as procedures and functions. A module Like weak normal equivalence, weak robust testing too tests one variable
Q27. Describe V &V activities during designs. Ans: V & V model Design may encapsulates related components so it can be tested without other system from each equivalence class. However, unlike the former method, it is also
include high level architectural design and low level design or detailed modules. 3. Subsystem Testing: This phase involves testing collections of focused on testing test cases for invalid values. 4. Strong Robust Equivalence
design which are created by architect. Design Verification: Verification of modules which have been integrated into sub-systems. Sub-systems may be Class Testing: Another type of equivalence class testing, strong robust testing
design may be a walkthrough of design document by design experts team independently designed. The most common problems which arise in large produces test cases for all valid and invalid elements of the product of the
members and stakeholders of the project. Project team along with architect software systems are sub-system interface mismatches. The sub-system test equivalence class. However, it is incapable of reducing the redundancy in
may walkthrough the design to find the completeness of the give process should therefore concentrate on the detection of interface errors by testing
component. Specific tools or methodologies like UML are used to create rigorously exercising the interfaces. 4. System Testing: Sub systems are Q.18 Decision table • Decision table testing is a software testing technique
design. Design Validation: Validation of the design can happen at two or integrated to make up the entire system. The testing process is concerned used to test system behavior for different input combinations. • This is a
more stages during software development life cycle. with finding errors that result from unanticipated interactions between sub- systematic approach where the different input combinations and their
systems and system components. It is also concerned with validating that corresponding system behavior (Output) are captured in a tabular form. •
the system meets its functional and non-functional requirements. 5. That is why it is also called as a Cause-Effect table where Cause and effects
Acceptance Testing: This is the final stage in the testing process before the are captured for better test coverage. • A Decision Table is a tabular
system is accepted for operational use. The system is tested with data representation of inputs versus rules/cases/test conditions
supplied by the system procurer rather than simulated test data.
Q19. Explain DD-paths and basis path testing. Ans: DD-path testing • The Q25. Explain the VV model of testing. Ans: The VV-model is an SDLC model Q33. What is performance testing? List different types of performance
best known form of structural testing is based on construct known as where execution of processes happens in a sequential manner in a V-shape. testing. Performance testing is intended to find whether the system meets
decision to decision path • The reason that program graphs play such an It is also known as Verification and Validation model. The VV-Model is an its performance requirements under normal load or normal level o f
important role in structural testing is because it forms the basis of a number extension of the waterfall model and is based on the association of a testing activities. Normal load must be defined by the requirement statement.
of testing methods, including one based on a construct known as decision- phase for each corresponding development stage. • Requirement Analysis Performance criteria must be expressed in numerical terms. Performance
to-decision paths (DD-Paths). • The idea is to use DD-Paths to create a Requirements analysis is critical to the success or failure of a systems or criteria must be measureable in quantitative terms such as time in
condensation graph of a piece of software’s program graph, in which a software project. The requirements should be documented, actionable, ‘milliseconds’. Some of the examples of performance testing are as below: -
number of constructs are collapsed into single nodes known as DD-Paths. • measurable, testable, traceable, related to identified business needs or a) Adding a new record in database must take maximum five milliseconds. It
DD-Paths are chains of nodes in a directed graph that adhere to certain opportunities, and defined to a level of detail sufficient for system design. • means that when the record is added in database, it may take time lesser or
definitions. • Each chain can be broken down into a different type of DD - System Design Software design usually involves problem solving and equal to five milliseconds. b) Searching of a record in a database containing
Path, the result of which ends up as being a graph of DD-Paths. The length planning a software solution. This includes both a lowlevel component and one million records must not take more than one second. One must add one
of a chain corresponds to the number of edges that the chain contains. DD- algorithm activities and a highlevel, architecture design. • Program Design million records in the system, and then use the search criteria to test this. c)
Path is also known as a decision-to-decision path. A DD-path is a sequence Program Design is the process that an organization uses to develop a Sending information of 1MB size across the system with a network of 512
of nodes in a program graph such that: - Case 1: It consists of a single node program. It is most. often an iterative process involving research, KBPS must not take more than one minute.
with indeg = 0. Case 2: It consists of a single node with outdeg = 0. • Case 3: consultation, initial design, testing and. redesign. A program design is the Q.36 What is acceptance testing? Explain different forms of it The focus of
It consists of a single node with indeg ≥ 2 or outdeg ≥ 2. Ms. Snehal Tandale acceptance testing is on the customer's perspective and judgment. The
plan of action that results from that process. • Acceptance testing
Page 12 Case 4: It consists of a single node with indeg = 1 and outdeg = 1. • Acceptance testing is a level of software testing where a system is tested for
acceptance test might be the only test the customer is actually involved in
Case 5: It is a maximal chain of length ≥ 1.Basic Path Testing • The basis is acceptability. The purpose of this test is to evaluate the system’s compliance or which they can understand. Acceptance tests can even be executed within
always define in terms of vector space, which is a set of element as well as with the business requirements and assess whether it is acceptable for lower test levels or distributed over several test levels. Typical forms o f
operations that corresponds to multiplication and addition defined for the acceptance testing include the following: 1. Testing to determine if the
delivery. • Interface testing Janhavi Vadke Interface testing is defined as a
vectors. • The basis of a vector space contains a set of vectors that are contract has been met: If customer specific software was developed, the
software testing type which verifies whether the communication between
independent of one another, and have a spanning property; this means that customer (in cooperation with the vendor) will perform acceptance testing
two different software systems is done correctly. A connection that
everything within the vector space can be expressed in terms of the according to the contract. On the basis of the results of these acceptance
integrates two components is called interface. • Integration testing The
elements within the basis tests the customer considers whether the ordered software system is free of
purpose of this level of testing is to expose faults in the interaction between (major) deficiencies and whether the development contract or the service
Q.20 Explain the concept and significance of cause and effect graphing integrated units. Test drivers and test stubs are used to assist in Integration
technique Ans: • Cause-Effect Graphing is a technique where causes are the defined by the contract has been accomplished. 2. User acceptance testing:
Testing • Coding, code review, unit testing Coding methodology includes a Another aspect concerning acceptance as the last phase of validation is the
input conditions and effects are the results of those input conditions. • The diagrammatic notation for documenting the results of the procedure. It also test for user acceptance. Such a test is especially recommended if the
Cause-Effect graph technique restates the requirements specification in includes an objective set (ideally quantified) of criteria for determining
terms of the logical relationship between the input and output conditions. customer and the user are different individuals. 3. Operational (acceptance)
whether the results of the procedure are of the desired quality. testing: Operational (acceptance) testing assures the acceptanceof the
Since it is logical, it is obvious to use Boolean operators like AND, OR and Q26. Explain V model for software. Ans: V model • Test policy and test system by the system administrators. It may include the testing of
NOT. • Cause-and-effect graphs shows unit inputs on the left side of a strategy for performing verification and validation activities are documented backup/restore cycles, disaster recovery, user management, maintenance
drawing, and using AND, OR, and NOT “gates” to express the flow of data beforehand to avoid any problem in final deliverables • Testing activities are tasks, and checks of security vulnerabilities.
across stages of unit. referred in project plan but they are detailed in quality plan of verification • Q37. Explain GUI testing with its advantages and disadvantages GUI Testing
Q.21 Explain the concept and significance of cause and effect graphing Plan of activities should decide about 5 Ws(What, When, Where, Why and GUI testing is defined as the process of testing the system's Graphical User
technique. Ans: In the early years of computing, the software community Who) and H(How) with respect to people, process, training etc • Activities Interface of the Application Under Test. GUI testing involves checking the
borrowed many ideas from the hardware community. In some cases, this prepared and documented should be analyzed for coverage, relationship screens with the controls like menus, buttons, icons, and all types of bars -
worked well, but in others, the problems of software just did not fit well with with different entities, structure and traceability • Functional test scenario toolbar, menu bar, dialog boxes, and windows, etc. GUI is what the user sees.
established hardware techniques. Cause-and-effect graphing is a good and structured test scenario are developed for design specification. • High A user does not see the source code. The interface is visible to the user.
example of this. Cause-andeffect graphs shows unit inputs on the left side of level and low level design must ensure that requirement are completely Especially the focus is on the design structure, images that they are working
a drawing, and using AND, OR, and NOT “gates” to express the flow of data covered so that software development covers everything • The output of properly or not. Advantages: • Tests the user interface from the users
across stages of a unit. In Cause-and-effect graphs if there is any problem at one phase must match the input criteria of other phase • The test artifacts perspective. • Efficiently reduces the number of risks towards the end of
an output, the path(s) back to the inputs that affected the output can be that developed must be reviewed and updated development life cycle. • Offers developers and testers ease of use and
retraced. Q28. Explain different roles and responsibilities of development group. Ans learning. • Helps validate the compliance of various icons and elements with
Q.22 Explain slice-based testing with an example. Ans: Slice-based testing Manager : The development manager selects the objects to be reviewed and their design specifications. • Increases the reliability and improves quality of
Definition: Given a program P and a set V of variables in P, a slice on the confirms that the base documents, as well as the necessary resources, are the product. Disadvantages • It requires more memory resources, which
variable set V at statement n, written S(V, n), is the set of all statement available. They also choose the participating people. Moderator The leads the system to perform slowly. • The process of testing is time
fragments in P that contribute to the values of variables in V at node n P-use moderator is responsible for: the administrative tasks pertaining to the consuming and may require extra software for running GUIs. • Since the
used in predicate decision C-use used in computation decision O-use used review, planning and preparation, ensuring that the review is conducted in interface of an application changes frequently, the team might have to
for output L-use used for location i-used used for iteration Example: • an orderly manner and meets its objectives, collecting review data, and refactor recorded test script to improve its accuracy. • Limited access or no
S(price, 5) = {5} • S(price, 6) = {5, 6, 8, 9} • S(price, 7) = {5, 6, 8, 9} • S(price, issuing the review report. Author The author is the creator of the document access to the source code makes the process of testing difficult.
8) = {8} • Lines 1 to 4 have no bearing on the value of the variable at line 7 that is the subject of a review. If several people have been involved in the Q.38 What is the need of a Security Testing? Security testing is a special type
(and,for that matter, for no other variable at any point), so they are not creation, one person with lead responsibility should be appointed; this of testing intended to check the level of security and protection offered by
added to the slice. • Line 5 contains a defining node of the variable price that person takes over the role of the author. Reviewer The reviewers, sometimes an application to the users against unfortunate incidences. The incidences
can affect the value at line 7, so 5 is added to the slice. • Line 6 can affect the also called inspectors, are several (usually a maximum of five) technical could be loss of privacy, loss of data, etc. Some definition associated with
value of the variable as it can affect the flow of control of the program. experts that shall check the review object after individual preparation. security are given below: - a) Vulnerability: -The weaker parts of the system
Therefore, 6 is added to the slice. Line 7 is not added to the slice, as it cannot Recorder The recorder (or scribe) shall document the findings (problems, represent the vulnerabilities in the systems. These parts of system are less
affect the value of the variable at line 7 in any way. • Line 8 is added to the action items, decisions, and recommendations) made by the review team. protected. One must take precaution not to expose these weak points to
slice – even though it comes after line 7 in the program listing. This is because The recorder must be able to record in a short and precise way, capturing the outsiders. b) Threats: -Threats represent the possible attacks on the system
of the loop: after the first iteration of the loop, line 8 will be executed before essence of the discussion from outsiders with malicious intentions. Threat is defined as an exploitation
the nex Q29. Discuss different types of reviews in verification. Ans: In-process review of vulnerabilities of the system. c) Perpetrators: -Perpetrators are the
Q.23 Write a note on decision table technique Ans: Decision Table Technique : Review conducted during different phases of software development life entities who are unwelcomed guests in the system. They can create a
• A decision table is a good way to deal with combinations of things (e.g. cycle. The are intended to check whether inputs to the phase are correct or problem in the system by doing something undesirable like loss of data and
inputs). • This technique is sometimes also referred to as a 'cause-effect' not and whether all the applicable process are followed Milestone review : making changes in the system. Perpetrators can be people, other system,
table. If different combinations of inputs result in different actions being It is conducted on periodic basis depending on the completion of a particular viruses, etc. d) Points of penetrations: -The point where the system can be
taken, this can be more difficult to show using equivalence partitioning and phase or a time frame defined or a milestone achieved. These reviews penetrated or where the system is least guarded represents the point of
boundary value analysis, which tend to be more focused on the user confirms that the output from the phase matches with predefined quality penetration. These points represent the vulnerabilities in the system
interface. Advantages • Decision tables can be used in test design whether Phase end review: It is conducted at the end of the development phase Q39. Explain the concept of inter system testing and its Importance. No
or not they are used in specifications, as they help testers explore the effects under review such as requirement phase, design coding and testing. system works alone. There are possibilities that the system developed may
of combinations of different inputs and other software states that must Waterfall cycle is suitable for doing a phase end review where distinction have to interact with many other supporting systems. Testing of interfaces
correctly implement business rules • Helping the developers do a better job between different phases are clearly defined Periodic review: When one between two or more systems is essential to make sure that they work
can also lead to better relationships with them • Decision tables aid the phase ends in reality another phase may have half way through. In such correctly and information is transferred between different systems. System
systematic selection of effective test cases and can have the beneficial side- cases one must review some on periodic basis such as weekly, monthly and testing is designed to determine whether: - a) Parameters and data are
effect of finding problems and ambiguities in the specification. • It is a quarterly. Percent completion review: Percent completion review is a correctly passed between application and other systems. b) Documentation
technique that works well in conjunction with equivalence partitioning combination of periodic review and phase end review where the project for the involved system must be accurate and complete and must be
Q24. Explain different methods of verification. Ans: The different methods of activities or product development activities are assessed on the basis of matching expected inputs and outputs. c) System testing must be conducted
verification are as follow: - Self-Review: - Self review may not be referred as percent completion whenever there is a change in the parameters. d) Representative set of test
an official way of review in most of the software verification descriptions, as Q30. Explain the concept of workbench. Ans: Ms. Seema Vishwakarma Page transactions is prepared in one system and passed on to another system. e)
it assumed that everybody does a self-check before giving work product for 11 The following basic things are required for workbench Input : There must Manual verification of documentation is done to understand the
further verification. Peer Review: - Peer review is the most informal type of be some entry check criteria when inputs are entering the workbench and it relationship between different systems.
review where an author and peer are involved. It is a review done by a peer should match with the output criteria of the earlier work bench Output: Q40. Explain the significance of Usability testing. Usability testing is done to
and review records are maintained. A peer may be a fellow developer or There must be some exit criteria from work bench which should match with check ‘ease of use’ of an application to a common user who will use the
tester as the case may be. There is also a possibility of superior review where input criteria for the next work bench. Output must include review comment application in production environment. It involves using user guides and
peer is a supervisor with better knowledge and experience. Walkthrough: - Verification Process: must describe the step by step activities to be help manuals available with application. It is applied to determine whether:
A walkthrough is conducted by the author of the ‘document under review conducted in each work bench Check Process: Describes how the verification - a) It is simple to understand application usage through look, feel and
who takes the participants through the document and his or her thought process has been checked. Quality plan must describe the objective to be support available like online help. b) It is easy to execute an application
processes, to achieve a common understanding and to gather feedback. This achieved. Standard tools and guideline: There may be tools, coding, process from user interface provided. Usability testing is done by: - a) Direct
is especially useful if people from outside the software discipline are guidelines or standards for verification observation of people using system. b) Conducting usability surveys. c) Beta
present, who are not used to, or cannot easily understand software Q4.31. Explain compatibility testing in details. Compatibility Testing • testing or business pilot of application is user environment. Usability testing
development documents. Ms. Snehal Tandale Page 15 Inspection(Formal Compatibility testing means testing the software on multiple configuration checks for human factor problems such as: - a) Whether outputs from the
review):-It is usually led by a trained moderator (certainly not by the to check the behaviours of different system component and their system such as printouts, reports etc. are meaningful or not. b) Is error
author).The document under inspection is prepared and checked thoroughly combination • The variables can be operating systems, browsers, databases diagnostic straightforward or not? c) Error messaging must help common
by the reviewers before the meeting, comparing the work product with its and languages • The hardware can be machine, server, routers and printers users using the system. d) Does User Interface have conformity to the syntax,
sources and other referenced documents, and using rules and checklists. In • Integration with other communication systems can be mailing software, format, style observations etc? e) Is the application easy to use? f) Is there
the inspection meeting the defects found are logged. Audits: - Audit is a messaging softwares. • Friend compatibility: happens when the application an exit option in all choices so that user can exit the system at any moment?
formal review based on samples. Audits are conducted by auditors who may behaviour on new platform is as if it is working on its base platform. Cost g) System must not annoy intended user h) System taking control from user
or may not be an expert in the given work product. benefit analysis has to be done to determine how much friend compatibility without indicating when it will be returned can be a problem. i) System must
Q.34. What is integration testing? Explain the Big bang approach. Integration is required. • Neutral compatibility: If the application has its own utilities provide online help or user manual. j) Consistent in its function and overall
testing involves integration of units to make a module, then integration of and services and uses them as if nothing has been provided by any platform. design.
modules to make a system. Integration testing may start at module level • Enemy compatibility: if the application is not compatible with targeted Q41. Discuss Bottom up and top down testing with an example. Top Down
where different units and components come together to form a module, and platform then this may be termed as enemy compatibility Testing: • In top-down testing approach, the top level of the application is
go up to system level. It is considered as a Structural testing. Integration Q32 Explain Commercial off-the-shelf software testing. ‘COTS’ stands for tested first and then it goes downward till it reaches the final component of
testing also tests the functionality of software but the main aim o f ‘commercially of the shell’ software. This software is readily available in the the system. All top-level components called by tested components are
integration testing is on the interfaces between different modules and market and user can buy and use them directly. The reason software combined one by one and tested in the process. • Drivers may not be
systems. Integration testing mainly focuses on input/ output protocols, and organizations use COTS is: - • Line of Business: - An organization may not be required as we go downward as earlier phase will act as driver for latter
parameters passing between different units, models and or system. There
in a line of business of making such software which it requires. • Cost-Benefit phase while one may have to design stubs to take care of lower-level
are various approaches of integration testing depending upon how the Analysis: -Sometimes, it is very costly to develop software in-house due to components which are not available at that time. • Top-level components
system is integrated and they are as follow: - a) BottomUp Testing b) Top-
various limitations like knowledge, skills, resources, etc. • Expertise/Domain are the user interfaces which are created first to elicit user requirements or
Down Testing
knowledge: -An organization may have knowledge about how to use the creation of prototype. Agile approaches like prototyping, formal proof of
Q.35. Write a short note on smoke testing. Smoke Testing • Smoke Testing is
software that it needs but it may not have knowledge to build such software concept, and test-driven development use this approach for testing. Bottom
also known as “Build Verification Testing”, is a type of software testing that
inhouse. • Delivery Schedule: COTS are available across the table by paying Up testing • It focuses on testing the bottom part/individual units and
comprises of a non-exhaustive set of tests • It aims at ensuring that the most
a price while developing such software in-house may take a very long time modules, and then goes upward by integrating tested and working units and
important functions work. The result of this testing is used to decide if a
build is stable enough to proceed with further testing. • Installation, and huge efforts. Following are the features of COTS:- • COTS' are developed modules for system testing. • It is a mirror image of the Top-down approach,
with general requirements • Some `COTS' may need changing business with the difference that stubs are replaced by driver modules that emulate
navigation through the application, invoking or accessing some major
units at the next level up in the tree.
functionalities involved in testing. • If smoke testing fails the user will not be processes to suit the `COTS' implementation. • Sometimes COTS may need
able to work with application and it may result into rejection of application configuration of software or system.
• Test manager and senior tester performs smoke testing and the entry
criteria is depended on smoke testing