The document discusses the challenges of implementing risk-based testing for complex software systems. It explains that while risk-based testing aims to prioritize tests based on risk, determining the appropriate test scope for changes in a complex system with many configurations and dependencies is difficult. The key challenges identified are understanding the system dependencies, collecting relevant data over time to learn how changes impact the system, and ensuring tests and manual exploratory testing sessions adequately capture this information. While risk analysis, automated testing frameworks, and exploratory testing can help guide scope selection, it remains a complex problem with no simple solution.
Whether you are new to testing or looking for a better way to organize your test practices and processes, the Systematic Test and Evaluation Process (STEP™) offers a flexible approach to help you and your team succeed. Dale Perry describes this risk-based framework—applicable to any development lifecycle model—to help you make critical testing decisions earlier and with more confidence. The STEP™ approach helps you decide how to focus your testing effort, what elements and areas to test, and how to organize test designs and documentation. Learn the fundamentals of test analysis and how to develop an inventory of test objectives to help prioritize your testing efforts. Discover how to translate these objectives into a concrete strategy for designing and developing tests. With a prioritized inventory and focused test architecture, you will be able to create test cases, execute the resulting tests, and accurately report on the quality of your application and the effectiveness of your testing. Take back a proven approach to organize your testing efforts and new ways to add more value to your project and organization.
software testing, Regression testing meaning,
requirement of regression testing,
techniques of regression testing:- hybrid, retest all, Test case prioritization, Regression test selection.
pros and cons of using regression testing,
tools for regression testing :-
Relational Functional Tester(RFT)
Quick Test Professional (QTP)
selenium
Whether you are new to testing or looking for a better way to organize your test practices and processes, the Systematic Test and Evaluation Process (STEP™) offers a flexible approach to help you and your team succeed. Dale Perry describes this risk-based framework—applicable to any development lifecycle model—to help you make critical testing decisions earlier and with more confidence. The STEP™ approach helps you decide how to focus your testing effort, what elements and areas to test, and how to organize test designs and documentation. Learn the fundamentals of test analysis and how to develop an inventory of test objectives to help prioritize your testing efforts. Discover how to translate these objectives into a concrete strategy for designing and developing tests. With a prioritized inventory and focused test architecture, you will be able to create test cases, execute the resulting tests, and accurately report on the quality of your application and the effectiveness of your testing. Take back a proven approach to organize your testing efforts and new ways to add more value to your project and organization.
software testing, Regression testing meaning,
requirement of regression testing,
techniques of regression testing:- hybrid, retest all, Test case prioritization, Regression test selection.
pros and cons of using regression testing,
tools for regression testing :-
Relational Functional Tester(RFT)
Quick Test Professional (QTP)
selenium
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
INTRODUCTION TO ISTQB FOUNDATION LEVEL - CTFLRahul R Pandya
This Slideshare will give you the basics introduction of the ISTQB Foundation level testing certification.
ISTQB stands for the “International Software Testing Qualifications Board.”
ISTQB Certification is a universally acknowledged programming testing affirmation that is directed online by its Member Boards through a testing Exam Provider.
Software test management overview for managersTJamesLeDoux
Software test management presentation given to the senior management of several Fortune 100 companies to aid them in planning their software development management efforts.
Non-functional testing is the testing of a software application or system for its non-functional requirements: the way a system operates, rather than specific behaviours of that system.
Testbytes is a community of software testers who are passionate about quality and love to test. We develop an in-depth understanding of the applications under test and include software testing strategies that deliver quantifiable results.
In short, we help in building incredible software.
Software Test Metrics and MeasurementsDavis Thomas
Explains in detail with example about calculation of -
1.Percentage Test cases Executed [Test Coverage]
2.Percentage Test cases not executed
3.Percentage Test cases Passed
4.Percentage Test cases Failed
5.Percentage Test cases BLOCKED/Deferred
6.Defect Density
7.Defect Removal Efficiency (DRE)
8.Defect Leakage
9.Defect Rejection ratio [Invalid bug ratio]
10.Percentage of Critical defects
11.Percentage of High defects
12.Percentage of Medium defects
13.Percentage of Low/Lowest defects
Quality, quality concepts
Software Quality Assurance
Software Reviews
Formal Technical Reviews
SQA Group Plan
ISO 9000, 9001
Example
Internal and external attributes
Test Case Design Techniques as chapter 4 of ISTQB Foundation. Topics included are Equivalence Partition, Boundary Value Analysis, State Transition Testing, Decision Table Testing, Use Case Testing, Statement Coverage, Decision Coverage, Error Guessing, Exploratory Testing, Checklist Based Testing
YouTube Link: https://youtu.be/S2_AJP9Oeg0
**Test Automation Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **
This Edureka PPT on "Test Plan in Software Testing" will give you in-depth knowledge on how to create a Test Plan in Software Testing and why it is important. The following are the topics covered in the session:
Software Testing Documentation
What is Test Plan?
Benefits of Using Test Plan
Types of Test Plan
How to Write a Test Plan?
Test Plan Template / Test Plan Document
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
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
INTRODUCTION TO ISTQB FOUNDATION LEVEL - CTFLRahul R Pandya
This Slideshare will give you the basics introduction of the ISTQB Foundation level testing certification.
ISTQB stands for the “International Software Testing Qualifications Board.”
ISTQB Certification is a universally acknowledged programming testing affirmation that is directed online by its Member Boards through a testing Exam Provider.
Software test management overview for managersTJamesLeDoux
Software test management presentation given to the senior management of several Fortune 100 companies to aid them in planning their software development management efforts.
Non-functional testing is the testing of a software application or system for its non-functional requirements: the way a system operates, rather than specific behaviours of that system.
Testbytes is a community of software testers who are passionate about quality and love to test. We develop an in-depth understanding of the applications under test and include software testing strategies that deliver quantifiable results.
In short, we help in building incredible software.
Software Test Metrics and MeasurementsDavis Thomas
Explains in detail with example about calculation of -
1.Percentage Test cases Executed [Test Coverage]
2.Percentage Test cases not executed
3.Percentage Test cases Passed
4.Percentage Test cases Failed
5.Percentage Test cases BLOCKED/Deferred
6.Defect Density
7.Defect Removal Efficiency (DRE)
8.Defect Leakage
9.Defect Rejection ratio [Invalid bug ratio]
10.Percentage of Critical defects
11.Percentage of High defects
12.Percentage of Medium defects
13.Percentage of Low/Lowest defects
Quality, quality concepts
Software Quality Assurance
Software Reviews
Formal Technical Reviews
SQA Group Plan
ISO 9000, 9001
Example
Internal and external attributes
Test Case Design Techniques as chapter 4 of ISTQB Foundation. Topics included are Equivalence Partition, Boundary Value Analysis, State Transition Testing, Decision Table Testing, Use Case Testing, Statement Coverage, Decision Coverage, Error Guessing, Exploratory Testing, Checklist Based Testing
YouTube Link: https://youtu.be/S2_AJP9Oeg0
**Test Automation Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **
This Edureka PPT on "Test Plan in Software Testing" will give you in-depth knowledge on how to create a Test Plan in Software Testing and why it is important. The following are the topics covered in the session:
Software Testing Documentation
What is Test Plan?
Benefits of Using Test Plan
Types of Test Plan
How to Write a Test Plan?
Test Plan Template / Test Plan Document
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Risk-based testing is a commonly-performed technique for prioritizing tests that must be performed in a short time frame. However, this technique isn't perfect and has some risks in itself. This presentation lists 13 ways a tester can be "fooled by risk."
How to deal with bad requirements of softwareBugRaptors
The Software Development Life Cycle (SDLC) starts from requirement gathering and analysis of the requirements. Before freezing requirements a complete analysis is mandatory both by BA and QA team. Always remember, a bad or poorly analyzed requirement can block the road for a good Software Product.
Bringing the hacker mindset into requirements and testing by Eapen Thomas and...QA or the Highway
Security requirements and testing are different from functional requirements & testing. In security testing the goal is to find out if the system can stand up to abusers. So the test scenarios may not be realistic from a common user standpoint. Being able to think of these requirements requires a different mindset than that used for traditional functional requirements. Anticipating and planning for these scenarios is vital for security testing.
Security requirements and testing requires an adversarial mindset, a “what if” mindset, i.e., the same one hackers use to break into systems.
Methods for Validating and Testing Software Requirements (lecture slides)Dagmar Monett
Online lecture at the School of Computer Science, University of Hertfordshire, Hatfield, UK, as part of the 11th Europe Week from 2nd to 6th March 2015.
Implementation of Risk-Based Approach for Quality & Cost OptimizationSonata Software
As a practiced trend in IT projects, Testing is performed only towards the end of a project. Teams
dedicate hours to test possible risks and flaws after the project is ready to run. As software testing at
this level invites several last minute modifications that can cause discomfort, or sometimes even refute
the very concept of the project, it has become the need of the hour to come up with a way to ensure
detection and reduction of risks, at an early stage of the project. Risk-Based Testing, or RBT as referred
to in this paper, is a procedure in software testing which is used to prioritize the development and
execution of tests based upon the impact and likelihood of failure of the functionality or aspect being
tested based on existing patterns of risk.
Through this testing technique, a software test
engineer can now select tests based on risk even before the initiation of the projectThis paper outlines the Risk-Based Testing approach and describes how Risk-Based Testing can positively impact the development life-cycle based on business-oriented factors, offering organizations an actionable plan for starting a Risk-Based Testing approach for projects.
The key to successful testing is effective and timely planning. Rick Craig introduces proven test planning methods and techniques, including the Master Test Plan and level-specific test plans for acceptance, system, integration, and unit testing. Rick explains how to customize an IEEE-829-style test plan and test summary report to fit your organization’s needs. Learn how to manage test activities, estimate test efforts, and achieve buy-in. Discover a practical risk analysis technique to prioritize your testing and become more effective with limited resources. Rick offers test measurement and reporting recommendations for monitoring the testing process. Discover new methods and develop renewed energy for taking your organization’s test management to the next level.
Performance Testing in the Agile LifecycleTechWell
Traditional large scale end-of-cycle performance tests served enterprises well in the waterfall era. However, as organizations transition to agile development models, many find their tried and true approach to performance testing—and their performance testing resources—becoming somewhat irrelevant. The strict requirements and lengthy durations just don’t fit in the context of an agile cycle. Additionally, investigating system performance at the end of the development effort misses out on the early stage feedback offered by an agile approach. And it’s more important than ever that today’s agile-built systems perform. So how can agile organizations ensure optimum performance of their business critical systems? Lee Barnes discusses why agile teams need to change their thinking about performance from a narrow focus on testing to a broader focus on analysis—from a people, process and technology perspective. Take back techniques for shifting your performance testing/analysis earlier in the development cycle and extracting performance data that is immediately actionable.
Continuous Performance Testing in DevOps - Lee BarnesQA or the Highway
Stop trying to cram traditional “big bang” end of cycle performance tests into your DevOps pipeline! This talk will show you how to implement performance testing and analysis activities that work with your DevOps practices instead of against them.
As cloud computing becomes of strategic importance in the enterprise, part of the solution is no longer on-premise but in the cloud, adding a layer of complexity. Edwin Chan demystifies performance testing of cloud systems and applications by addressing the following key questions: Is performance testing of cloud systems fundamentally different from testing on-premises applications? What are the best practices for performance testing of both cloud and on-premises systems? Performance testing of cloud systems is essentially the same as that of its on-premises counterpart with the exception of the key consideration of network latency. After clearing common misconceptions, Edwin shares the hot topic best practices—adopting an agile/lean methodology, conducting early performance testing, and automating the injection of test data. Discuss the challenges the testing team faces in these days of disruptive and fast-paced technology changes. Take back and apply some of the best practices that fit your organization’s need.
Curiosity and Coforge present - Oracle FLEXCUBE: De-risk upgrades and migrati...Curiosity Software Ireland
This live webinar took place on July 13th 2021. Watch the session on demand: https://resources.curiositysoftware.ie/oracle-flexcube-testing-webinar
Banks who rely on Oracle FLEXCUBE for their agile core banking infrastructure need agile testing practices which match the speed of FLEXCUBE innovation.
Too often, manual testing processes combine with a lack of niche FLEXCUBE knowledge, delaying upgrades and migrations in core banking. The time spent creating, executing, and maintaining complex FLEXCUBE tests then forces banks to make the undesirable choice between:
1. Updating core banking infrastructure at the risk of costly bugs;
2. Letting core banking systems fall behind the latest innovation and security updates.
The winners in this situation are the banks and fintech start-ups who can keep up with the latest in core banking innovation.
This webinar will set out how banks with substantial legacy infrastructure can keep pace with core banking innovation. It will showcase how risk-based test generation allows banks to enjoy all the innovation of new FLEXCUBE releases, while protecting custom FLEXCUBE implementations from bugs, downtime, and data breaches. You will discover how:
Model-based test automation generates optimised FLEXCUBE tests and data from flowcharts that are quick-to-build and easy-to-maintain.
The intuitive flowcharts reduce the need for niche FLEXCUBE knowledge in-house, visually assembling test scenarios from reusable components, UI scans, and imported tests.
Automated test generation creates rigorous tests for custom FLEXCUBE implementations, rigorously testing without delaying critical FLEXCUBE upgrades and migrations.
The visual flows maintain living documentation of core banking processes, enabling business analysts, testers, and developers to innovate core banking systems with confidence.
Watch the webinar on demand - https://resources.curiositysoftware.ie/oracle-flexcube-testing-webinar
Pay pal paypal continuous performance as a self-service with fully-automated...Dynatrace
PayPal's ongoing leadership as an industry innovator requires faster development cycles and increased adoption of continuous testing practices. For special efforts, the development teams needed more frequent feedback about application performance, scalability limitations and variances between builds. Accelerating the frequency of performance simulations would help increase the rate of innovation and improve the quality of code delivered to production.
In this session we'll review some the automation techniques that helped PayPal Credit increase testing feedback from a monthly effort to a nearly-continuous daily activity. We'll spend time looking at the benefits of a fully-automated, actionable performance feedback loop that delivers performance feedback to developers in hours rather than weeks or months. Additionally, we will take a closer look at how these changes impacted the culture of development and operations, improving both the quality of critical thinking about performance and the value delivered back to the business.
This "Secret Sauce" session will include conceptual learnings and hands-on demonstration:
- What a continuous performance environment looks like and the benefits it brings to your DevOps team
- How to create a parallel pipeline for on-demand performance feedback using JIRA, Rundeck, JMeter and Dynatrace
- Where and how to leverage performance feedback to optimize flow
- How to get engineers on-board and excited about building better performant code
This is a case study on conducting User Acceptance Testing (UAT) of a complex B2E software application. Involved testing of several critical HR and Payroll modules.
A presentation about how to categorize different test activities, by defining what attributes describe them. This is then used to improve planning, and finding redundancy and gaps.
Why do customers migrate to cloud? The answer is complex on the one hand, but the main benefits are pretty simple on the other one.
1.There is no need to take care about hardware availability, reliability and maintenance.
2.Relatively stable performance of hosted applications.
3.Easy backup process of the whole system or its part.
This information can be found in almost any marketing prospect on Cloud Computing and Cloud Hosting.
This document is centered on less obvious concepts.
It reveals the areas that you should care about before and during migration to a Cloud environment and explains why you should do that.
Introduction
Continuous Performance Testing: The New StandardTechWell
In the past several years the software development lifecycle has changed significantly with high-speed software releases, shared application services, and platform virtualization. The traditional performance assurance approach of pre-release testing does not address these innovations. To maintain confidence in acceptable performance in production, pre-release testing must be augmented with in-production performance monitoring. Obbie Pet describes three types of monitors—performance, resource, and VM platform—and three critical metrics fundamental to isolating performance problems—response time, transaction rate, and error rate. Obbie reviews techniques to acquire and interpret these metrics, and describes how to develop a continuous performance monitoring process. In conjunction with pre-release testing, this monitoring can be woven into a single integrated process, offering a best bet in assuring performance in today’s development world. Take away this integrated process for consideration in your own shop.
Approaches to unraveling a complex test problemJohan Hoberg
When testing a complex system you are often faced with complex test problems. Cause and effect cannot be deduced in advance, only in retrospect.
According to the Cynefin framework, the general approach to tackle complexity is probe-sense-respond. Try something, analyze the outcome, and based on that outcome, try something else. This is the basis of all my approaches to begin unraveling complex test problems. But how do I select my test scope for a specific complex test problem?
In this article I outline why I believe it should not be mandatory for all code changes to go through QA before they are merged to a master branch and released.
Quality Information Coverage - A QI ConceptJohan Hoberg
When I talk about Quality Intelligence, an important part of the QI concept is transparency and visibility. Providing the right quality intelligence to the right stakeholders at the right time. When doing this I find it valuable to talk about “Quality Information Coverage”, a concept which I am going to expand on in this article.
The Bug Backlog - An Evergrowing MountainJohan Hoberg
If you are part of a development team working on a game, and you are working in some kind of Agile way, you most likely have a bug backlog, or at least bugs as part of some kind of backlog. The bug backlog looks very different during different stages of the game development cycle - it starts out empty, and then as features and complexity is added, it grows. And in most cases it never stops growing.
One of the most important aspects of Quality Intelligence is transparency and visibility. Intelligence is worthless if it does not affect the decision-making process in some way. If the intelligence is not available to the people involved in the decision-making process, then it will have no effect.
Quality Intelligence - what does the term stand for in theory and in practice? This is a follow up to my previous presentation about why I think QI should replace QA as the acronym of choice.
This presentation outlines principles and thoughts that guide me in my pursuit of creating high quality complex software
I will also try to give concrete examples at the end of the presentation of what this looks like in practice
When dealing with complexity you have to be aware of that cause and effect can only be deduced in retrospect. With this in mind, success or failure, is not completely in our hands when we are developing complex products. What is in our hands is the commitment we show, the ownership we take, and the effort we put in. That is what we should celebrate.
Moving from scripted regression testing to exploratory testingJohan Hoberg
An article I wrote for the King Tech Blog about our move from scripted to exploratory testing.
https://techblog.king.com/moving-from-scripted-regression-testing-to-exploratory-testing/
In this article I will explore what I believe is a good foundation for building high quality software. I will cover a wide array of different topics which have in common that I believe they all contribute to this goal.
In this article I will explore why I think that deadlines should never be communicated to the development teams, and why all deadlines are basically meaningless anyway.
Do we really need game testers in development teams? What is it that defines the core competence of a tester, and does this competence add any value to the development team?
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
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.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
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.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
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.
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.
2. Introduction
• Johan Hoberg
• Sony Mobile
▫ ~10 years
▫ Tester, Test Team Leader, Test Architect
• This is a presentation of my experiences
of risk-based testing
2
2013-09-27
PA1
Confidential
3. Definition
• Risk-based testing (RBT) is a type of software
testing that prioritizes the tests of features and
functions based on the risk of their failure - a
function of their importance and likelihood or
impact of failure.
(http://en.wikipedia.org/wiki/Risk-based_testing)
3
2013-09-27
PA1
Confidential
4. The Devil is in the Details
• Refers to a catch or mysterious element hidden in
the details
• Derives from “God is in the Details”
▫ Generally attributed to Gustave Flaubert (1821–1880)
• It is easy to ask for efficient, risk-based testing
• It is much more difficult to actually do it well
4
2013-09-27
PA1
Confidential
5. System Under Test
Configuration 1
Configuration 2
Android Gingerbread Generic
Configuration 3
Android Gingerbread Customer A
Android Gingerbread Customer B
Android Jellybean Generic
Product X
Product Y
Android Jellybean Customer A
Android Jellybean Customer B
5
2013-09-27
PA1
Confidential
7. Changes in the System
• There is a change introduced somewhere in the
system
• Could be a bug fix, a change request, a new
feature, refactoring, etc.
7
2013-09-27
PA1
Confidential
8. Scope Selection
• Do you run every available test on every possible
configuration of the system and verify all
interoperability?
• A smart scope is necessary to make it containable
• We must be able to reuse test results between
products, configuration, and branches
8
2013-09-27
PA1
Confidential
9. Scope Selection based on Risk
Change
Introduced
9
2013-09-27
PA1
System Impact
Risk-based
Scope
Confidential
10. Complex vs. Complicated
• Complicated
▫ Opposite of simple
▫ Containing intricately combined or involved parts
• Complex
▫ Opposite of predictable?
▫ This adjective means having parts so
interconnected as to make the whole perplexing
10
2013-09-27
PA1
Confidential
11. Complex System
• A complex system is difficult to predict
• It is therefore difficult to plan which actions to
take to mitigate different outcomes
• It is difficult to plan which tests to run to cover
all potentially relevant defects
11
2013-09-27
PA1
Confidential
13. Example
• A change is introduced into the Display Driver
component – What do I need to test?
▫ Camera?
▫ Interoperability with TV and similar devices?
▫ Multimedia
View pictures, video etc.?
▫ All UI testing?
▫ Other parts of the system?
13
2013-09-27
PA1
Confidential
14. Reduce Complexity
• Risk Analysis
• Automated Test Framework
• Early Exploratory Testing
14
2013-09-27
PA1
Confidential
15. Risk Analysis – Input Data
Feature & Hardware Delta
Historical Data
Code Changes
System Dependencies &
Architecture
15
2013-09-27
PA1
•Easy to obtain
•Might give us an indication on
where to start looking, but can
often give false confidence in
scope selection, especially
when it comes to E2E system
test
•Hard to obtain
Confidential
16. Risk Analysis – Risk Model
Risk
Identification
Probability
Severity (S)
Occurrence (O)
Detection (D)
16
2013-09-27
PA1
Consequence
Mitigation
Plan
Risk Priority Number (RPN) = S*O*D
Confidential
17. Risk Analysis - Complex vs. Complicated
Risk analysis of
whole system is
complex
17
2013-09-27
PA1
Risk analysis of
sufficiently small
part is more
complicated than
complex
Confidential
18. Risk Analysis Database
• If each function performs risk analysis on their
components and enters risks in a database this
information could be used on system level to get
better understanding of impact of specific
changes
• Requires a uniform way of handing risk
information
18
2013-09-27
PA1
Confidential
19. Problems?
• We can get a lot of data that will help us select a
scope – but ultimately we will introduce a lot of risk
if we do not know how the system is designed, and
how different components depend on each other
• To get a complete dependency map of the whole
system requires not only a good risk-handling
infrastructure, but a common effort from a lot of
people
19
2013-09-27
PA1
Confidential
21. Automated Test Framework
Change + Basic
Risk Analysis
Automated Test
Execution
21
Scope Setting
Test Results
Analysis
2013-09-27
PA1
Test Execution
Confidential
22. Automated Test Framework
Change
Automated Tests
Executed
Better understanding of
System Dependencies
22
2013-09-27
PA1
Failed Tests
Investigated
Change in component
mapped towards failed tests
in other components
Confidential
23. Self-learning System
• Over time you will have more and more
information about how different changes impact
the system
• Map code changes to failed tests
• This impact map can further help you
set an efficient scope
23
2013-09-27
PA1
Confidential
24. Continuous Integration
• The more code changes we have and the more
isolated these code changes are, the easier it is to
create the impact map
• If you only have one integration per month, with
thousands of lines of code changed in different
parts of the system, it will be difficult to draw
conclusions
24
2013-09-27
PA1
Confidential
25. Problems?
• The information value you receive is dependant
on how good the tests are
• Dependency graph grows over time – in the
beginning there is very little data
25
2013-09-27
PA1
Confidential
26. Early Exploratory Testing
Change + Basic
Risk Analysis
Exploratory
Testing
26
Scope Setting
Test Results
Analysis
2013-09-27
PA1
Test Execution
Confidential
27. Codifying Experience
• How do you transfer the knowledge gained from
one tester to the other?
• The understanding about impact and
dependencies we gain from performing
exploratory testing must be stored in a way
which makes it accessible to other testers for
their risk-based scope selections
27
2013-09-27
PA1
Confidential
28. Manual Dependency Map
• After each exploratory session it is possible to
add information to a dependency map, where
you indicate which changes were made, and
what impact those changes had
• It needs to be done in a way which is quick and
easy, otherwise it will not be done at all
28
2013-09-27
PA1
Confidential
29. Problems?
• Additional time might be needed before testers
get experience with the new process
• It will be more difficult to time plan activity
before early exploratory testing is done – this
can cause problems with test/project leaders and
managers
• It requires skilled testers
29
2013-09-27
PA1
Confidential
30. Final thoughts
• Every risk-based scope introduces risk – our
goal is to eliminate any unnecessary risk
• Without skilled testers to write good automated
tests or perform exploratory testing it becomes
very difficult without a very intricate risk/impact
framework
30
2013-09-27
PA1
Confidential
31. Conclusion
• It is very difficult to perform riskbased testing for a large, complex
system
• It is very easy to ask someone else to
reduce their test scope by
introducing risk-based testing
31
2013-09-27
PA1
Confidential