SDLC (Software Development Life Cycle) is What is Manual Testing?

l Testing? Manual testing is Black Box Testing White Box Testing

used in Every Software Development testing of the software where tests are #It is a way of software testing in which the # It is a way of testing the software in which the
Company because it is the root of the executed manually by a QA Analyst. It is internal structure or the program or the code is tester has knowledge about the internal
Development Cycle, if that model would not performed to discover bugs in software under hidden and nothing is known about it. # It is structure or the code or the program of the
exist in the world, firstly no software can build development. In Manual testing, the tester mostly done by software testers. # No software. # It is mostly done by software
secondly if any how it would be made, it’s not checks all the essential features of the given knowledge of implementation is needed. # It developers. # Knowledge of implementation is
going to succeed it has no use, because of no application or software. In this process, the can be referred as outer or external software required. # It is the inner or the internal
maintenance, but Luckily SDLC model exist in software testers execute the test cases and testing. # It is functional test of the software. software testing. # It is structural test of the
Tech world But why we need it Actually! generate the test reports without the help of # This testing can be initiated on the basis of software. # This type of testing of software is
There are several reasons why organizations any automation software testing tools. It is a requirement specifications document.# No started after detail design document. # It is
use the Software Development Life Cycle classical method of all testing types and helps knowledge of programming is required. # It is mandatory to have knowledge of
(SDLC) when developing software find bugs in software systems. It is generally the behavior testing of the software. # It is programming. # It is the logic testing of the
applications: To provide a structured and conducted by an experienced tester to applicable to the higher levels of testing of software. # It is generally applicable to the
organized approach to software development: accomplish the software testing process. software. # It is also called closed testing. # It is lower levels of software testing. # It is also
The SDLC provides a framework for managing least time consuming. # It is not suitable or called as clear box testing. it is most time
the software development process, which What is Automation Testing? In Automated preferred for algorithm testing. # Can be done consuming. # It is suitable for algorithm testing.
helps to ensure that all necessary steps are Software Testing, testers write code/test by trial and error ways and methods. Data domains along with inner or internal
taken and that the final product meets the scripts to automate test execution. Testers use # Example: search something on google by boundaries can be better tested. # Example:
requirements appropriate automation tools to develop the using keywords # Types of Black Box Testing: by input to check and verify loops #Types of
1. Requirements gathering and analysis: This test scripts and validate the software. The goal • A. Functional Testing White Box Testing:
phase involves gathering information about is to complete test execution in a less amount • B. Non-functional testing • A. Path Testing • B. Loop Testing • C. Condition
the software requirements from stakeholders, of time. Automated testing entirely relies on testing
such as customers, end-users, and business the pre-scripted test which runs automatically Validation
analysts. 2. Design: In this phase, the software to compare actual result with the expected # We check whether the developed product is Verification
design is created, which includes the overall results. This helps the tester to determine right. # Validation is also known as dynamic # We check whether we are developing the
architecture of the software, data structures, whether or not an application performs as testing. # Validation includes testing like right product or not. # Verification is also
and interfaces. It has two steps: High-level expected. Automated testing allows you to functional testing, system testing, integration, known as static testing. # Verification includes
design (HLD): It gives the architecture of execute repetitive task and regression test and User acceptance testing. # It is a process different methods like Inspections, Reviews,
software products. Low-level design (LLD): It without the intervention of manual tester. of checking the software during or at the end and Walkthroughs. # It is a process of checking
describes how each and every feature in the Even though all processes are performed of the development cycle to decide whether the work-products (not the final product) of a
product should work and every component. automatically, automation requires some the software follow the specified business development cycle to decide whether the
3. Implementation or coding: The design is manual effort to create initial testing scripts. requirements. # Quality control comes under product meets the specified requirements.
then implemented in code, usually in several validation testing. # In validation testing, the # Quality assurance comes under verification
iterations, and this phase is also called as Manual Testing execution of code happens. # In the validation testing # The execution of code does not
Development.4. Testing: The software is # In manual testing, test cases are executed by testing, we can find those bugs, which are not happen in the verification testing. # In
thoroughly tested to ensure that it meets the a human tester and software. # Manual testing caught in the verification process. # Validation verification testing, we can find the bugs early
requirements and works correctly. is time-consuming and takes up human testing is executed by the testing team to test in the development phase of the product.
5. Deployment: After successful testing, The resources. # Exploratory testing is possible in the application. # Verification testing is executed by the Quality
software is deployed to a production Manual Testing # The initial investment in the assurance team to make sure that the product
environment and made available to end-users. Manual testing is comparatively lower. ROl is is developed according to customers'
6. Maintenance: This phase includes ongoing lower compared to Automation testing in the Silk Test in Software Testing requirements. # Verification is done before the
support, bug fixes, and updates to the long run. # Manual testing is not as accurate Silk Test is a powerful automation tool widely validation
software because of the possibility of the human errors. used in software testing to perform regression
Small changes like change in id, class, etc. of a and functional testing on a variety of • PERFORMANCE TESTING checks the speed,
•STRESS TESTING is a type of Software Testing button wouldn't thwart execution of a manual applications. It offers a comprehensive set of response time, reliability, resource usage,
that verifies the stability & reliability of the tester. # Investment is needed for human features that streamline the testing process, scalability of a software program under their
system. This test mainly measures the system resources. # Not cost effective for high volume including the ability to create and execute expected workload. The purpose of
on its robustness and error handling regression. # Manual Tests are usually automated test scripts, identify and verify Performance Testing is not to find functional
capabilities under extremely heavy load recorded in an Excel or Word, and test results objects within applications, and generate defects but to eliminate performance
conditions. •Stress Testing is done to make are not readily/ readily available. # The manual detailed test reports. Silk Test enables testers bottlenecks in the software or device. • The
sure that the system would not crash under testing method allows human observation, to efficiently validate the functionality and focus of Performance Testing is checking a
crunch situations. It even tests beyond the which may be useful to offer user-friendly performance of software applications across software program's • Speed - Determines
normal operating point and evaluates how the system.# Performance Testing is not feasible different platforms and environments, whether the application responds quickly •
system works under those extreme conditions. ultimately helping to improve software quality Scalability - Determines maximum user load
• A most prominent use of stress testing is to Automation Testing and accelerate the testing process. the software application can handle. • Stability
determine the limit, at which the system or # Automation Testing uses automation tools 1 - Silk Test is a software testing tool designed - Determines if the application is stable under
software or hardware breaks. It also checks to execute test cases. # Automated testing is for automated functional and regression varying loads • Performance Testing is
whether the system demonstrates effective significantly faster than a manual approach. testing of web, mobile, and enterprise popularly called “Perf Testing” • Performance
error management under extreme conditions #Automation does not allow random testing applications. 2) It supports a variety of testing will determine whether their software
Stress testing extremely valuable for the # The initial investment in the automated technologies such as Java, .NET, HTML5, Flex, meets speed, scalability and stability
following reason •To check whether the testing is higher. Though the ROl is better in the and SAP. 3) Silk Test allows testers to create requirements under expected workloads.
system works under abnormal conditions. long run. # Automated testing is a reliable test scripts using a visual scripting language or Types of Performance Testing
•Displaying appropriate error message when method, as it is performed by tools and scripts. automate tests using programming languages Load testing - checks the application's ability
the system is under stress. •System failure There is no testing Fatigue. # For even a trivial like C# or VB.NET. 4) It provides features for to perform under anticipated user loads. The
under extreme conditions could result in change in the Ul of the AUT, Automated Test test recording, playback, and debugging to objective is to identify performance
enormous revenue loss •It is better to be Scripts need to be modified to work as streamline the testing process. 5) Silk Test bottlenecks before the software application
prepared for extreme conditions by executing expected # Investment is required for testing supports data driven testing by allowing goes live. Stress testing - involves testing an
Stress Testing tools as well automation engineers # Not cost testers to parameterize test scripts using application under extreme workloads to see
•Distributed Stress Testing:In distributed effective for low volume regression # With external data sources. 6) The tool offers a how it handles high traffic or data processing.
client-server systems, testing is done across all automation testing, all stakeholders can login robust test execution engine that can run tests The objective is to identify the breaking point
clients from the server. •Application Stress into the automation system and check tes on multiple browsers, devices, and platforms. of an application. Endurance testing - is done
Testing:This testing concentrate on finding execution results # Automated testing does 7) Silk Test integrates with popular CI/CD tools to make sure the software can handle the
defects related to data locking and blocking, not involve human consideration. So it can like Jenkins for continuous testing as part of expected load over a long period of time. Spike
network issues and performance bottlenecks never give assurance of user-friendliness and the software development lifecycle testing - tests the software's reaction to
in an application. •Transactional Stress positive customer experience. # Performance sudden large spikes in the load generated by
Testing:It does stress testing on one or more Tests like Load Testing, Stress users. Volume testing - Under Volume Testing
transactions between two or more large no. of. Data is populated in a database
applications. It is used for fine-tuning & criteria for completion of testing
Test completion is the last step in the software and the overall software system's behavior is
optimizing the system. •Systemic Stress monitored. The objective is to check software
Testing:This is integrated stress testing which WinRunner is an Automation Software Testing testing life cycle, where we finalize all testing application's performance under varying
can be tested across multiple systems running Tool that is owned by HP and was developed activities and document the results. Our main database volumes. Scalability testing - The
on the same server. It is used to find defects by Mercury Interactive. It is known and goal is to ensure the software product is ready objective of scalability testing is to determine
where one application data blocks another extensively used for its ability to supports the for production release. the software application's effectiveness in
application. •Exploratory Stress Testing:This is majority of the programming languages and The activities involved in test completion can "scaling up" to support an increase in user load.
one of the types of stress testing which is used web development technologies such as C, C++, vary depending on the project but typically It helps plan capacity addition to your software
to test the system with unusual parameters or C#, Visual Basic, VC++, D2K, Java, HTML, Power include the following: • Verifying that all test system.
conditions that are unlikely to occur in a real Builder, Delphe, Cibell, etc. It is used for cases have been executed • Analyzing the test Common Performance Problems Most
scenario. It is used to find defects in performing various testing techniques, which results and identifying any defects • Prioritizing performance problems revolve around speed,
unexpected scenarios includes the functional testing, user interface and fixing defects • Generating a test response time, load time and poor scalability.
•Stress Testing process can be done in 5 major testing, integration testing, regression testing, completion report • Communicating the test Speed is often one of the most important
steps: •Planning the Stress Test: Here you etc., by making use of its options to record the results to stakeholders attributes of an application. A slow running
gather the system data, analyze the system, functionality for creating test steps and by The test completion report is a document that application will lose potential users.
define the stress test goals •Create using the playback UI interactions option for summarizes the results of the testing activities. Performance testing is done to make sure an
Automation Scripts: In this phase, you create generating the test scripts.WinRunner is a What is the purpose of Test Completion? app runs fast enough to keep a user's attention
the Stress testing automation scripts, generate Functional Testing tool to work on a A clear sense of purpose is essential to success and interest. Take a look at the following list of
the test data for the stress scenarios.Script compilation of tests that are used for in any endeavor. When it comes to testing a common
Execution: In this stage, you run the Stress collaborating with the HP QuickTest software product, we must ensure we’ve done
testing automation scripts and store the stress Professional and to be used as a supporting everything possible to ensure it’s ready for
results. Results Analysis: In this stage, you element for the quality assurance process, as a release. That’s where test completion criteria
analyze the Stress Test results and identify part of Test phase in the Software come in – the specific conditions we need to
bottlenecks. Tweaking and Optimization: In Development Life Cycle. This testing software meet before stopping testing.
this stage, you fine-tune the system, change is applied as a part of progress in product Things like • how many test cases we’ve run,
configurations, optimize the code with goal excellence • how much of the code we’ve covered,
meet the desired benchmark. • how many bugs we’ve found and fixed, and
• how risky the product is in determining when
we’re done testing.
It’s essential to have these measures defined in
the test plan and agreed upon by everyone
involved so that we’re all on the same page
and can work efficiently.
Quality Assurance (QA) Beta Testing Field testing refers to the process of testing The purpose of software testing
# QA focuses on providing assurance that the The beta testing phase is an important step and evaluating an application in real-world The purpose of software testing is to ensure
quality requested will be achieved. # QA is the towards ensuring a successful product launch. conditions outside of the controlled the delivery of a high-quality, reliable, and
technique of managing quality. # QA is It helps the developers to ensure that their development environment. Testers deploy efficient software product. It is a systematic
involved during the development phase. # QA software is stable, reliable, and meets the this approach for both web and mobile and disciplined approach that aims to identify
does not include the execution of the program. needs of the users. Beta testing also helps to applications with the aim of gathering real-user and rectify defects, errors, and potential issues
# QA is a managerial tool. # QA is process build customer loyalty by involving them in the feedback and identifying any issues or within the software during its development
oriented. # The aim of quality assurance is to development process and making them feel potential improvements before the official lifecycle. The primary goals of software testing
prevent defects. # Quality Assurance is like their input is valued. Beta Testing is release. In mobile, it involves deploying the app are to validate the software’s functionality,
performed before # Quality Control. # QA is a performed by real users of the software to actual devices and having users interact enhance its performance, and improve the
preventive technique. # QA is a proactive application in a real environment. Beta testing with it in their everyday environments. overall user experience.
measure. # QA is responsible for the entire is one of the types of User Acceptance Testing. Typically, the testing is done on mobile Here are a few points explaining the purpose
software development life cycle. # QA is a low- A Beta version of the software, whose networks only. It is a type of mobile testing of software testing: • Validate the functionality
level activity that identifies an error and feedback is needed, is released to a limited Field testing checks the app on various of the software to ensure it meets the specified
mistakes that QC cannot.# Pays main focus is number of end-users of the product to obtain devices, operating systems, and network requirements and works as intended. • Identify
on the intermediate process. # All team feedback on the product quality. Beta testing conditions to assess its performance, and eliminate defects and errors that could
members of the project are involved. # QA helps in minimization of product failure risks functionality, usability, and overall user negatively impact the software’s performance
aims to prevent defects in the system and it provides increased quality of the experience. The goal is to uncover issues and and stability. • Improve the reliability and
product through customer validation. It is the collect feedback that went unnoticed during robustness of the software to provide
Quality Control (QC) last test before shipping a product to the the development and testing phases. consistent and accurate results. • Enhance the
# QC focuses on fulfilling the quality customers. One of the major advantages of Field tests are a perfect way of experimenting software’s performance, making it more
requested. # QC is the technique to verify beta testing is direct feedback from with your product before launching it to your efficient and responsive even under heavy
quality. # QC is not included during the customers. customer base. The short time window user loads. • Ensure the software is user-
development phase. # QC always includes the Beta testing is necessary for several reasons: between the final testing and the release date friendly and intuitive, offering a positive and
execution of the program. # QC is a corrective 1 Identify and fix bugs: Beta testing helps to is when the field test is performed. The process satisfactory user experience.
tool. # QC is product oriented. # The aim of identify and fix bugs or errors in the software. It allows you to: • Gain access to unhinged
quality control is to identify and improve the allows developers to catch issues that were feedback from a small portion of users who The CMM is not a software lifecycle model. It is
defects. # Quality Control is performed after not detected during the development process interact with the application. • Develop a strategy for improving software process.
the Quality Assurance activity is done. # QC is a and resolve them before the official launch. products that are error-free and ready for CMM is used to judge the maturity of the
corrective technique. # QC is a reactive 2 Ensure software quality: Beta testing helps to launch. • Collect critical data that are essential software process of an organization. CMM
measure. # QC is responsible for the software ensure that the software meets the expected to improve the application and its features. helped organization to improve the quality of
testing life cycle. # QC is a high-level activity quality standards before it is released to the • Work on new features and upgrades for the software they developed. The Software
that identifies an error that QA cannot. # Its public. This helps to reduce negative reviews, future. • Use the test data from the users for Engineering Institute (SEI) Capability Maturity
primary focus is on final products. # Generally, returns, and refunds that can affect the other purposes, such as sales and marketing. Model (CMM) specifies an increasing series of
the testing team of the project is involved. product’s reputation. levels of a software development organization.
# QC aims to identify defects or bugs in the 3 Evaluate performance: Beta testing enables The higher the level, the better the software
system. # QC is a more time-consuming People Capability Maturity Model (PCMM)
developers to evaluate the software’s PCMM is a maturity structure that focuses on development process, hence reaching each
activity. performance in real-world scenarios, which level is an expensive and time-consuming
continuously improving the management and
can help identify issues with the software’s development of the human assets of an process. CMM can be used in two ways:
Cost of Quality functionality, speed, and responsiveness. organization. The People Capability Maturity Capability evaluation: provide a way to access
There is cost of activity in every project, it 4 Get user feedback: Beta testing provides a Model (PCMM) is a framework that helps the the software process capability. Software
should have business value and software platform for users to provide feedback about organization successfully address their critical process assessment: it is used by an
testing software testing is no exception. To the software, its features, and usability. This people issues. Based on the best current study organization with the objective to improve the
optimize its business value, test managers feedback can be used to improve the in fields such as human resources, knowledge process capability  Level One : Initial - The
should optimize testing appropriately. There software’s overall performance and user management, and organizational software process is characterized as
should not be unnecessary testing otherwise it experience. development, the PCMM guides organizations inconsistent. Defined processes and standard
causes unnecessary delays and ends up 5 Improve user engagement: Beta testing can in improving their steps for managing and practices that exist are abundoned during a
incurring more costs. Also, there should not be improve user engagement by allowing users to developing their workforces. The PCMM crisis. Success of the organization majorly
incomplete or too less testing otherwise, there test the software and provide feedback. This subsists of five maturity levels that lay depends on an individual effort, talent, and
may be a chance of defective products to be helps to build a relationship between the successive foundations for continuously heroics. The heroes eventually move on to
handed to the end users. Therefore, software developers and the users, leading to increased improving talent, developing effective other organizations taking their wealth of
testing should be done appropriately. user satisfaction methods, and successfully directing the knowledge or lessons learnt with them. Here
Cost of Quality : It is the most established, people assets of the organization. each engineer follow their own style..  Level
effective measure of quantifying and Initial Level: Maturity Level 1 The Initial Level of Two: Repeatable - This level of Software
calculating the business value of testing. There ISO 900 series standards maturity includes no process areas. Although Development Organization has a basic and
are four categories to measure cost of quality: The International organization for workforce practices implement in Maturity consistent project management processes to
Prevention costs, Detection costs, Internal Standardization is a world wide federation of Level, 1 organization tend to be inconsistent or track cost, schedule, and functionality. Size and
failure costs, and External failure costs. national standard bodies. The International ritualistic, virtually all of these organizations cost estimation technique such as COCOMO
These are explained as follows below. standards organization (ISO) is a standard perform processes that are defined in the ,function point analysis . The process is in place
1 Prevention costs include cost of training which serves as a for contract between Maturity Level 2 process areas. Managed to repeat the earlier successes on projects with
developers on writing secure and easily independent parties. It specifies guidelines for Level: Maturity Level 2 To achieve the similar applications. Program management is a
maintainable code 2 Detection costs include development of quality system. Managed Level, Maturity Level 2, managers key characteristic of a level two organization. 
the cost of creating test cases, setting up Quality system of an organization means the starts to perform necessary people Level Three: Defined - The software process
testing environments, revisiting testing various activities related to its products or management practices such as staffing, for both management and engineering
requirements. 3 Internal failure costs include services. Standard of ISO addresses to both operating performance, and adjusting activities are documented, standardized, and
costs incurred in fixing defects just before aspects i.e. operational and organizational compensation as a repeatable management integrated into a standard software process
delivery. 4 External failure costs include aspects which includes responsibilities, discipline. The organization establishes a for the entire organization. . Also introduce a
product support costs incurred by delivering reporting etc. An ISO 9000 standard contains culture focused at the unit level for ensuring training group to provide organization wide
poor quality software. set of guidelines of production process that person can meet their work commitments knowledge. ISO 9000 certificate provide this
without considering product itself. Defined Level: Maturity Level 3 The software level.  Level Four: Managed - Management
test plan ISO 9000 Certification process for both management and can effectively control the software
A test plan is a document that consists of all Why ISO Certification required by Software engineering activities are documented, development effort using precise
future testing-related activities. It is prepared Industry?There are several reasons why standardized, and integrated into a standard measurements. At this level, organization set a
at the project level and in general, it defines software industry must get an ISO certification. software process for the entire organization quantitative quality goal for both software
work products to be tested, how they will be Some of reasons are as follows : • This and all projects across the organization use an process and software maintenance. At this
tested, and test type distribution among the certification has become a standards for approved, tailored version of the organization's maturity level, the performance of processes is
testers. Before starting testing there will be a international bidding. • It helps in designing standard software process for controlled using statistical and other
test manager who will be preparing a test plan. high-quality repeatable software products. developing,testing and maintaining the quantitative techniques, and is quantitatively
In any company whenever a new project is • It emphasis need for proper documentation. application. Predictable Level: Maturity Level predictable.  Level Five: Optimizing - The Key
taken up before the tester is involved in the • It facilitates development of optimal 4 At the Predictable Level, the organization characteristic of this level is focusing on
testing the test manager of the team would processes and totally quality measurements. handles and exploits the capability developed continually improving process performance
prepare a test Plan. Advantages of ISO 9000 Certification : by its framework of workforce competencies. through both incremental and innovative
Some of the advantages of the ISO 9000 The organization is now able to handle its technological improvements. At this level,
The test plan serves as the blueprint that certification process are following : capacity and performance quantitatively. changes to the process are to improve the
changes according to the progressions in the • Business ISO-9000 certification forces a Optimizing Level: Maturity Level 5 At the process performance and at the same time
project and stays current at all times. corporation to specialize in “how they are Optimizing Level, the integrated organization is maintaining statistical probability to achieve
It serves as a base for conducting testing doing business”. Each procedure and work focused on continual improvement. These the established quantitative process-
activities and coordinating activities among a instruction must be documented and thus improvements are made to the efficiency of improvement objectives.
QA team. becomes a springboard for continuous individuals and workgroups, to the act of
It is shared with Business Analysts, Project improvement. • Employees morale is competency-based processes, and workforce
Managers, and anyone associated with the increased as they’re asked to require control of practices and activities
project. their processes and document their work
processes • Better products and services
result from continuous improvement process. A Quality Assurance Plan (QAP) is a document
Software Quality Management • Increased employee participation, or set of documents that outlines the
System contains the methods that are used by involvement, awareness and systematic systematic processes, procedures, and
the authorities to develop products having the employee training are reduced problems. standards for ensuring the quality of a product
desired quality. Some of the methods are: or service. It is a key component of quality
• Managerial Structure: Quality System is management and is used in various industries
responsible for managing the structure as a to establish and maintain a consistent level of
whole. Every Organization has a managerial quality in deliverables. For a software product
structure. • Individual Responsibilities: Each or service, an SQA plan will be used in
individual present in the organization must conjunction with the typical development,
have some responsibilities that should be prototyping, design, production, and release
reviewed by the top management and each cycle. An SQA plan will include several
individual present in the system must take this components, such as purpose, references,
seriously. • Quality System Activities: The configuration and management, tools, code
activities which each quality system must have controls, testing methodology, problem
been ◦ Project Auditing. ◦ Review of the reporting and remedial measures, and more,
quality system.◦ It helps in the development for easy documentation and referencing.
of methods and guidelines.
Software Quality Assurance (SQA) Major Software Quality Assurance (SQA) Software testing standards are a set of What is Software Engineering?
SQA process Specific quality assurance and Activities guidelines and principles used to define and Software Engineering is the process of
quality control tasks Effective software 1 SQA Management Plan: Make a plan for how guide the process of software testing. These designing, developing, testing, and maintaining
engineering practice Control of all software you will carry out the SQA throughout the standards outline the strategies, procedures, software. It is a systematic and disciplined
work products and the changes made to them project. Think about which set of software methodologies, and best practices for testing approach to software development that aims
a procedure to ensure compliance with engineering activities are the best for project. software to ensure its quality, functionality, to create high-quality, reliable, and
software development standards check level of SQA team skills. and performance. They also provide a maintainable software. # Software
measurement and reporting mechanisms 2 Set The Check Points: SQA team should set foundation for creating and evaluating engineering includes a variety of techniques,
Elements of Software Quality Assurance (SQA) checkpoints. Evaluate the performance of the software testing processes, techniques, and tools, and methodologies, including
Standards: The IEEE, ISO, and other standards project on the basis of collected data on tools. Some common software testing requirements analysis, design, testing, and
organizations have produced a broad array of different check points. standards include ISO/IEC 29119, IEEE 829, maintenance. # It is a rapidly evolving field,
software engineering standards and related 3 Measure Change Impact: The changes for and ISO/IEC 9126. Adhering to these standards and new tools and technologies are constantly
documents. The job of SQA is to ensure that making the correction of an error sometimes can help organizations improve the being developed to improve the software
standards that have been adopted are re introduces more errors keep the measure of effectiveness and efficiency of their software development process. # By following the
followed and that all work products conform impact of change on project. Reset the new testing processes and ultimately deliver high- principles of software engineering and using
to them. change to check the compatibility of this fix quality software products to customers. the appropriate tools and methodologies,
1 Reviews and audits: Technical reviews are a with whole project. Here is a brief guide to some of the key software developers can create high-quality,
quality control activity performed by software 4 Multi testing Strategy: Do not depend on a elements of software testing standards: reliable, and maintainable software that meets
engineers for software engineers. Their intent single testing approach. When you have a lot of • Test planning: This is the process of defining the needs of its users. # Software Engineering
is to uncover errors. Audits are a type of review testing approaches available use them. the scope, objectives, and approach to is mainly used for large projects based on
performed by SQA personnel with the intent 5 Manage Good Relations: In the working software testing. • Test case development: This software systems rather than single programs
of ensuring that quality guidelines are environment managing good relations with is the process of creating test cases that will be or applications. # The main goal of Software
beingfollowed for software engineering work. other teams involved in the project used to test software. • Test execution: This is Engineering is to develop software
2. Testing: Software testing is a quality control development is mandatory. Bad relation of the process of running test cases against applications for improving quality, budget, and
function that has one primary goal—to find SQA team with programmers team will impact software. • Test analysis: This is the process of time efficiency. # Software Engineering
errors. The job of SQA is to ensure that testing directly and badly on project. Don’t play reviewing test results and identifying defects. ensures that the software that has to be built
is properly planned and efficiently conducted politics. • Test reporting: This is the process of should be consistent, correct, also on budget,
for primary goal of software. 6 Maintaining records and reports: communicating test results to stakeholders. on time, and within the required requirements.
3.Error/defect collection and analysis: SQA Comprehensively document and share all QA
collects and analyzes error and defect data to records, including test cases, defects, changes,
better understand how errors are introduced and cycles, for stakeholder awareness and Importance of Software Quality Assurance ITaxonomy of software techniques
and what software engineering activities are future reference. Plan Software Testing Techniques
best suited to eliminating them. 7 Reviews software engineering activities: The • Quality Standards and Guidelines: The SQA Software testing techniques are methods used
4.Change management: SQA ensures that SQA group identifies and documents the Plan lays out the requirements and guidelines to design and execute tests to evaluate
adequate change management practices processes. The group also verifies the to make sure the programme satisfies software applications. The following are
have been instituted. 5.Education: Every correctness of software product. predetermined standards for quality. common testing techniques: Manual testing –
software organization wants to improve its 8 Formalize deviation handling: Track and • Risk management: It is the process of Involves manual inspection and testing of the
software engineering practices. A key document software deviations meticulously. recognizing, evaluating and controlling risks in software by a human tester.Automated
contributor to improvement is education of Follow established procedures for handling order to reduce the possibility of errors and testing – Involves using software tools to
software engineers, their managers, and other variances. other problems with quality. automate the testing process.Functional
stakeholders. The SQA organization takes the • Standardization and Consistency: The testing – Tests the functional requirements of
lead in software process improvement which Software safety is an engineering discipline strategy guarantees consistent methods, the software to ensure they are met.Non-
is key proponent and sponsor of educational that aims to ensure that software, which is processes, and procedures, fostering a unified functional testing – Tests non-functional
programs. 6. Security management: SQA used in safety-related systems does not and well-structured approach to quality requirements such as performance, security,
ensures that appropriate process and contribute to any hazards such a system might assurance. and usability.Unit testing – Tests individual
technology are used to achieve software pose. There are numerous standards that • Customer Satisfaction: The SQA Plan helps to units or components of the software to ensure
security .7. Safety: SQA may be responsible for govern the way how safety-related software ensure that the finished product satisfies they are functioning as intended.Integration
assessing the impact of software failure and for should be developed and assured in various customer needs, which in turn increases testing – Tests the integration of different
initiating those steps required to reduce risk. domains. Most of them classify software overall customer satisfaction. components of the software to ensure they
8. Risk management: The SQA organization according to their criticality and propose • Resource optimization: It is the process of work together as a system.System testing –
ensures that risk management activities are techniques and measures that should be defining roles, responsibilities, and procedures Tests the complete software system to ensure
properly conducted and that risk-related employed during the development and in order to maximize resource utilization and it meets the specified requirements.
contingency plans have been established. assurance Goals • Functional safety is achieved minimize needless rework. Acceptance testing – Tests the software to
through engineering development to ensure • Early Issue Detection: SQA Plans help identify ensure it meets the customer’s or end-user’s
correct execution and behavior of software problems early on, which lowers the expense expectations.Regression testing – Tests the
Process Change Management functions as intended • Safety consistent with and work involved in fixing them software after changes or modifications have
When any software application/product goes mission requirements, is designed into the been made to ensure the changes have not
for any changes in an IT environment, it software in a timely, cost effective manner. Software Measurement and Metrics introduced new defects.Performance testing
undergoes a series of sequential processes as • On complex systems involving many Software Measurement: A measurement is a – Tests the software to determine its
follows: • Creating a request for change interactions safety-critical functionality should manifestation of the size, quantity, amount, or performance characteristics such as speed,
• Reviewing and assessing a request for change be identified and thoroughly analyzed before dimension of a particular attribute of a product scalability, and stability. Security testing –
• Planning the change • Testing the change deriving hazards and design safeguards for or process. Software measurement is a titrate Tests the software to identify vulnerabilities
• Creating a change proposal • Implementing mitigations. • Safety-critical functions lists and impute of a characteristic of a software and ensure it meets security requirements.
changes • Reviewing change performance preliminary hazards lists should be determined product or the software process. Exploratory testing – A type of testing where
• Closing the process proactively and influence the requirements Types of Software Metrics the tester actively explores the software to find
Importance of Change Management that will be implemented in software. 1 Product Metrics: Product metrics are used defects, without following a specific test plan.
• To improve performance • To increase • Contributing factors and root causes of faults to evaluate the state of the product, tracing Boundary value testing – Tests the software at
engagement • For enhancing innovation and resultant hazards associated with the risks and undercover prospective problem the boundaries of input values to identify any
• For including new technologies• For system and its software are identified, areas. The ability of the team to control quality defects.
implementing new requirements evaluated and eliminated or the risk reduced is evaluated. Examples include lines of code,
• To reduce cost to an acceptable level, throughout the cyclomatic complexity, code coverage, defect Product Quality and Process Quality
Source of Change lifecycle. • Reliance on administrative density, and code maintainability index. Product Quality: Means that the product is
There may be multiple reasons involved during procedures for hazard control is minimized. 2 Process Metrics: Process metrics pay according to the specifications gathered by
the development process for which certain particular attention to enhancing the long- Business Analyst AND is bug free.
changes are required to be implemented in the term process of the team or organization. Process Quality: Means the process adopted
product. These sources are as follows : These metrics are used to optimize the by the company to test the
• Business reorganization • New Market development process and maintenance application should be defined well enough
conditions • New equipment • Fixing any activities of software. Examples include effort that it covers all the aspect of the
bugs/errors • New customer needs variance, schedule variance, defect injection application.
• Performance or reliability improvement rate, and lead time. Product quality means we concentrate always
• Budgetary or scheduling constraints 3 Project Metrics: The project metrics final quality but in case of process quality we
Key points of Change Management describes the characteristic and execution of a set the process parameter.
• Reason for change • Result of change project. Examples include effort estimation A quality product must still meet those
• The portion to be changed • Person will accuracy, schedule deviation, cost variance, requirements, and it follows that a process
change • Risks involved in change • Alternative and productivity. Usually measures- • Number that's going to produce a quality product must
to change• Resources required for change of software developer• Staffing patterns over track them carefully. Process quality: is a team
• Relationship between changes the life cycle of software • Cost and schedule of quality, engineering, and business
• Productivity Advantages of Software Metrics management professionals helping
1 Reduction in cost or budget. 2 It helps to organizations rapidly improve. The product
identify the particular area for improvising. that conforms to final specification is product
3 It helps to increase the product quality. quality but the process that conforms to the
4 Managing the workloads and teams. process specifications to get quality product is
5 Reduction in overall time to produce the process quality.
product,.6 It helps to determine the Product quality deals with incoming material
complexity of the code and to test the code quality and controls the quality of the
with resources. 7 It helps in providing effective final product. Process quality means deals
planning, controlling and managing of the with process of documentation type like work
entire product. instruction, control plan etc.
Product quality deals with the given
specification of an individual product whereas
the process quality deals with the process
capability of the process that how much it can
be effective to produce the quality products.
Product quality is a one complete details and
analysis data and before customer give to
proper quality of material life depth of analysis
is known as product qualityProcess quality is a
instructions following the given diagram can
be following and inspection for process area or
manufacturing product can be approved and
to nextprocess move it is a process quality
What is a Test Case?
A test case is a defined format for software
testing required to check if a particular
application/software is working or not. A test
case consists of a certain set of conditions that
need to be checked to test an application or
software i.e. in more simple terms when
conditions are checked it checks if the
resultant output meets with the expected
output or not. A test case consists of various
parameters such as ID, condition, steps, input,
expected result, result, status, and remarks.
Parameters of a Test Case:
• Module Name: Subject or title that defines
the functionality of the test. • Test Case Id: A
unique identifier assigned to every single
condition in a test case. • Tester Name: The
name of the person who would be carrying out
the test. • Test scenario: The test scenario
provides a brief description to the tester, as in
providing a small overview to know about
what needs to be performed and the small
features, and components of the test. • Test
Case Description: The condition required to be
checked for a given software. for eg. Check if
only numbers validation is working or not for
an age input box. • Test Steps: Steps to be
performed for the checking of the condition.
• Prerequisite: The conditions required to be
fulfilled before the start of the test process.
• Test Priority: As the name suggests gives
priority to the test cases that had to be
performed first, or are more important and
that could be performed later. • Test Data: The
inputs to be taken while checking for the
conditions. • Test Expected Result: The output
which should be expected at the end of the
test. • Test parameters: Parameters assigned
to a particular test case. • Actual Result: The
output that is displayed at the end.
• Environment Information: The environment
in which the test is being performed, such as
the operating system, security information, the
software name, software version, etc. • Status:
The status of tests such as pass, fail, NA, etc.
• Comments: Remarks on the test regarding
the test for the betterment of the software.
When do we Write Test Cases?
Test cases are written in different situations:
• Before development: Test cases could be
written before the actual coding as that would
help to identify the requirement of the
product/software and carry out the test later
when the product/software gets developed.
• After development: Test cases are also
written directly after coming up with a
product/software or after developing the
feature but before the launching of a
product/software as needed to test the
working of that particular feature. • During
development: Test cases are sometimes
written during the development time,
parallelly. so whenever a part of the
module/software gets developed it gets tested
as well. • Unit Test case: Here we are only
checking if the username validates at least for
the length of eight characters.