Various Types of Testing: What are the different Methodologies in Agile Cyclomatic complexity of a code section is the

Black box testing – Internal system design is not Development Model? quantitative measure of the number of linearly
considered in this type of testing. Tests are based on There are currently seven different Agile independent paths in it. It is a software metric used
requirements and functionality. methodologies: to indicate the complexity of a program. It is
White box testing – This testing is based on 1. Extreme Programming (XP) 2. Scrum 3. Lean computed using the Control Flow Graph of the
knowledge of the internal logic of an application’s Software Development4. Feature-Driven program. The nodes in the graph indicate the
code. Also known as Glass box Testing. Internal Development 5. Agile Unified Process 6. Crystal 7. smallest group of commands of a program, and a
software and code working should be known for this Dynamic Systems Development Model (DSDM) directed edge in it connects the two nodes i.e., if
type of testing. Tests are based on coverage of code What is the Structure-based (white-box) testing second command might immediately follow the first
statements, branches, paths, conditions. techniques? command.
Unit testing – Testing of individual software Structure-based testing techniques use the internal McCabe's sof Complexity = E - N + 2P
components or modules. Typically done by the structure of the software to derive test cases. They Where, E = Number of edges in control flow graph
programmer and not by testers, as it requires detailed are commonly called 'white-box' or 'glass box' N = Number of vertices in control flow graph
knowledge of the internal program design and code. techniques since they require knowledge of how the P = Program factor
May require developing test driver modules or test software is implemented, that is, how it works. For Explain some of the quality metric
harnesses. example, a structural technique may be concerned attributes/features.
Integration testing – Testing of integrated modules with exercising loops in the software. Different test A quality metric is a quantitative measurement of the
to verify combined functionality after integration. cases may be derived to exercise the loop once, degree to which an item possesses a given quality
Modules are typically code modules, individual twice, and many times. This may be done regardless attribute.
applications, client and server applications on a of the functionality of the software. Correctness: the degree to which the system
network, etc. This type of testing is especially Why we use decision tables? performs its intended function.
relevant to client/server and distributed systems. A decision table is a good way to deal with Reliability- the degree to which the software is
Functional testing – This type of testing ignores the combinations of things (e.g. inputs). This technique is expected to perform its required functions under
internal parts and focus on the output is as per sometimes also referred to as a 'cause-effect' table. stated conditions for a stated period.
requirement or not. Black-box type testing geared to The reason for this is that there is an associated logic Usability- relates to the degree of effort needed to
functional requirements of an application. diagramming technique called 'cause-effect learn. Operate, prepare input, and interpret output of
System testing – Entire system is tested as per the graphing' which was sometimes used to help derive the software.
requirements. Black-box type testing that is based on the decision table. Integrity-relates to the system's ability to withstand
overall requirements specifications, covers all What is test coverage? both intentional and accidental attacks.
combined parts of a system. Test coverage is defined as a metric in Software Portability-relates to the ability of the software to be
Regression testing – Testing the application as a Testing that measures the amount of testing transferred from one environment to another.
whole for the modification in any module or performed by a set of tests. It will include gathering Maintainability: the effort needed to make changes
functionality. Difficult to cover all the system in information about which parts of a program are in the software.
regression testing so typically automation tools are executed when running the test suite to determine Interoperability: the effort needed to link or couple
used for these testing types. which branches of conditional statements have been one system to another.
Alpha testing – In house virtual user environment taken. Various causes of software errors:
can be created for this type of testing. Testing is done What are Test comparators? 1. Faulty Requirements Definition
at the end of development. Still minor design A test comparator is a tool to automate the process 2. Client-developer communication failures
changes may be made as a result of such testing. of comparison between the actual and expected 3. Deliberate deviations from software requirements
Beta testing – Testing typically done by end-users or results produced by a software product at the time of 4. Logical design errors
others. Final testing before releasing application for software testing. This automation of comparison can 5. Coding errors
commercial purpose. take place during the testing procedure or after the 6. Non-compliance with documentation and coding
Mutation Testing is a type of Software Testing that testing procedure is complete. instructions
is performed to design new software tests and What is exploratory testing? 7. Shortcomings of the Testing Process
evaluate the quality of already existing software tests. Exploratory testing is a hands-on approach in which 8. User Interface and Procedure errors
Mutation testing is related to modification a program testers are involved in minimum planning and 9. Documentation Errors
in small ways. It focuses to help the tester develop maximum test execution. The planning involves the Software Quality:
effective tests or locate weaknesses in the test data creation of a test charter, a short declaration of the Software quality product is defined in term of its
used for the program. scope of a short time-boxed test effort, the objectives fitness of purpose. That is, a quality product does
What is risk-based testing? and possible approaches to be used. The test design precisely what the users want it to do. For software
Risk-based testing is the term used for an approach and test execution activities are performed in parallel products, the fitness of use is generally explained in
to creating a test strategy that is based on prioritizing typically without formally documenting the test terms of satisfaction of the requirements laid down in
tests by risk. The basis of the approach is a detailed conditions, test cases or test scripts. the SRS document.
risk analysis and prioritizing of risks by risk level. Software Testing Tools: Software Engineering:
Tests to address each risk are then specified, starting 1.Selenium 2. TestingWhiz 3.HPE Unified Functional Software engineering is the process of designing,
with the highest risk first. Testing (HP – UFT formerly QTP) 4.TestComplete developing, testing, and maintaining software. It is
Rapid Application Development? 5.Ranorex 6.Sahi 7.Watir 8.Tosca Testsuite 9.Telerik a systematic and disciplined approach to software
Rapid Application Development (RAD) is formally a TestStudio 10.Katalon Studio development that aims to create high-quality,
parallel development of functions and subsequent Selenium: Selenium is a testing framework to reliable, and maintainable software. Software
integration. Components/functions are developed in perform web application testing across various engineering includes a variety of techniques, tools,
parallel as if they were mini projects, the browsers and platforms. Selenium helps the testers and methodologies, including requirements
developments are time-boxed, delivered, and then to write tests in various programming languages. It analysis, design, testing, and maintenance.
assembled into a working prototype. Rapid change offers record and playback features to write tests Software Quality Assurance (SQA): It is simply a
and development of the product is possible using this without learning Selenium IDE. way to assure quality in the software. It is the set of
methodology. TestingWhiz is a test automation tool with the code- activities which ensure processes, procedures as
What is the difference between Testing less scripting by Cygnet Infotech, a CMMi Level 3 IT well as standards are suitable for the project and
Techniques and Testing Tools? solutions provider. TestingWhiz offers various implemented correctly. Software Quality Assurance
Testing technique: – Is a process for ensuring that automated testing solutions like web testing, is a process which works parallel to development of
some aspects of the application system or unit software testing, database testing, API testing, software. It focuses on improving the process of
functions properly there may be few techniques but mobile app testing, regression test suite development of software so that problems can be
many tools. maintenance, optimization, and automation, and prevented before they become a major issue.
Testing Tools: – Is a vehicle for performing a test cross-browser testing. Efficiency: It deals with the hardware resources
process. The tool is a resource to the tester, but itself Watir is an open-source testing tool made up of Ruby needed to perform the different functions of the
is insufficient to conduct testing. libraries to automate web application testing. It is software system. It includes processing capabilities
What is component testing? pronounced as “water.” Watir offers the following (given in MHz), its storage capacity (given in MB or
Component testing, also known as unit, module and features: GB) and the data communication capability (given in
program testing, searches for defects in, and verifies •Tests any language-based web application •Cross- MBPS or GBPS).
the functioning of software (e.g. modules, programs, browser testing •Compatible with business-driven What do you mean by mutation testing?
objects, classes, etc.) that are separately testable. development tools like RSpec, Cucumber, and Mutation testing is an approach to test data
Component testing may be done in isolation from the Test/Unit •Tests web page’s buttons, forms, links, and generation that requires knowledge of code
rest of the system depending on the context of the their responses. structure. It considers the possible faults that could
development life cycle and the system. Control Flow Graph (CFG): occur in a software component as the basis for test
Integrity: This factor deals with the software system It is the graphical representation of control flow or data generation and evaluation of testing
security, that is, to prevent access to unauthorized computation during the execution of programs or effectiveness.
persons, also to distinguish between the group of applications. Control flow graphs are mostly used in
people to be given read as well as write permit. static analysis as well as compiler applications, as
they can accurately represent the flow inside of a
program unit.
Relationship between failure, fault and error McCall’s factor model: McCall’s factor model What are the main issues in the project
Bug, Defect, Error, Fault, Failure classifies all software requirements into 11 software development plan?
We can say that the several issues and quality factors. The 11 factors are grouped into three Setting clear goals and objectives.
inconsistencies found throughout software are linked categories – product operation, product revision and Scope creep.
and dependent on each other. product transition – as follows: Budget restrictions and changes
Software Error: Error is a situation that happens 1 Product Operation: It includes five software What are the main issues in the project’s quality
when the Development team or the developer fails quality factors, which are related with the plan?
to understand a requirement definition and hence requirements that directly affect the operation of the 1. Responsibility of Management. 2. Document
that misunderstanding gets translated to buggy software. Management and Control. 3. Requirements Scope.
code. This situation is coined by the developers.  Efficiency –The amount of hardware resources 4. Design Control.
Software Fault: Fault occurs in software means and code the software, needs to perform a Which are main components of project life cycle
that the logic was not incorporated to handle the function. components?
errors in the application. This is an undesirable  Integrity –The extent to which the software can Stage1: Planning and requirement analysis
situation, but it mainly happens due to invalid control an unauthorized person from the Stage2: Defining Requirements
documented steps or a lack of data definitions. accessing the data or software. Stage3: Designing the Software
Software Failure: Failure is the accumulation of  Reliability –The extent to which a software Stage4: Developing the project
several defects that ultimately lead to Software performs its intended functions without failure. Stage5: Testing
failure and results in the loss of information in  Usability –The extent of effort required to learn, Stage6: Deployment
critical modules thereby making the system operate and understand the functions of the Stage7: Maintenance
unresponsive. software. Software project life cycle components
Bug: A malfunction in the software/system is an  Correctness –The extent to which a software A software life cycle model (also termed process
error that may cause components or the s ystem to meets its requirements specification. model) is a pictorial and diagrammatic representation
fail to perform its required functions. For example, 2 Product Revision: It includes three software of the software life cycle. A life cycle model
incorrect data description, statements, input data, quality factors, which are required for testing and represents all the methods required to make a
design, etc. maintenance of the software. software product transit through its life cycle stages.
Defect: Defect in a software product represents the  Flexibility – The effort needed to improve an It also captures the structure in which these methods
inability and inefficiency of the software to meet the operational software program. are to be undertaken.
specified requirements and criteria and  Testability – The effort required to verify a Stage1: Planning and requirement analysis
subsequently prevent the software application to software to ensure that it meets the specified Requirement Analysis is the most important and
perform the expected and desired working. requirements. necessary stage in SDLC.
Software Testing: Testing is generally described as Planning for the quality assurance requirements and
 Maintainability – The effort required to detect
a group of procedures carried out to evaluate some identifications of the risks associated with the
and correct an error during maintenance phase.
aspect of a piece of software. Testing can be projects is also done at this stage.
3. Product Transition: It includes three software
described as a process used for revealing defects in Once the requirement is understood, the SRS
quality factors that allows the software to adapt to
software, and for establishing that the software has (Software Requirement Specification) document is
the change of environments in the new platform or
attained a specified degree of quality with respect to created. The developers should thoroughly follow
technology from the previous.
selected attributes. this document and also should be reviewed by the
 Portability –The effort required to transfer a
What are the three categories belonging to customer for future reference.
program from one platform to another.
McCall’s factor model? Stage2: Defining Requirements
3 categories – Product operation, Product revision,  Re-usability –The extent to which the program’s Once the requirement analysis is done, the next
Product transition factors. code can be reused in other applications. stage is to certainly represent and document the
Relate Quality assurance with Quality control.  Interoperability –The effort required to integrate software requirements and get them accepted from
Justify your answer that QA is not QC. two systems with one another. the project stakeholders.
Quality control can be defined as "part of quality Components of SQA Architecture: This is accomplished through "SRS"- Software
management focused on fulfilling quality 1 Pre-project components 2 Components of Requirement Specification document which contains
requirements." While quality assurance relates to project life cycle activities assessment all the product requirements to be constructed and
how a process is performed or how a product is 3 Components of infrastructure error prevention developed during the project life cycle.
made, quality control is more the inspection aspect of and improvement 4. Components of software Stage3: Designing the Software
quality management. quality management 5. Components of The next phase is about to bring down all the
Define Software Quality Assurance. standardization, certification, and SQA system knowledge of requirements, analysis, and design of
Software quality assurance (SQA) is the ongoing assessment 6. Organizing for SQA — the human the software project. This phase is the product of the
process that ensures the software product meets and components last two, like inputs from the customer and
complies with the organizations established and 1. Pre-Project Components requirement gathering.
standardized quality specifications. This assures that the commitment of the project has Stage4: Developing the project
Quality control: Quality Control is a software been defined clearly regarding the time estimation, In this phase of SDLC, the actual development
engineering process that is used to ensure that the clarification of customer requirements, total budget of begins, and the programming is built. The
approaches, techniques, methods and processes are the project, evaluation of development risks, total implementation of design begins concerning writing
designed in the project are following correctly. Quality staff required for that project. code. Developers have to follow the coding
control activities operate and verify that the 2. Software Project Life Cycle Components guidelines described by their management and
application meet the defined quality standards. In the project development life cycle, it includes programming tools like compilers, interpreters,
What are the three categories belonging to components like reviews, expert opinions, and debuggers, etc. are used to develop and implement
Product Transition Software Quality Factors? finding defects in software design and programming, the code.
Product operation factors − Correctness, whereas in the software maintenance life cycle. Stage5: Testing
Reliability, Efficiency, Integrity, Usability. 3.Infrastructure Components for Error After the code is generated, it is tested against the
Product revision factors − Maintainability, Prevention and Improvements requirements to make sure that the products are
Flexibility, Testability. This component includes staff training, certification, solving the needs addressed and gathered during the
Product transition factors − Portability, Reusability, and configuration management, preventive and requirements stage.
Interoperability. corrective measures in order to reduce the rate of During this stage, unit testing, integration testing,
Find the two contract review stages. errors in software based on the organization’s system testing, acceptance testing is done.
The review process itself is conducted in two stages: accumulated SQA experience. Stage6: Deployment
Stage One – “proposal draft review” - Review of the 4. Management SQA Components Once the software is certified, and no bugs or errors
proposal draft prior to submission to the potential This class includes software quality metrics, software are stated, then it is deployed.
customer quality costs, which includes control of maintenance Then based on the assessment, the software may be
Stage Two – “contract draft review” - Review of and development activities, and the introduction of released as it is or with suggested enhancement in
contract draft prior to signing. managerial involvement in order to reduce the risk of the object segment.
Who performs a contract review? quality, schedule, and budget in the project. Stage7: Maintenance
A contract review is a contractual process used to 5. Components of Standardization, Certification, Once when the client starts using the developed
identify and analyse the key provisions within an and SQA System Assessment systems, then the real issues come up and
agreement. A legal professional will read each The main objective of this class is the utilization of requirements to be solved from time to time.
contract thoroughly to understand the terms and professional international knowledge, which helps in This procedure where the care is taken for the
conditions and highlight risks or relevant information. the coordination between the different organization developed product is known as maintenance.
Tell the way to conduct contract review process? quality systems at a professional level. Software quality cost:
•Clarification of the customer’s requirements 6. Organizing for SQA Human Components The costs of software quality (COSQ) are those costs
•Review of the project’s schedule and resource This base includes managers, testers, and other SQA incurred through both meeting and not meeting the
requirement estimates •Evaluation of the practitioners that are interested in SQA. The main customer's quality expectations.
professional staff’s capacity to carry out the proposed objective is to support and initiate the SQA activities,
project •Evaluation of the customer’s capacity to fulfil detect the gaps/deviations in them, and suggest
his obligations •Evaluation of development risks. improvements for that.
List out the different types of BBT. Ways to extend the SQA system: Six Sigma in ST
Black box testing involves testing a system with no 1 Integrate automated testing: Automated testing Six Sigma is the process of producing high and
prior knowledge of its internal workings. A tester tools can help to improve the efficiency and improved quality output. This can be done in two
provides an input, and observes the output effectiveness of the SQA system by automating phases – identification and elimination. The cause of
generated by the system under test. repetitive and time-consuming testing tasks. defects is identified and appropriate elimination is
1. Decision Table Technique: Decision Table 2 Implement code review processes: Code done which reduces variation in whole processes.
Technique is a systematic approach where various Characteristics of Six Sigma:
reviews can help to identify and fix defects and
input combinations and their respective system 1 Statistical Quality Control:
vulnerabilities in the code before it is deployed.
behaviour are captured in a tabular form. It is Six Sigma is derived from the Greek Letter? which
appropriate for the functions that have a logical 3 Conduct performance testing: Performance denote Standard Deviation in statistics. Standard
relationship between two and more than two inputs. testing is a critical aspect of SQA that helps to ensure Deviation is used for measuring the quality of output.
2. Boundary Value Technique Boundary Value that the software can handle the expected load and 2 Methodical Approach:
Technique is used to test boundary values, boundary performs well under stress. 4 Integrate security The Six Sigma is a systematic approach of
values are those that contain the upper and lower testing: Security testing is a critical component of the application in DMAIC and DMADV which can be used
limit of a variable. It tests, while entering boundary SQA system that helps to identify and mitigate to improve the quality of production. DMAIC means
value whether the software is producing correct security vulnerabilities in the software. for Design-Measure- Analyze-Improve-Control.
output or not. 5 Incorporate user testing: By incorporating user While DMADV stands for Design-Measure-
3. State Transition Technique: State Transition testing into the SQA system, developers can gain Analyze-Design-Verify.
Technique is used to capture the behaviour of the valuable feedback from users and improve the 3 Fact and Data-Based Approach:
software application when different input values are usability and user experience of the software. The statistical and methodical method shows the
given to the same function. This applies to those scientific basis of the technique.
SQA activities in software maintenance:
types of applications that provide the specific number 4 Project and Objective-Based Focus:
of attempts to access the application. 1 Change management: This can involve change The Six Sigma process is implemented to focus on
4. All-pair Testing Technique: All-pair testing request forms, change impact analysis, and the requirements and conditions.
Technique is used to test all the possible discrete regression testing to ensure that the changes do not 5 Customer Focus:
combinations of values. This combinational method adversely affect the quality or performance of the The customer focus is fundamental to the Six Sigma
is used for testing the application that uses checkbox software. 2 Defect management: This can involve approach. The quality improvement and control
input, radio button input, list box, text box, etc. defect tracking tools, root cause analysis, and standards are based on specific customer
5. Cause-Effect Technique: Cause-Effect verification testing to ensure that the defects have requirements.
Technique underlines the relationship between a been resolved. 3 Configuration management: This Teamwork Approach to Quality Management:
given result and all the factors affecting the result. It can involve version control, release management, The Six Sigma process requires organizations to get
is based on a collection of requirements. and configuration audits to ensure that the software organized for improving quality.
6. Equivalence Partitioning Technique: artefacts are properly tracked and managed. ISO 9000 Quality Standards: It is defined as the
Equivalence partitioning is a technique of software quality assurance system in which quality
4 Performance monitoring: This can involve
testing in which input data divided into partitions of components can be organizational structure,
performance testing, load testing, and analysis of
valid and invalid values, and it is mandatory that all responsibilities, procedures, processes, and
partitions must exhibit the same behaviour. performance metrics to identify performance resources for implementing quality management.
List out the main components of software bottlenecks and optimize the software for improved Examples: ISO/IEC 9075-9: 2001, ISO/IEC 9075-13:
maintenance. Verification Validation 2002
1. Change Request, 2. Change Management It includes checking It includes testing CMMI
3. Impact Analysis, 4. System Release Planning documents, design, and validating the The Capability Maturity Model Integration (CMMI) is
5. Change Implementation 6. System Release codes and programs. actual product. a model that aids in identifying the strengths and
Risk Analysis (example spiral model): Risk Verification is the static Validation is the weaknesses of an organization’s current processes
analysis in software testing is an approach to testing. dynamic testing. and shows the way to improvement. CMMI’s primary
software testing where software risk is analyzed and It does not include the It includes the goal is to create high-quality software.
measured. Traditional software testing normally execution of the code. execution of the Maturity Levels:
looks at relatively straight-forward function testing code. Maturity Level 1 (Initial):
(e.g. 2 + 2 = 4). Spiral model is one of the most Methods used in Methods used in Maturity Level 2 (Managed):
important Software Development Life Cycle models, verification are reviews, validation are Black Maturity Level 3 (Defined):
which provides support for Risk Handling. The exact walkthroughs, Box Testing, White Maturity Level 4 (Quantitatively measured):
number of loops of the spiral is unknown and can inspections and desk- Box Testing and Maturity Level 5 (Optimized):
vary from project to project. Each loop of the spiral is checking. non-functional IEEE
called a Phase of the software development process. testing. IEEE 829: This standard is used for proper document
Different phases of the Spiral Model: 1) It can find the bugs in the It can only find the formatting and is practiced in different stages of
Objectives determination and identify alternative early stage of the bugs that could not software testing.
solutions: Requirements are gathered from the development. be found by the IEEE 1061: It has the technique to establish better
customers and the objectives are identified, verification process. quality and validating the software with quality
elaborated, and analyzed at the start of every phase. The goal of verification is The goal of metrics.
2) Identify and resolve Risks: During the second application and software validation is an IEEE 1059: Supports in guiding software verification
quadrant, all the possible solutions are evaluated to architecture and actual product. and validation.
select the best possible solution. Then the risks specification. IEEE 1008: Standard which supports proper unit
associated with that solution are identified and the Software Quality Assurance Standards testing.
risks are resolved using the best possible strategy. 3) In general, SQA may demand conformance to one or Alpha Testing Beta Testing
Develop next version of the Product: During the more standards. Alpha testing Beta testing commonly
third quadrant, the identified features are developed Some of the most popular standards are involves both the uses black-box testing.
and verified through testing. At the end of the third discussed below: white box and black
quadrant, the next version of the software is ISO 9000: This standard is based on seven quality box testing.
available. 4) Review and plan for the next Phase: management principles which help the organizations Alpha testing is Beta testing is performed
In the fourth quadrant, the Customers evaluate the to ensure that their products or services are aligned performed by by clients who are not
so far developed version of the software. In the end, with the customer needs. testers who are part of the organization.
planning for the next phase is started. CMMI level: CMMI stands for Capability maturity usually internal
Automation Testing: In automation testing, the model Integration. This model originated in software employees of the
test automation engineer will write the test script or engineering. It can be employed to direct process organization.
use the automation testing tools to execute the improvement throughout a project, department, or Alpha testing is Beta testing is performed
application. On the other hand, in manual testing, the entire organization. performed at the at the end-user of the
test engineer will write the test cases and implement Test Maturity Model integration (TMMi): Based on developer’s site. product.
the software on the basis of written test cases. CMMi, this model focuses on maturity levels in Alpha testing Beta testing also
What is UI automation testing? software quality management and testing. ensures the quality concentrates on the
Automated tests that drive your application through Data Flow Testing is a type of structural testing. It is of the product quality of the product but
its user interface (UI) are known as coded UI tests a method that is used to find the test paths of a before forwarding to collects users input on
(CUITS) in Visual Studio. These tests include program according to the locations of definitions and beta testing. the product and ensures
functional testing of the UI controls. uses of variables in the program. It has nothing to do that the product is ready
What are Drivers tool. with data flow diagrams. Data Flow Testing uses the for real time users.
Drivers are tools used to control and operate the control flow graph to find the situations that can Alpha testing may Beta testing requires only
software being tested. One of the simplest examples interrupt the flow of the program.
of a driver is a batch file, a simple list of programs or require a long a few weeks of
execution cycle. execution.
commands that are executed sequentially.
 Structural Testing Functional Testing Discuss the types of review. Explain various List out the Software testing axioms.
(WBT) (BBT) components of review plan. 1. It is impossible to test a program completely. 2.
Structural testing is Functional testing can A software review is a process or meeting during Software testing is a risk-based exercise. 3. Testing
done in manual mode. be performed either which a software product is examined by a project cannot show the absence of bugs. 4. The more bugs
manually or personnel, users, computers, user representatives, you find, the more bugs there are. 5. Not all bugs
automatically. or other interested parties for comment or approval. found will be fixed. 6. It is difficult to say when a bug
Structural testing is Functional testing is Types: Software Peer Reviews: This type of review is indeed a bug. 7. Specifications are never final. 8.
done after the coding performed during is conducted by the main author of the software, or it Software testers are not the most popular members
process is completed development and/or can be between the colleagues so that the evaluation of a project. 9. Software testing is a disciplined and
by maintenance maintenance. can be done of the technical content or quality of the technical profession.
groups. work. Write short notes on Test, Test Set, and Test
Structural testing Functional testing Software Management Reviews: The management Suite.
mainly focuses on focuses on verifying representatives are responsible for this type of A Test is a group of related test cases, or a group of
logical errors or bugs in that the system meets review. Software Audit Reviews: These are related test cases and test procedure.
the code. its requirements. conducted by the personnel outside of the software A group of related test is sometimes referred to as a
Structural Testing is Functional testing project. They evaluate the software with test set.
used for testing could be used to test specifications, standards, and other criteria. A group of related tests that are associated with a
systems that are stand-alone List the challenges in automation? database, and are usually run together, is sometimes
interconnected. applications. 1) Testing the complete application referred to as a Test Suite.
In Structural Testing, In Functional Testing, 2) Misunderstanding of company processes Why is Software Testing hard?
software application it is verified by 3) Relationship with developers 1 Software Testing is hard and difficult because we
functionality is verified performing tests that 4) Regression testing need to test the software/application for both valid
by performing tests that exercise specified 5) Lack of skilled testers and invalid inputs. 2 During the time of testing we
exercise each individual combinations of 6) Testing always under time constraint always need to give the inputs in such a way that
module in isolation. related modules. Write some tips to improve automation testing? each and every line of the program/code is tested
Decide What to Automate. efficiently. 3 Tester needs to give inputs randomly and
Quality Assurance Quality Control Prioritize & Divide Tasks. ensure that the software/application never fails. 4 We
Prepare Test Cases & Scenario Beforehand. need to test the software by keeping the user
(QA) (QC)
Identify the Process. perspective in mind and check whether the error
It focuses on providing It focuses on fulfilling
Create Tests that Don't Affect UI Changes. messages displayed properly or not.
assurance that the the quality requested.
Utilize Quality Test Data. Show the process of object oriented model in
quality requested will
Define baseline testing. flow chart format.
be achieved.
Baseline testing is a type of non- functional testing
It is the technique of It is the technique to
which is generally performed by testing engineers. It
managing quality. verify quality.
refers to the validation of the documents and
It is involved during the It is not included specifications on which test cases are designed.
development phase. during the Many problems are discovered and solved during
development phase. baseline testing.
It does not include the It always includes the What is a performance baseline?
execution of the execution of the The Performance Measurement Baseline is a time-
program. program. phased schedule of all the work to be performed, the
It is a managerial tool. It is a corrective tool. budgeted cost for this work, and the organizational
The aim of quality The aim of quality elements that produce the deliverables from this
assurance is to prevent control is to identify work.
defects. and improve the What is KPI in testing?
defects. A Key Performance Indicator (or KPI) is usually used
It is responsible for the It is responsible for to evaluate the software process efficiency
entire software the software testing evaluation. The important parameters and their
development life cycle. life cycle. usage are analysed and the outcome of the
Example: Verification Example: Validation measurement is used to trigger any process
Software Quality Metrics improvements.
Software metrics can be classified into three What is Test Plan?
categories − A TEST PLAN is a document describing software
Product metrics − Describes the characteristics of testing scope and activities. It is the basis for formally
the product such as size, complexity, design features, testing any software/product in a project.
performance, and quality level. What is the role of test manager?
Process metrics − These characteristics can be The test manager is usually responsible for test
used to improve the development and maintenance policy making, customer interaction, test planning,
activities of the software. test documentation, controlling and monitoring of
Project metrics − This metrics describe the project tests, training, test tool acquisition, participation in
characteristics and execution. Examples include the inspections and walkthroughs, reviewing test work,
number of software developers, the staffing pattern the test repository, and staffing issues such as hiring,
over the life cycle of the software, cost, schedule, and firing. and evaluation of the test team members.
productivity. What is compatibility testing?
Advantage of Software Metrics Compatibility Testing is a type of Software testing to
1 Comparative study of various design methodology check whether your software is capable of running on
of software systems. different hardware, operating systems, applications,
2 In the preparation of software quality specifications. network environments or Mobile devices.
3 In the verification of compliance of software Compatibility Testing is a type of the Non-functional
systems requirements and specifications. testing.
Disadvantage of Software Metrics What is AD HOC TESTING?
1 The application of software metrics is not always AD HOC TESTING, also known as Random Testing
easy, and in some cases, it is difficult and costly. or Monkey Testing, is a method of software testing
2 The verification and justification of software metrics without any planning and documentation. The tests
are based on historical/empirical data whose validity are conducted informally and randomly without any
is difficult to verify. formal expected results. The tester improvises the
Define test Harness. steps and arbitrarily executes them (like a monkey
The auxiliary code developed into support testing of typing while dancing).
units and components is called a test harness. What is Random Testing?
Write the WBS elements for testing? Random testing is a black-box software testing
1. Project startup 2. Management coordination 3. technique where programs are tested by generating
Tool selection 4. Test planning 5. Test design 6. Test random, independent inputs.
development 7. Test execution 8. Test measurement, Results of the output are compared against software
and monitoring 9. Test analysis and reporting 10. Test specifications to verify that the test output is pass or
process improvement. fail.