The rise of micro-service architectures offers the promise of a more agile software development process.
Software systems will be made up of many collaborating components which are developed, deployed and operated by distributed teams and organizations. But how can we avoid a recurring configuration nightmare (c.f. DLL hell) and ensure that we benefit from the promised flexibility, rather than creating a fragile, distributed monolith?
Contract testing offers an excellent solution.
Participants will be able to:
- Explain why contract testing is critically important
- Describe how to incorporate contract testing in your development practices
- Show their team where they can get an introduction to the open source tool, Pact.
Micro-service delivery - without the pitfallsSeb Rose
The days of delivering a monolithic desktop application once a year on physical media are long gone. Today we expect continuous (or at least frequent) delivery of upgrades and security patches with zero downtime. To support this, more and more companies are moving to a distributed, cloud-based architecture of collaborating micro-services. But managing and testing an evolving of a micro-service ecosystem is not without it’s challenges.
In this session we’ll examine what can go wrong when organisations jump headfirst into micro-service architectures without understanding the potential pitfalls. You’ll leave with an understanding of the techniques and tooling necessary to reap the benefits of increased flexibility and velocity without creating additional risk or deployment nightmares.
Microservices architecture has become the new norm in software development. CI/CD delivery had made releasing updates so frequent it’s almost a daily thing. Modern Software delivery allows no downtime and creates new challenges.
In this webinar, Seb Rose, Continuous Improvement Lead at SmartBear, and Alon Eizenman, CTO & Co-Founder at SeaLights will examine what can go wrong when organizations jump headfirst into microservices architectures without understanding the potential pitfalls.
Join this webinar to learn:
Techniques and tooling necessary to reap the benefits of increased flexibility and velocity without creating additional risk or deployment nightmares
How to gain visibility to ensure your coverage in each microservice
How to set quality gates without delaying release to production
Hyperledger Fabric Technical Deep Dive 20190618Arnaud Le Hors
Slides presented at the Hyperledger Fabric workshop in Barecelona on July 10th, 2019.
This introduces blockchain for business and describes in details the Hyperledger Fabric design principles, overall architecture, its components, and the transaction flow.
The API economy is here and it's fueling disruption in many established industries. In response to this. many companies are looking to increase their agility through breaking down legacy monoliths into discrete services focused around specific business capabilities. Whilst this approach has many advantages, there are potential pitfalls awaiting the unwary. The number of integration points between these distributed components is greatly increased. Considering such an architecture, a naïve approach could be to simply continue to apply traditional integration testing techniques as this can lead to spiraling cost of ownership through brittle test suites. What can we do to mitigate this risk while still giving us the confidence that the various services will work cohesively?
In this session we will explore using consumer driven contacts, specifically Pact, to solve this problem and share some lessons learned from the trenches.
This session is focused on Consumer-driven Contract Testing. It’s a software testing methodology used to create a data pipeline automation testing framework. We can test microservices use of this framework. We introduce how we can use contract testing, how it works and why we need this methodology, and the architecture of PACT.
Micro-service delivery - without the pitfallsSeb Rose
The days of delivering a monolithic desktop application once a year on physical media are long gone. Today we expect continuous (or at least frequent) delivery of upgrades and security patches with zero downtime. To support this, more and more companies are moving to a distributed, cloud-based architecture of collaborating micro-services. But managing and testing an evolving of a micro-service ecosystem is not without it’s challenges.
In this session we’ll examine what can go wrong when organisations jump headfirst into micro-service architectures without understanding the potential pitfalls. You’ll leave with an understanding of the techniques and tooling necessary to reap the benefits of increased flexibility and velocity without creating additional risk or deployment nightmares.
Microservices architecture has become the new norm in software development. CI/CD delivery had made releasing updates so frequent it’s almost a daily thing. Modern Software delivery allows no downtime and creates new challenges.
In this webinar, Seb Rose, Continuous Improvement Lead at SmartBear, and Alon Eizenman, CTO & Co-Founder at SeaLights will examine what can go wrong when organizations jump headfirst into microservices architectures without understanding the potential pitfalls.
Join this webinar to learn:
Techniques and tooling necessary to reap the benefits of increased flexibility and velocity without creating additional risk or deployment nightmares
How to gain visibility to ensure your coverage in each microservice
How to set quality gates without delaying release to production
Hyperledger Fabric Technical Deep Dive 20190618Arnaud Le Hors
Slides presented at the Hyperledger Fabric workshop in Barecelona on July 10th, 2019.
This introduces blockchain for business and describes in details the Hyperledger Fabric design principles, overall architecture, its components, and the transaction flow.
The API economy is here and it's fueling disruption in many established industries. In response to this. many companies are looking to increase their agility through breaking down legacy monoliths into discrete services focused around specific business capabilities. Whilst this approach has many advantages, there are potential pitfalls awaiting the unwary. The number of integration points between these distributed components is greatly increased. Considering such an architecture, a naïve approach could be to simply continue to apply traditional integration testing techniques as this can lead to spiraling cost of ownership through brittle test suites. What can we do to mitigate this risk while still giving us the confidence that the various services will work cohesively?
In this session we will explore using consumer driven contacts, specifically Pact, to solve this problem and share some lessons learned from the trenches.
This session is focused on Consumer-driven Contract Testing. It’s a software testing methodology used to create a data pipeline automation testing framework. We can test microservices use of this framework. We introduce how we can use contract testing, how it works and why we need this methodology, and the architecture of PACT.
Blockchain is a technology for a new generation of transactional applications that establishes trust,
accountability and transparency while streamlining processes in business networks. Think of it as
an operating system for interactions between participants in a business network. It has the potential
to vastly reduce the cost and complexity of getting things done
10 crucial must have features in a Contract Management SoftwareOptimus BT
Organizations have lots of business relationships dictated by contracts and its terms. Keeping track of contract terms, provisions, obligations in a methodical fashion is frustratingly difficult when the volume of contracts is high. So how does one choose a contract management software? To answer that question, here are the top 10 crucial features to look for in a contract management software.
There are not much documents in the internet world regarding Vistex. In this post, the author has tried to give an overview of the Vistex Contract (with examples from Pharma Contracts Management System) and the bird’s eye view to the common terminologies, screens, transactions and technical objects (user exits, BADIs etc). Hope this post would act as a launch pad to all interested consultants who would like to take deep dive into Vistex Contract.
Below are the contents of the attached document:
i) Vistex Introduction
ii) Benefits of Vistex Solution
iii) Industry Challenges
iv) Benefits of Vistex Solution
v) Integrated Contract Life-Cycle Management
vi) Contract Development and Administration
vii) Contract Types
viii) Contract Screen General Tab
ix) Contract Screen Customer Tab
ix) Contract Screen Products Tab
x) Group Purchase Organization (GPO) & Buying Group
xi) Group Membership
xii) Membership/Block Maintenance Screen
xiii) Buying Group assignment to Contract
xiv) Sample Process Flow
xv) Sample Exception Processing Flow
xvi) Contract Activation
xvii) Contract Best Price Logic
xviii) Contract Data Upload
xix) Manual File Upload
xx) File Upload
xxi) Inbound Contract Create/Update (EDI 845)
xxii) Common T-Codes, Tables & BADI
Topic: Web Services Agreement Specification. The presentation contains all the basic details required for Web Services Agreement. The research paper has been quoted in the references. Cheers!
Software contracts or: how I learned to stop worrying and love releasing. Agi...Seb Rose
The test automation pyramid suggests that we should favour unit and integration tests over end-to-end tests, which leads developers to use test doubles (fakes, stubs, mocks etc.). The risk is that the developer's test double does not behave in exactly the same way as the actual component that it is replacing. When this happens, the tests all pass in your build pipeline, but you get failures when it's released into an integration (or production) environment.
Contract testing is a technique that can give you confidence that your test doubles are accurately simulating the dependencies that they replace. This is not a new technique, but the extra investment in creating and maintaining (yet another) suite of tests has restricted its uptake. Instead, organizations mitigate the risks by investing in more and more integration environments and end-to-end tests. This was always expensive, but with the adoption of micro-service architectures across the industry, the cost and complexity has escalated to a point where this approach is no longer sustainable.
There is now an urgent need for organizations to revisit contract testing, with a specific focus on consumer driven contracts for micro-services. This need led to the creation of the Pact open source tool for HTTP based micro-services. The Pact project has created a multi-platform suite of tools that dramatically simplifies the adoption of contract testing.
In this session, you'll learn why contract testing is critically important, look at how you can incorporate contract testing in your development practices, and get an introduction to Pact.
Get Started Today with Cloud-Ready Contracts | AWS Public Sector Summit 2017Amazon Web Services
In this session, we provide an overview of existing cloud-ready contracts, such as cooperative, federal, and state directed contracts, and walk through steps on how to choose the right one for your procurement. We compare various cloud-ready contracts by identifying scope, end-user eligibility, and primary service offerings to help you make the right choice for your mission needs. Learn More: https://aws.amazon.com/government-education/
Get Started Today with Cloud-Ready Contracts | AWS Public Sector Summit 2016Amazon Web Services
In this session, we will provide an overview of existing cloud-ready contracts, such as cooperative contracts and GWACs, and walk through steps on how to choose the right one for your procurement. We will explore the strengths and weaknesses and provide a comparison of various cloud-ready contracts to help you make the right choice for your mission needs.
An institutional view of Pairwyse and how it significantly reduces web3 risk, cost and maintenance while amplifying transparent governance, fault tolerance and transparent and DIY flexible control of smart contracts… post-deployment
Looking at Swagger and Pact to handle REST API specifications and contracts. Swagger allows for a JSON first specification of the API as well as generating and discovering service controllers. This can be done coherently across multiple technology stacks. We also look into using Pact to create consumer-driven contract between services in a micro service architecture to improve development confidence.
This lecture include introduction to software contracts. Before starting development companies prepare agreement document to deal with conflicts afterwards.
Testing Micro Services is an area that cannot be avoided or procrastinated to any point of time. Each services’ build before it reaches the deployment stage must be ensured that it passes the test criteria defined by the project team.
New software development approaches continue to be promoted. You may be aware of waterfall, RUP, 4GLs, 3-tier client server – all still alive and kicking in some domains. You will be familiar with some (or all) of Agile, Kanban, DevOps, SAFe, No Code/Low Code and many others. A new kid on the block is DevSecOps. What does that mean? Why is it important? How will it affect agile software teams? If we adopted the tenets of DevSecOps without calling it DevSecOps would it “smell just as sweet”? What would it “smell” like if we spun up a DevSecOps team, without understanding the fundamental challenges that DevSecOps was intended to overcome? In this session I’ll explore the origins of DevSecOps before going on to demonstrate how there’s often a distance between the label and the intent of DevSecOps. Finally I’ll discuss the impact that DevSecOps can have on our agile teams and organisations based on my perspective gathered over a 40 year career in software.
Example mapping - slice any story into testable examples - SoCraTes 2022.pdfSeb Rose
Example mapping is a simple but powerful technique for structuring the conversation you need to have before a user story goes into development. If you are struggling with user stories that are too big, or hard to test, or you're finding that the team are not all on the same page about the scope of a user story, Example Mapping could be just what you need. Using a regular pack of coloured index cards, we'll work in groups to practice breaking down the details of a user story, capturing the business rules, examples of those rules, and any questions or assumptions that emerge. Example mapping is a great input to a BDD or ATDD process, but that's not essential. You'll still get a lot out of this conversation technique even if you don't turn the examples into automated tests.
More Related Content
Similar to Software contracts - Global Enterprise Agile 2023.pdf
Blockchain is a technology for a new generation of transactional applications that establishes trust,
accountability and transparency while streamlining processes in business networks. Think of it as
an operating system for interactions between participants in a business network. It has the potential
to vastly reduce the cost and complexity of getting things done
10 crucial must have features in a Contract Management SoftwareOptimus BT
Organizations have lots of business relationships dictated by contracts and its terms. Keeping track of contract terms, provisions, obligations in a methodical fashion is frustratingly difficult when the volume of contracts is high. So how does one choose a contract management software? To answer that question, here are the top 10 crucial features to look for in a contract management software.
There are not much documents in the internet world regarding Vistex. In this post, the author has tried to give an overview of the Vistex Contract (with examples from Pharma Contracts Management System) and the bird’s eye view to the common terminologies, screens, transactions and technical objects (user exits, BADIs etc). Hope this post would act as a launch pad to all interested consultants who would like to take deep dive into Vistex Contract.
Below are the contents of the attached document:
i) Vistex Introduction
ii) Benefits of Vistex Solution
iii) Industry Challenges
iv) Benefits of Vistex Solution
v) Integrated Contract Life-Cycle Management
vi) Contract Development and Administration
vii) Contract Types
viii) Contract Screen General Tab
ix) Contract Screen Customer Tab
ix) Contract Screen Products Tab
x) Group Purchase Organization (GPO) & Buying Group
xi) Group Membership
xii) Membership/Block Maintenance Screen
xiii) Buying Group assignment to Contract
xiv) Sample Process Flow
xv) Sample Exception Processing Flow
xvi) Contract Activation
xvii) Contract Best Price Logic
xviii) Contract Data Upload
xix) Manual File Upload
xx) File Upload
xxi) Inbound Contract Create/Update (EDI 845)
xxii) Common T-Codes, Tables & BADI
Topic: Web Services Agreement Specification. The presentation contains all the basic details required for Web Services Agreement. The research paper has been quoted in the references. Cheers!
Software contracts or: how I learned to stop worrying and love releasing. Agi...Seb Rose
The test automation pyramid suggests that we should favour unit and integration tests over end-to-end tests, which leads developers to use test doubles (fakes, stubs, mocks etc.). The risk is that the developer's test double does not behave in exactly the same way as the actual component that it is replacing. When this happens, the tests all pass in your build pipeline, but you get failures when it's released into an integration (or production) environment.
Contract testing is a technique that can give you confidence that your test doubles are accurately simulating the dependencies that they replace. This is not a new technique, but the extra investment in creating and maintaining (yet another) suite of tests has restricted its uptake. Instead, organizations mitigate the risks by investing in more and more integration environments and end-to-end tests. This was always expensive, but with the adoption of micro-service architectures across the industry, the cost and complexity has escalated to a point where this approach is no longer sustainable.
There is now an urgent need for organizations to revisit contract testing, with a specific focus on consumer driven contracts for micro-services. This need led to the creation of the Pact open source tool for HTTP based micro-services. The Pact project has created a multi-platform suite of tools that dramatically simplifies the adoption of contract testing.
In this session, you'll learn why contract testing is critically important, look at how you can incorporate contract testing in your development practices, and get an introduction to Pact.
Get Started Today with Cloud-Ready Contracts | AWS Public Sector Summit 2017Amazon Web Services
In this session, we provide an overview of existing cloud-ready contracts, such as cooperative, federal, and state directed contracts, and walk through steps on how to choose the right one for your procurement. We compare various cloud-ready contracts by identifying scope, end-user eligibility, and primary service offerings to help you make the right choice for your mission needs. Learn More: https://aws.amazon.com/government-education/
Get Started Today with Cloud-Ready Contracts | AWS Public Sector Summit 2016Amazon Web Services
In this session, we will provide an overview of existing cloud-ready contracts, such as cooperative contracts and GWACs, and walk through steps on how to choose the right one for your procurement. We will explore the strengths and weaknesses and provide a comparison of various cloud-ready contracts to help you make the right choice for your mission needs.
An institutional view of Pairwyse and how it significantly reduces web3 risk, cost and maintenance while amplifying transparent governance, fault tolerance and transparent and DIY flexible control of smart contracts… post-deployment
Looking at Swagger and Pact to handle REST API specifications and contracts. Swagger allows for a JSON first specification of the API as well as generating and discovering service controllers. This can be done coherently across multiple technology stacks. We also look into using Pact to create consumer-driven contract between services in a micro service architecture to improve development confidence.
This lecture include introduction to software contracts. Before starting development companies prepare agreement document to deal with conflicts afterwards.
Testing Micro Services is an area that cannot be avoided or procrastinated to any point of time. Each services’ build before it reaches the deployment stage must be ensured that it passes the test criteria defined by the project team.
Similar to Software contracts - Global Enterprise Agile 2023.pdf (20)
New software development approaches continue to be promoted. You may be aware of waterfall, RUP, 4GLs, 3-tier client server – all still alive and kicking in some domains. You will be familiar with some (or all) of Agile, Kanban, DevOps, SAFe, No Code/Low Code and many others. A new kid on the block is DevSecOps. What does that mean? Why is it important? How will it affect agile software teams? If we adopted the tenets of DevSecOps without calling it DevSecOps would it “smell just as sweet”? What would it “smell” like if we spun up a DevSecOps team, without understanding the fundamental challenges that DevSecOps was intended to overcome? In this session I’ll explore the origins of DevSecOps before going on to demonstrate how there’s often a distance between the label and the intent of DevSecOps. Finally I’ll discuss the impact that DevSecOps can have on our agile teams and organisations based on my perspective gathered over a 40 year career in software.
Example mapping - slice any story into testable examples - SoCraTes 2022.pdfSeb Rose
Example mapping is a simple but powerful technique for structuring the conversation you need to have before a user story goes into development. If you are struggling with user stories that are too big, or hard to test, or you're finding that the team are not all on the same page about the scope of a user story, Example Mapping could be just what you need. Using a regular pack of coloured index cards, we'll work in groups to practice breaking down the details of a user story, capturing the business rules, examples of those rules, and any questions or assumptions that emerge. Example mapping is a great input to a BDD or ATDD process, but that's not essential. You'll still get a lot out of this conversation technique even if you don't turn the examples into automated tests.
Software testing - learning to walk again (expoQA22)Seb Rose
Software testing seems to advance at an ever increasing pace. However, lurking under the surface of relentless progress, Seb Rose believes there is a rich strata of continuity. In this session he will explore these foundational aspects of our trade - informally and illustrated by some pretty pictures.
The first article Seb wrote for a software journal was in 2003 (https://accu.org/index.php/articles/363) where he drew an awkward analogy between software projects and building a shed. Over the years, he has found that he has a penchant for analogies and this session will continue in that vein. Don’t worry, though, he’s not going to bore you with pictures of building sites or aphorisms from lean manufacturing.
Instead, he’ll take you on a gentle walk on some mountainous paths in the south of France. There’ll be red wine and automated testing; oak forests and scope creep; deep river gorges and CI pipelines. He’ll ask you to walk with him and take a close look at the concepts that underpin our trade.
“We must learn to walk before we can run” is an age-old adage. We all learned to walk decades ago. Many of us learnt how to test software shortly thereafter. However, just as running is not simply walking faster, neither is better software testing simply working with the latest shiny tools. By slowing down, observing our behaviour, considering alternatives, and deliberately practicing different approaches we can re-learn how to develop software. Or confirm that how we’re doing it now is just fine.
As Jon Jagger reminds us in the FAQ of the wonderful Cyber-Dojo: “Stop trying to go faster; start trying to go slower. Don’t think about finishing; think about improving. Think about practicing.”
From this keynote, you’ll enjoy a gentle walk on some mountainous paths in the south of France, some red wine with unit testing and above all understand how to walk before running.
DevSecOps - Unicom Agile and DevOps Expo (Adaptive Challenges) 2021Seb Rose
New software development approaches continue to be promoted. You may be aware of waterfall, RUP, 4GLs, 3-tier client server – all still alive and kicking in some domains. You will be familiar with some (or all) of Agile, Kanban, DevOps, SAFe, No Code/Low Code and many others.
A new kid on the block is DevSecOps. What does that mean? Where did it come from? Why is it important? If we adopted the tenets of DevSecOps without calling it DevSecOps would it “smell just as sweet”? What would it “smell” like if we spun up a DevSecOps team, without understanding the fundamental challenges that DevSecOps was intended to overcome?
In this session I’ll explore the origins of DevSecOps before going on to demonstrate the distance between the label and the intent of DevSecOps. Finally I’ll try to generalise the journey from “good idea” to “empty slogan” that seems to underpin many of the hyped transformations that I’ve lived through during my 40 year career in software.
A brief history of requirements - Unicom 2022Seb Rose
Was there a time before requirements? Can the product be created before the requirements? Is a product ever “finished”? These are just some of the questions considered in this session. It begins by reviewing the great requirement formalisms of yester-year, before delving into the secrets which still lie at the heart of agile product development, from user stories to living documentation, via confetti parties and Behaviour Driven Development (BDD)
* BDUF – Big Design Up Front
** JIT – Just In Time
Example mapping (with builds) - ProductWorld 2022Seb Rose
Is your team struggling with unproductive meetings and workshops? Are you unsatisfied with how your team comes together to refine requirements and specify solutions? Have you heard about example mapping and want to know more?
Specifying and delivering software is a process of discovery. No team has ever delivered a valuable product without discovering many things during the development process, but many teams struggle to get good at discovery. Matt Wynne created a technique called example mapping that has helped thousands of teams around the world use examples to reach a shared understanding of the problems that need solved. As a consequence there are fewer misunderstandings, fewer disagreements, and a smoother flow of value delivery.
Is your team struggling with unproductive meetings and workshops? Are you unsatisfied with how your team comes together to refine requirements and specify solutions? Have you heard about example mapping and want to know more?
Specifying and delivering software is a process of discovery. No team has ever delivered a valuable product without discovering many things during the development process, but many teams struggle to get good at discovery. Matt Wynne created a technique called example mapping that has helped thousands of teams around the world use examples to reach a shared understanding of the problems that need solved. As a consequence there are fewer misunderstandings, fewer disagreements, and a smoother flow of value delivery.
No code, low code, machine code QA ATL 2021Seb Rose
Everything looks solvable if you ignore most of the complications. Many things look impossible if you’re stuck in the weeds. The current fashion for low/no code solutions heralds the cyclical return to looking for solutions that require softer skillsets. When is this appropriate and when is it a recipe for disaster?
No code, low code, machine code QA ATL 2021Seb Rose
Everything looks solvable if you ignore most of the complications. Many things look impossible if you’re stuck in the weeds. The current fashion for low/no code solutions heralds the cyclical return to looking for solutions that require softer skillsets. When is this appropriate and when is it a recipe for disaster?
No code, low code, machine code - Unicom 2021Seb Rose
Everything looks solvable if you ignore most of the complications. Many things look impossible if you’re stuck in the weeds. The current fashion for low/no code solutions heralds the cyclical return to looking for solutions that require softer skillsets. When is this appropriate and when is it a recipe for disaster?
BDD: from soup to nuts - The Future of Work Scotland 2021Seb Rose
Behaviour Driven Development (BDD) is an agile approach to delivering software that has been around for well over a decade. It was created to help developers care about quality, morphed into a collaboration approach, and found widespread mis-adoption as a test automation technique.
In this session Seb will explain how BDD is intended to work, what value it delivers when done well, and why much BDD in the workplace falls short.
Learning Objectives:
What can our attendees expect to take away from the session?
● enumerate the three core practices of BDD
● explain the difference between BDD and test automation
● argue that collaboration and learning are at the heart of successful software development
Contrasting test automation and BDD - 2020Seb Rose
Test automation and BDD are related, but they are not the same. To get the most out of each of them, we need to understand the separate challenges that they address before getting engrossed in the tools that have been created to facilitate their adoption. And those challenges are rooted in the interactions between the different disciplines involved in software specification and delivery.
In this session we’ll explore what test automation and BDD are - and how they separately contribute to successful inter-disciplinary agile delivery. We'll also spend some time describing how they're different, and look at several typical examples of what can go wrong when BDD and test automation get confused.
Are BDD and test automation the same thing? Automation Guild 2021Seb Rose
Test automation and behaviour-driven development (BDD) are related, but they are not the same. To get the most out of each of them, we need to understand the separate challenges that they address before getting engrossed in the tools that have been created to facilitate their adoption. And those challenges are rooted in the interactions between the different disciplines involved in software specification and delivery.
In this session we’ll explore what test automation and BDD are – and how they separately contribute to successful inter-disciplinary agile delivery. We’ll also spend some time describing how they’re different, and look at several typical examples of what can go wrong when BDD and test automation get confused.
"Our BDDs are broken!" Lean Agile Exchange 2020Seb Rose
Is the goal of your QA team to increase the number of automated tests? Are managers looking for tools that allow test-automation without the need for development skills? Are you using Given/When/Then phrasing to write automation tests?
In this session we’ll briefly define what BDD is, spend a bit longer describing what it isn’t, and look at several typical examples of what can go wrong if you use Cucumber when you’re not following a BDD approach.
User stories: from good intentions to bad advice - Agile Scotland 2019Seb Rose
These are the slides I wanted to use at Agile Scotland 2019. Unfortunately, my laptop refused to play ball and I ended up using an older version that was already on SlideShare.
User stories: from good intentions to bad advice - Lean Agile Scotland 2019Seb Rose
User stories are one of the most visible artefacts of most agile methods and, as such, have generated large quantities of expert advice. In my experience, much of that advice is open to misinterpretation.
In this session, we'll explore several classic pieces of advice, to see how misunderstandings can cause problems, despite the best intentions. The examples we'll look at are:
- an acronym: INVEST, created by Bill Wake
- a technique: relative estimation using story points, created by Ron Jeffries or Joseph Pelrine
- a template: Connextra (As-A/I-Want/So-That), created by Rachel Davies
Expert advice taken in good faith, that leads to bad outcomes, can cause us to become distrustful. It's time to reiterate that there is no magic formula, no silver bullet. At best, experts can lend you a framework within which to think, but their advice will never make thinking unnecessary.
Planning poker, introduced back in the early days of XP, has become a standard ritual in many agile processes.
To paraphrase the Hitchhiker's Guide, although planning poker frequently leads to estimates that are "apocryphal, or at least wildly inaccurate, it scores over older, more pedestrian techniques in two important respects. First, it is almost entirely informal; and secondly it let's consultancies inscribe their name in large friendly letters on the back of each card".
In 11 slides I'll describe how planning poker is supposed to work, why it usually doesn't, and offer some alternatives that might work better for you. Along the way we'll also try to answer one of the universe's most difficult questions: how long is a piece of string?
Ever looked at a specification and wondered exactly what it meant? Ever wasted time trying to figure out what might be impacted by a change in the specifications? Ever been unsure which parts of the specification have actually been developed? Ever looked at test scripts and found yourself unclear what was actually being tested?
Of course you have!
There is a better way to tackle uncertainty and write easily understood specifications, that can also act as automated tests. Come find out how.
Ever looked at a requirement and wondered exactly what you should be testing?
Ever wasted time trying to figure out which of your tests are impacted by a change in the requirements?
Are your automated tests so clear that anyone on the team can read and write them - even the Product Owner?!
These are not unicorns, there is a better way to write clean, simple, easily maintainable tests.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
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.
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.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
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.
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.
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.
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.
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/
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
Software contracts - Global Enterprise Agile 2023.pdf
1. Software contracts
- agility in the world of micro-services
Seb Rose
Mastodon: @sebrose@mastodon.scot
Twitter: @sebrose
Blog: https://cucumber.io/blog/
E-mail: seb.rose@smartbear.com
Please help us by completing this 30 second
microservices and contract testing questionnaire.
3. @sebrose h
tt
p:/
/smartbear.com
Micro-service architecture …
… a collec
ti
on of services that are:
•Independently deployable
•Loosely coupled
•Organised around business capabili
ti
es
•Owned by a small team
•Highly maintainable and testable
h
tt
ps:/
/microservices.io/
4. @sebrose h
tt
p:/
/smartbear.com
Bene
fi
ts
The micro-service architecture enables the
rapid, frequent and reliable delivery of
large, complex applica
ti
ons. It also enables
an organiza
ti
on to evolve its technology
stack.
h
tt
ps:/
/microservices.io/
5. @sebrose h
tt
p:/
/smartbear.com
Pi
tf
alls
• The micro-service I depend on isn’t ready
• The micro-service I depend on doesn’t
provide the func
ti
onality I need
• I’m not con
fi
dent that the new version of
the micro-service will behave the same
• We want to update our micro-service, but
don’t know who is using it. Or how.
6. @sebrose h
tt
p:/
/smartbear.com
You have a distributed monolith
Beth Skurrie
If you can’t deploy services independently,
you don’t have micro-services.
Spot the he
ff
alump
7. @sebrose h
tt
p:/
/smartbear.com
TL;DR
• All interac
ti
ons between so
ft
ware
components are governed by contracts
• Contract tes
ti
ng ensures that both
components have the same expecta
ti
ons
• Contract tests should be wri
tt
en by the
developers
11. @sebrose h
tt
p:/
/smartbear.com
Design by contract
Design by contract
Contract
• an agreement between client
and supplier
Characteris
ti
cs
• expect some bene
fi
ts
• incur some obliga
ti
ons
16. @sebrose h
tt
p:/
/smartbear.com
▪Closed and complete Provider contracts express a service's business
function capabilities in terms of the complete set of exportable elements
available to consumers, and as such are closed and complete with respect
to the functionality available to the system.
▪Singular and authoritative Provider contracts are singular and authoritative
in their expression of the business functionality available to the system.
▪Bounded stability and immutability A provider contract is stable and
immutable for a bounded period and/or locale. Provider contracts typically
use some form of versioning to differentiate differently bounded instances
of the contract.
https://martinfowler.com/articles/consumerDrivenContracts.html
Provider contracts
17. @sebrose h
tt
p:/
/smartbear.com
▪Open and incomplete Consumer contracts are open and incomplete with
respect to the business functionality available to the system. They express
a subset of the system's business function capabilities in terms of the
consumer's expectations of the provider contract.
▪Multiple and non-authoritative Consumer contracts are multiple in
proportion to the number of consumers of a service, and each is non-
authoritative with regard to the total set of contractual obligations placed on
the provider. Consumers may evolve at different rates.
▪Bounded stability and immutability Like provider contracts, consumer
contracts are valid for a particular period of time and/or location.
https://martinfowler.com/articles/consumerDrivenContracts.html
Consumer driven contracts (CDC)
24. @sebrose h
tt
p:/
/smartbear.com
• Each consumer captures their expecta
ti
ons
of the provider in a separate contract.
• All of these contracts are shared with the
provider so they gain insight into the
obliga
ti
ons they must ful
fi
l for each
individual client.
• The provider can create a test suite to
validate these obliga
ti
ons.
h
tt
ps:/
/thoughtworks.github.io/pacto/pa
tt
erns/cdc/
Consumer driven contracts
31. @sebrose h
tt
p:/
/smartbear.com
JB Rainsberger, via GOOS mailing list, “Unit-test mock/stub assumptions rots”
15 March 2012
Systema
ti
c contract tes
ti
ng
• Collabora
ti
on tests make
assump
ti
ons about the contract
• Contract tests try to jus
ti
fy those
assump
ti
ons
JB Rainsberger, via GOOS mailing list, “Unit-test mock/stub assumptions rots”
15 March 2012
37. @sebrose h
tt
p:/
/smartbear.com
Pact provides a mechanism for crea
ti
ng a
contract between a service consumer and a
service provider, and then providing the tools
to validate that the consumer and provider
adhere to the contact independently of each
other.
https://dius.com.au/2014/05/19/simplifying-micro-service-testing-with-pacts/
Simplifying consumer driven contracts
38. @sebrose h
tt
p:/
/smartbear.com
•Consumer creates contracts using Pact DSL
•When consumer tests are run:
•Pact creates a mock HTTP server
•a Pact
fi
le is created
•Provider uses Pact
fi
le to verify compa
ti
bility
•Provider may o
ff
er “backdoor” interface
Pact - key points
43. @sebrose h
tt
p:/
/smartbear.com
• Pacts are published by Consumer
• Pacts are fetched by Provider
• Results are stored in the “Matrix”
• “Matrix” supports independent deployment
Pact broker - key points
44. @sebrose h
tt
p:/
/smartbear.com
Pact
fl
ow is the complete contract testing solution
allowing teams to orchestrate and scale their contract
testing initiative.
Visibility to focus on what ma
tt
ers
With Pact
fl
ow, developers can
fi
nd and
fi
x integration
errors earlier in the SDLC and teams can improve
communication & collaboration, reduce reliance on
E2E tests resulting in faster and safer deployments.
45. @sebrose h
tt
p:/
/smartbear.com
•Increases agility and con
fi
dence
•Reduces need for integra
ti
on tests
•Speeds up development
•No subs
ti
tute for communica
ti
on
•Is a development ac
ti
vity
•Does not replace other forms of tes
ti
ng
Take aways
Contract tes
ti
ng:
46. https://bddbooks.com
Please help us by completing this
30 second microservices and
contract testing questionnaire.
Seb Rose
Mastodon: @sebrose@mastodon.scot
Twitter: @sebrose
Blog: https://cucumber.io/blog/
E-mail: seb.rose@smartbear.com
Download these
slides