The document outlines topics related to quality control engineering and software testing. It discusses key concepts like the software development lifecycle (SDLC), common SDLC models, software quality control, verification and validation, software bugs, and qualifications for testers. It also covers the quality control lifecycle, test planning, requirements verification techniques, and test design techniques like equivalence partitioning and boundary value analysis.
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
Static testing is a software testing method that involves examination of program's code and its associated documentation but does not require the program to be executed.
Static Testing Techniques
Informal Reviews
Formal Reviews
Technical Reviews
Walk Through
Inspection Process
Static Code Review
Software testing is the process of evaluation a software item to detect differences between given input and expected output. Also to assess the feature of A software item. Testing assesses the quality of the product. Software testing is a process that should be done during the development process. In other words software testing is a verification and validation process.
Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to the process of executing a program or application with the intent of finding software bugs (errors or other defects).
Software testing can be stated as the process of validating and verifying that a computer program/application/product:
• meets the requirements that guided its design and development,
• works as expected,
• can be implemented with the same characteristics,
• and satisfies the needs of stakeholders.
Software Development Process Cycle:-
PLAN (P): Device a plan. Define your objective and determine the strategy and supporting methods required to achieve that objective.
DO (D): Execute the plan. Create the conditions and perform the necessary training to execute the plan.
CHECK (C): Check the results. Check to determine whether work is progressing according to the plan and whether the results are obtained.
ACTION (A): Take the necessary and appropriate action if checkup reveals that the work is not being performed according to plan or not as anticipated.
A brief that includes the following:
- Software Testing
- Quality Assurance
- Quality Control
- Types of Testing
- Levels of Software Testing
- Types of Performance Testing
- API
- Verification & Validation
- Test Plan & Testing Strategy
- Agile & Waterfall
- Software Development Life Cycle
- Career Path
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
software testing is necessary to make sure the product or application is defect free, as per customer specifications. Software testing identifies fault whose removal increases the software Quality and Increases the software reliability.Testing effort is directly proportional to the complexity of the program.
This ppt is done by my dear classmate Sap, almost each ppt I have uploaded is copied from net and other sources.I hope this will b a little useful for students..
Running, improving & maintaining a site in the real worldDavid Voyles
How to build and deploy an ASP.NET applicaton. This talk covers how to scale your applications using Azure
This entire series can be found here: http://www.davevoyles.com/slides-and-code-for-my-asp-net-presentation/
Static testing is a software testing method that involves examination of program's code and its associated documentation but does not require the program to be executed.
Static Testing Techniques
Informal Reviews
Formal Reviews
Technical Reviews
Walk Through
Inspection Process
Static Code Review
Software testing is the process of evaluation a software item to detect differences between given input and expected output. Also to assess the feature of A software item. Testing assesses the quality of the product. Software testing is a process that should be done during the development process. In other words software testing is a verification and validation process.
Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to the process of executing a program or application with the intent of finding software bugs (errors or other defects).
Software testing can be stated as the process of validating and verifying that a computer program/application/product:
• meets the requirements that guided its design and development,
• works as expected,
• can be implemented with the same characteristics,
• and satisfies the needs of stakeholders.
Software Development Process Cycle:-
PLAN (P): Device a plan. Define your objective and determine the strategy and supporting methods required to achieve that objective.
DO (D): Execute the plan. Create the conditions and perform the necessary training to execute the plan.
CHECK (C): Check the results. Check to determine whether work is progressing according to the plan and whether the results are obtained.
ACTION (A): Take the necessary and appropriate action if checkup reveals that the work is not being performed according to plan or not as anticipated.
A brief that includes the following:
- Software Testing
- Quality Assurance
- Quality Control
- Types of Testing
- Levels of Software Testing
- Types of Performance Testing
- API
- Verification & Validation
- Test Plan & Testing Strategy
- Agile & Waterfall
- Software Development Life Cycle
- Career Path
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
software testing is necessary to make sure the product or application is defect free, as per customer specifications. Software testing identifies fault whose removal increases the software Quality and Increases the software reliability.Testing effort is directly proportional to the complexity of the program.
This ppt is done by my dear classmate Sap, almost each ppt I have uploaded is copied from net and other sources.I hope this will b a little useful for students..
Running, improving & maintaining a site in the real worldDavid Voyles
How to build and deploy an ASP.NET applicaton. This talk covers how to scale your applications using Azure
This entire series can be found here: http://www.davevoyles.com/slides-and-code-for-my-asp-net-presentation/
Lecture 7 Software Engineering and Design User Interface Design op205
3F6 Software Engineering and Design, February 2012, lecture slides 7, User Interface Design, Dr Elena Punskaya, Cambridge University Engineering Department
This is Prateek Mishra from Ramaiah institute of management studies, Bangalore and the following presentation gives an overview of launch of a hypothetical product into the market.
A Research Study on importance of Testing and Quality Assurance in Software D...Sehrish Asif
A Research Study on importance of Testing and Quality Assurance in Software Development Life Cycle (SDLC) Models & Quality Assurance for Product Development using Agile & A Software Quality Framework for Mobile Application Testing
Types of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating system
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
2. 1. Introduction to Software Engineering
2. Introduction to Quality Control Engineering
3. Quality Control Lifecycle During the SDLC
4. Test Planning and Management
5. How to Verify the Software Requirements
6. Effective Test Design Techniques
7. How to Create Effective Test Cases
8. Non-functional Testing Techniques
9. Test Reporting and Monitoring
10. Test Time Estimation and Defects Seeding
•2
4. What is Software Engineering?
Software engineering is the application
of a systematic and quantifiable
approach to the design, development,
and maintenance of software.
•4
Part 1: Introduction to Software Engineering
5. What is the SDLC Model ?
“Software development life cycle” model
describe phases of the software cycle
and the order in which those phases are
executed.
There are many models, and many
companies adopt their own, but all have
similar patterns or references.
•5
Part 1: Introduction to Software Engineering
6. What are the common SDLC Models ?
1. Big Bang
2. Code and Fix
3. Waterfall
4. Iterative
5. V-model
Note: There are many other models, and many
companies adopt their own, but most models are
inherited from the above listed models.
•6
Part 1: Introduction to Software Engineering
7. 1. Big-Bang Model :
The Approach
People+Money+Energy=Perfect
Software or Nothing!
Advantages
Simple, needs less planning, less
formal development process
Disadvantages
No formal testing activities, hard to
manage and monitor, risky
•7
8. 2. Code and Fix Model :
The Approach
Informal specification loop of code and
fix till enough-is-enough decision
Release
Advantages
Little planning and documentation
work
Disadvantages
Hard to manage the testing and control the
quality
•8
9. 3. Waterfall Model :
The Approach
Discrete phases, a review after each
phase will decide to move next or stay
at this phase till it’s ready.
Advantages
Easy to test (clear requirements), easy
to manage and monitor
Disadvantages
High bugs fixing and changes cost, the
customer has minimal involvement
during the project
•9
10. 4. Iterative Model :
The Approach
Dividing the project into builds, each build
can be executed by waterfall model.
Advantages
Easy to test, customer is tightly
Involved, change cost is low.
Disadvantages
Time consuming.
(C) 2015, Quality Partners™ •10
11. 5. V- Model :
The Approach
For every single phase in the development
cycle there is a directly associated testing
phase. It is an extension of the waterfall.
Advantages
Testing is exist in every phase.
Defects are detected early
Disadvantages
Time consuming.
(C) 2015, Quality Partners™ •11
13. What is Software Quality Control (QC)?
•13
QC is the set of procedures used by organizations to
ensure that a software product will meet its quality
goals at the best value to the customer, and to
continually improve the organization’s ability to
produce software products in the future.
Software quality control refers to specified functional
requirements as well as non-functional requirements.
These specified procedures and outlined requirements
leads to the idea of Verification and Validation and
software testing.
14. What is Software Testing?
•14
A quality control activity aimed at
evaluating a software item against the
given system requirements.
This includes, but is not limited to, the
process of executing a program or
application with the intent of finding
software bugs.
Testing is a QC activity.
15. What is the Verification and Validation (V&V)?
•15
Verification: Confirming that something
(software) meets its specification.
Validation: Confirming that it meets the
user’s requirements.
The two major V&V activities are reviews,
and testing.
Testing is part of the V&V activities.
16. What is the Software ‘Bug’ ?
•16
Things the software does that while it
is not supposed to do, or
something the software doesn't while
it is supposed to.
17. Why Does Software Have Bugs ?
•17
• Miscommunication or no communication.
• Programming errors.
• Changing requirements.
• Time pressures.
• Ego.
• Poorly documented code.
• Software development tools.
18. What should the Tester do?
•18
1. Find the bugs
2. Find them early
3. Make sure that they have been fixed
19. What should not the Tester do?
•19
1. Fix the bugs!
2. Test with good faith!
3. Test with no requirements!
4. Not to report the obvious bugs!
5. Mock at others because of their bugs!
20. Main Qualifications for a Good Software Tester:
•20
• Be familiar with the SDLC being used.
• Have excellent attention to details.
• Have excellent communication skills (oral and written).
•Have strong personality and the ability to resist
pressures and say 'no' to other managers when quality
is insufficient.
•Be able to run meetings and keep them focused.
• Patient, Mature and diplomatic.
•Able to prioritize things and take critical decisions.
22. Testing Lifecycle main activities:
•22
1. Test Planning.
2. Test Analysis and Design.
3. Test Cases preparation.
4. Test Execution.
5. Test Reporting and Monitoring.
6. Bugs Reporting and Regression Testing.
7. Releasing Reporting.
8. User Acceptance Test Execution.
23. What are the Testing Lifecycle main activities?
(C) 2015, Quality Partners™ •23
Project Phase Team Deliverables QC Deliverables
Initiation
o Charter
o Scope
o Scope Verification
Planning o Project Plans
o QC Plan
o UAT Plan
Analysis
o SRS
o Use Cases
o SRS Verification
o Test Design
o Test Cases
Design
o Logic Design
o DB Design (ERD)
o GUI Design (Mockups)
o Design Verification
Development and
Testing
o Builds
o Functional and Non-Functional Testing
o Bugs Reports
o Final Release Report (FRR)
Delivery o Release o User Acceptance Test
25. What are the main components of the
good Test Plan?
•25
1. Introduction
1.1 Objectives
1.2 Scope (In scope and out of scope)
1.3 Roles & Responsibilities
1.4 Risks and Dependencies
1.5 Deliverables
2. Resources and Environment Requirements
2.1 Staffing and Training needs
2.2 Test Environment
2.3 Test Tools Requirements
2.4 Test Data
26. What are the main components of the
good test plan (cont’d)?
•26
3. Schedule
4. Test Monitoring and Reporting
5. Pass/Fail criteria
28. What is the Software Requirements Specification
Document?
•28
A software requirements specification (SRS)
is a comprehensive description of the
intended purpose and environment for
software under development. The SRS
document fully describes what the software
will do and how it will be expected to
perform.
29. The Characteristics of a good Requirements:
•29
1.Complete: The information covers all aspects of
this user function.
2.Consistent: The information for this user
function is internally consistent. There are no
conflicting statements.
3.Correct: The item is free from error.
4.Testable: Can the requirement be easily mapped
to specific test cases?
30. The Characteristics of a good Requirements :
(Cont’d)
•30
5. Specific :The item is exact and not vague;
there is a single interpretation; the meaning
of each item is understood; the specification
is easy to read. Use well defined terms and
enough information. Terms such as “High”,
“Low”, “Quick”, “Fast”, “Big” are not
acceptable.
6. Relevant: The item is related to the
problem and its solution.
7. Expressed in the User’s Language: All
requirements shall be expressed using no
design and in the users terminology.
31. The Characteristics of a good Requirements :
(Cont’d)
•31
8. Understandable: Difficult language
should not be used. Be clear. If formal
notations are used, make sure they are easy
to understand. Figures and tables are
helpful, but must be
explained.
9. Traceable: The item can be traced to its
origin in the problem environment. Also,
you must be able to find who originated a
requirement, who wrote it, what other
requirement does this one impact. This
information is important to make the
requirements usable and maintainable
(changeable).
32. The Characteristics of a good Requirements :
(Cont’d)
•32
10. Feasible: The item can be implemented with
the available techniques, tools, resources, and
personnel, and within the specified cost and
schedule constraints .
11. Free of unwarranted design details: The
requirements specifications are a statement of the
requirements that must be satisfied by the
problem solution, and they are not obscured by
proposed solution to the problem.
12. Prioritized: The priority of this item relative to
other requirements has been recorded.
34. What is Test Design document?
•34
Documentation specifying the details of the
test approach for a software feature or
combination of software features and identifying
the associated tests.
35. Test Design Techniques:
•35
1. Equivalence Partitioning
Equivalence partitioning is a test design method
for deriving test cases. In this method, classes of
input conditions called equivalence classes are
identified such that each member of the class
causes the same kind of processing and output to
occur. In this method, the tester identifies various
equivalence classes for partitioning. A class is a set
of input conditions that are is likely to be handled
the same way by the system. If the system were to
handle one case in the class erroneously, it would
handle all cases erroneously.
36. 1. Equivalence Partitioning (Cont’d):
•36
Why we should use Equivalence Partitioning
when designing test cases:
1. To reduce the number of test cases (by
avoiding the redundant cases), hence reducing
the testing time and cost.
2. To assure better test coverage, by testing all
input classes, hence improve the test efficiency.
37. Test Design Techniques:
•37
2. Boundary Values Analysis (BVA)
BVA is a methodology for designing test cases that
concentrates software testing effort on cases near
the limits of input ranges (the boundaries).
Note: BVA should be performed after identifying
the Equivalence Partitions of the software.
BVA generates test cases that highlight errors
better than equivalence partitioning. The trick is to
concentrate software testing efforts at the
extreme ends of the equivalence classes. At those
points when input values change from valid to
invalid errors are most likely to occur.
38. What are the main components of the Good
Test Design document?
•38
1. Scope
1.1 Features to be tested
1.2 Testing types to be applied
2. Test Cases Structure
3. Test Levels
4. Test Approach (Design Matrix)
5. Pass/Fail criteria
41. What are the characteristics of a good Test Case?
•41
Testability; easy to be executed
Use active case, do this, do that, system displays this,
does that
Simple, conversational language
Exact, consistent names of fields, not generic
Don’t explain Windows basics
10-15 steps or less. In the case of integration test case’s
try to provide references instead of explaining the
functionality again and again
Always update your test cases along with new build
43. Non-Functional Testing Types:
•43
Performance: the response time, utilization, and throughput
behavior of the system.
• Volume : Testing a software application for a certain data volume.
• Load : Creating demand on a system or device and measuring its response.
• Stress: Determine the stability of a given system or entity.
Compatibility : Measures how well the system operates on different operating
environment.
Recovery : Testing a system's ability to recover from a hardware or software
failure.
44. Non-Functional Testing Types (Cont’d):
•44
Availability: Is it available when and where I need to use it?
Efficiency: How few system resources does it consume?
Flexibility: How easy is it to add new features?
Maintainability: How easy it is to correct defects or make changes?
Portability: Can it be made to work on other platforms?
Security: The system’s ability to resist unauthorized attempts at usage or
behavior modification, while still providing service to authorized users.
Accessibility testing: measure how well the system interface serve users with
disabilities.
45. Non-Functional Testing Types (Cont’d):
•45
Reliability: How long does it run before causing a failure?
Reusability: How easily can we use components in other systems?
Usability: How easy is it for people to learn or to use?
Installability: How easy is it to correctly install the product.
47. How to write effective Bug report
•47
Report the pattern not an example.
Don’t describe what's wrong, only!
Be direct to the point (don’t tell a story!).
Report the bug, but not how to solve it.
Don’t mix between priority and severity.
Don’t use: CAPS, red letters, red circles, ‘!’ , ‘?’.
Don’t use your personal judgment.
Write with the fixer language, not with yours.
Minimize the options.
Don’t use the word ‘Sometimes’.
49. Bug Convergence
(C) 2015, Quality Partners™ •49
Bug convergence is the point at which the team
makes visible progress against the active bug count.
At bug convergence, the rate of bugs resolved
exceeds the rate of bugs found; thus the actual
number of active bugs decreases.
Because the bug count will still go up and down,
even after it starts its overall decline, bug
convergence usually manifests itself as a trend
rather than a fixed point in time.
50. Defects Seeding
•50
Defect seeding is a practice in which defects are
intentionally inserted into a program by one group
for detection by another group. The ratio of the
number of seeded defects detected to the total
number of defects seeded provides a rough idea of
the total number of unseeded defects that have
been detected.
IndigenousDefectsTotal =
( SeededDefectsPlanted / SeededDefectsFound ) *
IndigenousDefectsFound