The document summarizes an agile testing meetup that covered various agile testing techniques. It began with introductions from attendees and an overview of agile testing approaches. Key points included testing being part of development with whole team involvement. Techniques covered were unit testing, test driven development, acceptance testing, and behaviour driven development. Unit testing tests smallest parts while acceptance tests verify features. Test driven development focuses on writing tests first before code. Behaviour driven development uses scenarios to define features from a business perspective. The meetup concluded with a Q&A session.
This session will focus on a Agile Testing and provide you with practical examples and techniques to help your team understand what is behind this approach.
The presentation was delivered at Testing Automation & continuous testing summit at bangalore, organized by NextgenTesting team and unicom learning team.
As Agile become mainstream increasingly organizations are looking to double down on the role of the Product Owner encouraging them to manage the intersection between technology and the business. But Product Ownership is a difficult role as it tries to balance the needs of the business with the reality of software delivery. Also, for many organizations there is some ‘confusion’ with existing roles of business analyst, product manager or even project manager. What does the product owner do anyway?
In this talk Dave West, Product Owner and CEO Scrum.org, the home of Scrum and Professional Scrum Trainer with Prowareness Rob van Lanen describe the genesis of the Product Owner role and how many organizations are dealing with the challenges of slotting this key role into existing product, project and release roles. They will introduce some techniques such as user centric design, and hypophysis based development and describe how approaches such as Lean Startup and pragmatic marketing are providing product owners with a tool box to do their job.
Recorded Webinar can be found at :-https://www.scrum.org/resources/who-product-owner-anyway
This session will focus on a Agile Testing and provide you with practical examples and techniques to help your team understand what is behind this approach.
The presentation was delivered at Testing Automation & continuous testing summit at bangalore, organized by NextgenTesting team and unicom learning team.
As Agile become mainstream increasingly organizations are looking to double down on the role of the Product Owner encouraging them to manage the intersection between technology and the business. But Product Ownership is a difficult role as it tries to balance the needs of the business with the reality of software delivery. Also, for many organizations there is some ‘confusion’ with existing roles of business analyst, product manager or even project manager. What does the product owner do anyway?
In this talk Dave West, Product Owner and CEO Scrum.org, the home of Scrum and Professional Scrum Trainer with Prowareness Rob van Lanen describe the genesis of the Product Owner role and how many organizations are dealing with the challenges of slotting this key role into existing product, project and release roles. They will introduce some techniques such as user centric design, and hypophysis based development and describe how approaches such as Lean Startup and pragmatic marketing are providing product owners with a tool box to do their job.
Recorded Webinar can be found at :-https://www.scrum.org/resources/who-product-owner-anyway
The Business Analyst’s Critical Role in Agile ProjectsTechWell
Are you a business analyst, wondering how you fit into agile projects? Are you a ScrumMaster who wants to work with business analysts for a stronger project team? Are you a product owner who needs to supercharge your product backlog? Mark Layton introduces you to the critical role of the business analyst on agile projects. Get the essential information business analysts need to know to be successful members of an agile project team. Learn how business analysts can use their product knowledge and requirements translation skills to support product owners and stakeholders. Discover the role of product owner agent and why business analysts do well in that role. Learn how business analysts approach documentation—especially requirements—on agile projects. Dive into the details of the product backlog and user stories. Bring your questions and be ready to learn all about the who and the how of the business analyst in agile projects.
A short talk that explains a little of what Agile is; where it originated and how it works. This talk is applicable whatever method you use - scrum, XP, DSDM etc. Concludes by introducing ICAgile (the International Consortium of Agile).
Agile Software Development
Not being too attached to your initial idea of what the project will look like and to be ready for change and to refactor.
Agile software engineering combines a philosophy and a set of development guidelines.
To be agile you need to put the agile values and principles into practice.
it was used as a basis for a panel discussion on one of our Polar Talks recently.
abstract:
It's been 15 years since the Agile Manifesto was signed and several methodologies were raised ever since. There is almost no developer nowdays that haven't adopted at least one of the Agile principles and uses them in everyday work or even private life. Some has even done improvised versions which work according their needs.
The question that's been around these past years is if the Agile is old enough to become past and what's the next big thing, is it a time to call it Post-Agile period and what that means. What has or needs to change in order to abandon the old and become the Post Agile follower.
Lots of teams already claim themselves as Post-Agile pioneers and some new ideas of methodologies have been introduced. I'll try to bring an overview of some of them and bring you some thoughts that might help answering the above questions.
Product Owners need Super Powers to unlock the creative potential to innovate in the context of their organisation. The #PoDojo is the place to get your level up.
The Role of a BA on a Scrum Team IIBA Presentation 2010scrummasternz
What is your role as a BA on a Scrum team? How do you fit in? This presentation was given to the IIBA conference in NZ in 2010 by Stephen Reed. Stephen had worked extensively as a BA and moved into using Scrum with multiple teams at a large Insurance company. This experience led to a lot of questions around what the BA should be doing on a Scrum team. This presentation goes some way to listing what worked in the teams Stephen was involved in. The BA role does not change and all the skills of a great BA are necessary still on a great Software Development team, just more focused on being a team member and utilising those skills for the Scrum process of getting working software to the customer with more focus and clarity for the user.
What is scaling and how can it help to improve your organisation? What is the right mix of scaling principles and practices for your culture and teams? I will compare some agile approaches on scaling like Scaled Agile Framework aka SAFe, Large Scale Scrum (LeSS) both based on principles of Lean Product Development and Scaling Agile @ Spotify.
Have you ever wondered what makes a good Product Owner? It’s a broad and deep role that is often filled with a hodgepodge of differently skilled individuals. Many organizations struggle to understand its importance as they scale their agile transformations. What about exceptional Product Ownership? What does that entail? In this highly collaborative session, Bob Galen explores the Four Quadrants of Effective Product Ownership—Product Management, Project Management, Leadership, and Business Analysis. Each of these critical aspects of the Product Owner role supports the agile team. Together, they lead to well-constructed product backlogs with an emphasis on creating high quality and high value products. Leave this session with a better understanding of the breadth and depth associated with outstanding Product Owners, a newfound respect for how challenging the role is, and with immediate insights and actions for improving your organization’s Product Ownership.
Scaling Agile and Scrum (cPrime/Angela Johnson)Cprime
This webinar will introduce attendees to Agile and Scrum tools to “scale”across products, the enterprise and locations. Unlike other scaling approaches that are a one size fits all model, this interactive session shows how to apply Scrum and Agile without contradicting values, principles or frameworks.
Оформление коммерческого предложения. Зачем нужно оформление коммерческого предложения? Какие инструменты мы используем для оформления? Каких ошибок лучше избегать при подготовке коммерческих предложений. Фрагмент презентации с семинара Тимура Асланова "Техника написания коммерческих предложений, которые реально продают". www.supersales.ru
The Business Analyst’s Critical Role in Agile ProjectsTechWell
Are you a business analyst, wondering how you fit into agile projects? Are you a ScrumMaster who wants to work with business analysts for a stronger project team? Are you a product owner who needs to supercharge your product backlog? Mark Layton introduces you to the critical role of the business analyst on agile projects. Get the essential information business analysts need to know to be successful members of an agile project team. Learn how business analysts can use their product knowledge and requirements translation skills to support product owners and stakeholders. Discover the role of product owner agent and why business analysts do well in that role. Learn how business analysts approach documentation—especially requirements—on agile projects. Dive into the details of the product backlog and user stories. Bring your questions and be ready to learn all about the who and the how of the business analyst in agile projects.
A short talk that explains a little of what Agile is; where it originated and how it works. This talk is applicable whatever method you use - scrum, XP, DSDM etc. Concludes by introducing ICAgile (the International Consortium of Agile).
Agile Software Development
Not being too attached to your initial idea of what the project will look like and to be ready for change and to refactor.
Agile software engineering combines a philosophy and a set of development guidelines.
To be agile you need to put the agile values and principles into practice.
it was used as a basis for a panel discussion on one of our Polar Talks recently.
abstract:
It's been 15 years since the Agile Manifesto was signed and several methodologies were raised ever since. There is almost no developer nowdays that haven't adopted at least one of the Agile principles and uses them in everyday work or even private life. Some has even done improvised versions which work according their needs.
The question that's been around these past years is if the Agile is old enough to become past and what's the next big thing, is it a time to call it Post-Agile period and what that means. What has or needs to change in order to abandon the old and become the Post Agile follower.
Lots of teams already claim themselves as Post-Agile pioneers and some new ideas of methodologies have been introduced. I'll try to bring an overview of some of them and bring you some thoughts that might help answering the above questions.
Product Owners need Super Powers to unlock the creative potential to innovate in the context of their organisation. The #PoDojo is the place to get your level up.
The Role of a BA on a Scrum Team IIBA Presentation 2010scrummasternz
What is your role as a BA on a Scrum team? How do you fit in? This presentation was given to the IIBA conference in NZ in 2010 by Stephen Reed. Stephen had worked extensively as a BA and moved into using Scrum with multiple teams at a large Insurance company. This experience led to a lot of questions around what the BA should be doing on a Scrum team. This presentation goes some way to listing what worked in the teams Stephen was involved in. The BA role does not change and all the skills of a great BA are necessary still on a great Software Development team, just more focused on being a team member and utilising those skills for the Scrum process of getting working software to the customer with more focus and clarity for the user.
What is scaling and how can it help to improve your organisation? What is the right mix of scaling principles and practices for your culture and teams? I will compare some agile approaches on scaling like Scaled Agile Framework aka SAFe, Large Scale Scrum (LeSS) both based on principles of Lean Product Development and Scaling Agile @ Spotify.
Have you ever wondered what makes a good Product Owner? It’s a broad and deep role that is often filled with a hodgepodge of differently skilled individuals. Many organizations struggle to understand its importance as they scale their agile transformations. What about exceptional Product Ownership? What does that entail? In this highly collaborative session, Bob Galen explores the Four Quadrants of Effective Product Ownership—Product Management, Project Management, Leadership, and Business Analysis. Each of these critical aspects of the Product Owner role supports the agile team. Together, they lead to well-constructed product backlogs with an emphasis on creating high quality and high value products. Leave this session with a better understanding of the breadth and depth associated with outstanding Product Owners, a newfound respect for how challenging the role is, and with immediate insights and actions for improving your organization’s Product Ownership.
Scaling Agile and Scrum (cPrime/Angela Johnson)Cprime
This webinar will introduce attendees to Agile and Scrum tools to “scale”across products, the enterprise and locations. Unlike other scaling approaches that are a one size fits all model, this interactive session shows how to apply Scrum and Agile without contradicting values, principles or frameworks.
Оформление коммерческого предложения. Зачем нужно оформление коммерческого предложения? Какие инструменты мы используем для оформления? Каких ошибок лучше избегать при подготовке коммерческих предложений. Фрагмент презентации с семинара Тимура Асланова "Техника написания коммерческих предложений, которые реально продают". www.supersales.ru
La bibliothèque sous toutes ses formes
Livres animés, récits audiovisuels, écritures mouvantes et poèmes vivants : les métamorphoses du livre n’ont de cesse de nous émerveiller. En 1961, Raymond Queneau composait la première œuvre de poésie combinatoire : Cent mille milliards de poèmes, que l’on retrouve désormais en version numérique plus pratique, car au lieu de feuilleter des lamelles au hasard, le lecteur peut choisir chaque vers parmi les dix possibilités qui lui sont offertes. En 1971, le projet Gutenberg donnait naissance au livre numérique qui compte aujourd’hui de plus en plus d’adeptes. Aujourd’hui, les possibilités du numérique offrent encore plus de surprises.
Des contes interactifs
La souris qui raconte est une maison d’édition 100% numérique qui propose plusieurs collections d’histoires inédites selon différents degrés d’interactivité : avec les histoires à inventer par exemple, l’enfant peut recomposer l’histoire à sa façon, et le cadre narratif devient pour lui un espace de création. Pour Françoise Prêtre, directrice, il s’agit d’une lecture innovante, gourmande, qui ne s’appuie sur aucun livre édité mais offre une lecture plurielle, où lettres, mots, images et sons s’animent pour le plus grand plaisir des lecteurs en herbe.
Les livres prennent vie
En 2009, Jacques Attali publie Le Sens des choses un « hyperlivre » truffé de flashcodes qui renvoient vers des contenus multimédia. A présent, les éditions Nathan proposent une collection de livres pédagogiques en réalité augmentée. Il suffit d’un ordinateur équipé de webcam : après avoir téléchargé le logiciel, on contrôle à partir du clavier tous les objets modélisés en 3D. Tels des Pop-ups animés, hélicoptères, dragons et dinosaures surgissent alors du livre comme par magie. Imaginez alors les possibilités d’apprentissage, le goût pour la lecture réactivé via ces nouvelles formes de lecture.
Le livre augmenté, objet d’art ?
Promenade visuelle de toute beauté, Le monde des montagnes de Camille Scherrer nous emmène dans un univers merveilleux. Cette jeune designer interactive donne vie à ses histoires en mêlant technologie et poésie qui séduisent par son originalité, sa créativité et sa grâce. Superbe exemple où un univers, invisible sur le support imprimé, se dévoile. Des poissons surgissent des cadres photos, des nuages passent doucement sur la page, des flocons caressent le papier : autant d’invitations à l’étrange.
Ces expériences de lecture à vivre ouvrent la voie à des nouveaux territoires comme l’univers des applications mobiles : Les fantastiques livres volants de M. Morris Lessmore, Voyage au centre de la terre, le livre qui voulait être un jeu vidéo (Etienne Mineur Editions).
What is the Board's role in governance and do they follow good practice?
What does good look like?
Are there good practice guidelines available?
And in particular how can you influence your board to adopt good practice in governance of project management?
These are some of the questions answered at the latest evening session of the APM Governance SIG.
This was one of a series of sessions that the Governance SIG is presenting to enable good practice to be shared.
Poor governance of projects and project management is a major cause of project failure. Recent research (by both PwC and APM) has shown a direct correlation between organisational and project success and good governance. So good governance is the key success factor in delivering successful project outcomes. Shouldn't Boards take note and make improvement of governance a strategic objective?
Protéger vos données grâce à microsoft rms - Marocco SharePoint Days 2016Joris Faure
Face à l'explosion du numérique qui permet de nouvelles formes de collaboration. Les entreprises de toutes tailles sont confrontées à des besoins croissants de protection de leurs informations sensibles. Dans ce même temps, ces entreprises doivent partager en toute sécurité cette même information entre les collaborateurs appropriés. Microsoft Rights Management service ou plus communément AD RMS offre la possibilité de créer et consommer des contenus protégés présents sur vos espaces de collaboration (SharePoint, partage réseau).
Découvrez dans cette session les concepts de cette protection ainsi que la configuration nécessaire pour la mise en place de cette infrastructure. Tout cela, suivi d’une présentation live de la mise en place d’une protection RMS dans SharePoint.
How do you know if you have too much process, too little, or just the right amount? If you ignore process completely, unpredictability and chaos can follow. If you define the process to the nth degree and follow it religiously, the work grinds to a halt. Janet Gregory shares her experiences about how to find the tastiest balance of process and creativity for your projects and organization. She proposes that a formally defined process is sometimes necessary, but that it should be the exception. Explore with Janet the many variables—team size, complexity, criticality, organization structure, and culture—you must assess to find just the right balance. Learn how to make existing processes better by adding visibility to the process, getting team members’ input, and adapting documentation you need. Learn how to transform complicated processes into simpler ones—such as reporting a simple “thumbs up” or “thumbs down”—and go home with new tools to sprinkle on just enough process.
Campbell & Readman - TDD It's Not Tester Driven Development - EuroSTAR 2012TEST Huddle
EuroSTAR Software Testing Conference 2012 presentation on TDD It's Not Tester Driven Development by Campbell & Readman. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Agile2014 Report: As a Speaker and a Reporter of the latest Agile in the world Rakuten Group, Inc.
This is a flash report of Agile2014 by Hiroyuki Ito.
「Agile2014」の参加レポート(速報版)です。
Agile2014
http://agile2014.agilealliance.org/
Please feel and enjoy atmosphere of the latest Agile :)
How to Jumpstart Enterprise Agile AdoptionTechWell
Want to get a jumpstart on agile adoption in your organization? Begin by leveraging a roadmap that Intuit has used for rolling out enterprise agile to its business units. While there is no single way to bring enterprise agile into your organization, Alan Padula describes a model that has worked repeatedly. The important first step is to create a vision of what full agile adoption looks like. Once a rich vision is created describing what people will be doing and how they will be doing it, create a roadmap, a time-sequenced plan with milestones. Each milestone has a description of everyone’s job responsibilities, the measurements to take along the way, the personal and business benefit, and the set of activities planned in order to achieve each succeeding milestone. Key transition activities include training, infrastructure, change leadership, planning, and governance. Join Alan for the jumpstart you need to successfully adopt agile in your organization.
Quality for DevOps teams - Quality engineering in the DevOps cultureRik Marselis
This presentation is about quality engineering in the DevOps culture.
It is based on our new TMAP book: "Quality for DevOps teams"
I presented this at various conferences, for example at TestCon and the ANZ Selenium days in October 2020.
More information can be found on our body of knowledge website www.TMAP.net
Technology-Driven Development: Using Automation and Development Techniques to...Hiroyuki Ito
This is the report presented at Agile2014 on "Experience Report" track.
「Agile2014」の「Experience Report」トラックで発表したスライドです。
Agile2014
http://agile2014.agilealliance.org/
Track information
http://agile2014.sched.org/event/356d50c44035cafe4c27c33da03c2b80#
Automation and development techniques such as Continuous Integration/Continuous Delivery, TDD (Test-Driven Development) and BDD (Behavior-Driven Development) are useful for not only efficiency but also learning and collaboration.
I explained these practices as "Technology-Driven Development".
CI/CD・TDD・BDD といった自動化技術・技術プラクティスは、業務効率化だけではなく、メンバーの成長およびコラボレーションの促進にも効果があります。
これらのプラクティスを "Technology-Driven Development" と命名・整理した資料になります。
Agile2014 Report: As a Speaker and a Reporter of the latest Agile in the worldHiroyuki Ito
This is a flash report of Agile2014 by Hiroyuki Ito.
「Agile2014」の参加レポート(速報版)です。
Agile2014
http://agile2014.agilealliance.org/
Please feel and enjoy atmosphere of the latest Agile :)
L'I.T. dans une entreprise, c'est comme une copropriété. On peut passer à côté des autres et se revoir pour le bilan financier annuel, mais ne rien produire de concret ensemble d'autres qu'une routine sensée être bien huilée.
Mais quand un incident majeur arrive, chacun reste dans son coin, et on n'est pas solidaires. On peut même en arriver à se faire des procès entre co-propriétaires et à se rendre la vie impossible par des mesquineries.
Jusqu'au point où déménager reste la seule solution, ou alors au point où la maison tombe en ruine par absence de soin ou de travaux.
Comment sortir de cette logique?
Et puis d'abord.......mais pourquoi nous parle-t'il de tout ça? Quel rapport avec Devops?
Les pratiques Devops existent depuis maintenant un bon moment, et deviennent mainstream.
Pourquoi est-ce le cas? Est-ce vraiment important? Devriez-vous vous y intéresser?
Et surtout, c'est quoi Devops?
Conférence #GEN5 (21/09/2017) - Atelier découverte de l'agilité. Au travers d'un jeu (le "ball point game"), nous vous proposons de découvrir quelques principes clés de l'agilité.
Workshop held during the Luxembourg Internet Days 2016 Start-ups forum on 22 November '16. It includes an exercise to have the participants experience what a Problem Interview is, and realize how important it is to seek market validation from the very beginning of the startup process.
DevOps qu'est-ce que c'est? Comment l'utiliser? Qu'est-ce qu'une VM? Et l'agilité dans tout ça? Cette introduction au monde de DevOps vous permettra de comprendre comment le mouvement est né mais aussi sur quoi il repose.
Agile Mëtteg - 29 November 2012
Welcome to the dojo! If you want to code like a ninja you have to practice your katas!
A code kata is a simple exercise that allows a developer to improve his coding, testing & refactoring skills.
In this session you will practice pair-programming, TDD & clean code.
This session is for developers only!
Kanban: going Lean/Agile for your IT dev. & support teamAgile Partner S.A.
Agile Mëtteg - 22 September 2011.
In Luxembourg we see many IT teams that are struggling to respond to new business requests while supporting existing systems. Without a proper management framework and clearly defined objectives, this can lead to misunderstanding between business and IT, and eventually disappointment and distrust.
In the past few years a new approach has emerged within the Lean/Agile community: Kanban for software development. This method differentiates from most other Agile approaches as it is not iterative but based on a continuous flow managed with a pull system.
During this session you will discover the Kanban Method and how to implement it for empowering your team for managing both software development projects and support activities, achieving better results and rebuilding trust with your business stakeholders.
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.
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.
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
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.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
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.
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
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.
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.
2. Agile Mëtteg in 2010 Complete Agile Mëtteg calendar on www.agilepartner.net/agility_seminars.html 15 July 2010 Agile Mëtteg - Agile Testing 2
3. OBJECTIVES & AGENDA Objectives This session will focus on a Agile Testing and provide you with practical examples and techniques to help your team understand what is behind this approach. Agenda Introduction of Agile Partner The attendees What is agile testing? And why? And how? Unit testing Behaviour Driven Development Test Driven Development Acceptance testing Q&A 15 July 2010 Agile Mëtteg - Agile Testing 3
4. AGILE PARTNER SERVICES 15 July 2010 Agile Mëtteg - Agile testing 4 IS users Services 1 Custom Software Development & Maintenance Our core business to answer customer needs IS services Thanks to our expertise we can support IT team to reach their productivity & quality objectives (Assessment, Coaching, Support, Training, Resource delegation…) IS Solutions Take benefit from commercial or Open Source platform to answer as quick as possible to specific needs IS users services We can support Product & Services owners to work closely with the IT team (Assessment, Coaching, Support, Training, Resource delegation…) 4 Software Development & SoftwareMaintenance 2 ISSolutions IS Services Agility Agility 3 1 2 3 4 Agility
5. NEXT TRAININGS & CERTIFICATIONS 15 July 2010 Agile Mëtteg - Agile testing 5 -15% Complete calendar on: http://www.agilepartner.net/training/training_calendar.html
7. PRESENTATION OF THE ATTENDEES Who are you ? What is your role ? What do you know about agility ? What are your expectations ? July 15th, 2010 Agile Mëtteg – Agile Testing 7
8. AGENDA Agenda What is agile testing? And why? And how? Unit testing Test Driven Development Acceptance testing Behaviour Driven Development 15 July 2010 Agile Mëtteg - Agile testing 8
9. WHAT IS SOFTWARE TESTING? Definition: Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. (Wikipedia) 15 July 2010 Agile Mëtteg - Agile testing 9
10. WHAT IS SOFTWARE TESTING? Definition: Software testing is a way to measure the quality of the product using tests. (Stephan Zimmer & Eric Ferrot) 15 July 2010 Agile Mëtteg - Agile testing 10
11. MEASURING QUALITY Measuring quality using tests: tests to find defects functional / non-functional testing a LOT of kinds of tests 15 July 2010 Agile Mëtteg - Agile testing 11
12. 15 July 2010 Agile Mëtteg - Agile testing 12 SO WHAT IS AGILE TESTING ?… AND WHY?… AND HOW?
13. Traditional / Waterfall approach Testing is done after the development WHAT IS AGILE TESTING? 15 July 2010 Agile Mëtteg - Agile testing 13
14. Agile approach Testing is part of the development process WHAT IS AGILE TESTING? 15 July 2010 Agile Mëtteg - Agile testing 14 Iteration 1 Iteration 2 Iteration n No specific order
15. WHAT IS AGILE TESTING? 15 July 2010 Agile Mëtteg - Agile testing 15 Programmer Traditional / Waterfall approach Testing is done after the development Clear separation of roles Domain Expert Tester
16. Agile approach Testing is part of the development process A whole team WHAT IS AGILE TESTING? 15 July 2010 Agile Mëtteg - Agile testing 16 Programmer Programmer Domain Expert Tester Tester
17. Agile testing places an increased portion of the testing in the hands of the developers Wait… WHAT?!?! I’m a programmer not a tester It’s trivial I don’tneed a test I don’t have time for testing My code isverydifficult to test WHAT IS AGILE TESTING? 15 July 2010 Agile Mëtteg - Agile testing 17
18. WHY AGILE TESTING? WHY should developers write tests? Fear / Confidence Do you dare to change the code? Tests = safety net It places developers as users Better usability It makes the code testable Better design 15 July 2010 Agile Mëtteg - Agile testing 18
19. WHY AGILE TESTING? A better design “How good the design is doesn't matter near as much as whether the design is getting better or worse. If it is getting better, day by day, I can live with it forever. If it is getting worse, I will die.” (Kent Beck ) 15 July 2010 Agile Mëtteg - Agile testing 19
20. AGILE TESTING… HOW? Agile testing… HOW? Unit testing Test Driven Development Acceptance testing Behaviour Driven Development 15 July 2010 Agile Mëtteg - Agile testing 20
21. BUT FIRST… 15 July 2010 Agile Mëtteg - Agile testing 21
22. LET US INTRODUCE YOU TO… 15 July 2010 Agile Mëtteg - Agile testing 22 TIME MASTER TIM!
23. AGILE TESTING… HOW? DINO LEGS A real project A new feature: „The Crystal Quest“ 15 July 2010 Agile Mëtteg - Agile testing 23 http://dinolegs.blogspot.com/
25. UNIT TESTING Definitions Unit : Smallest testable part of an application Unit test : A method to test a unit 15 July 2010 Agile Mëtteg - Agile testing 25
26. UNIT TESTING Some bad things about unit tests: Expensive to write and expensive to maintain You can test too much You can test the wrong things Possibility to get false sense of security when all tests pass No integration tests 15 July 2010 Agile Mëtteg - Agile testing 26
27. UNIT TESTING Why write unit tests? More confidence in the code Avoid regression Tests themselves are documentation Encourages better software design: minimal interfaces and modularity 15 July 2010 Agile Mëtteg - Agile testing 27
28. UNIT TESTING The „3A“ pattern Arrange Act Assert 15 July 2010 Agile Mëtteg - Agile testing 28
29. UNIT TESTING F.I.R.S.T. Fast Independent Repeatable Self-Validating Timely [Clean Code – Robert C. Martin] 15 July 2010 Agile Mëtteg - Agile testing 29
30. UNIT TESTING „The act of writing a unit test is more an act of design than of verification“ (Robert C. Martin) 15 July 2010 Agile Mëtteg - Agile testing 30
31. UNIT TESTING A lot of existing unit testing… xUnit (NUnit, Junit, csUnit, …), MSTest, Pex, Visual Studio UTF, etc. …and mocking frameworks Moq, Rhino Mocks, Moles, TypeMock, JMock, etc. 15 July 2010 Agile Mëtteg - Agile testing 31
33. TEST DRIVEN DEVELOPMENT (TDD) 15 July 2010 Agile Mëtteg - Agile testing 33 Unit Test What is TDD? Difference to unit testing Write the unit test Code FIRST!
34. TEST DRIVEN DEVELOPMENT (TDD) What is TDD? Difference to unit testing Write the unit test FIRST! « Red – Green – Refactor » pattern 15 July 2010 Agile Mëtteg - Agile testing 34
35. TEST DRIVEN DEVELOPMENT (TDD) Red – Green – Refactor Make it failwrite the test first Make it workwrite the simplest implementation Make it betterrefactor without changing the behavior 15 July 2010 Agile Mëtteg - Agile testing 35
36. TEST DRIVEN DESIGN (TDD) TDD is not only about testing Also called Test Driven Design TDD is a methodology that helps creating a good design when developing code. 15 July 2010 Agile Mëtteg - Agile testing 36
37. TEST DRIVEN DESIGN (TDD) TDD is not only about testing Also called Test Driven Design TDD consequences YAGNI DRY Law of Demeter Single responsibility principle Interface segregation principle Inversion of control 15 July 2010 Agile Mëtteg - Agile testing 37 GOOD DESIGN !
40. ACCEPTANCE TESTING Unit testing tells us that the code is meeting the programmer‘s expectations Unit testing is essential but not sufficient Acceptance tests are specifications for the desired behaviour and functionality of a system. Customer oriented About the what and not the how Usually black box system tests Integration tests character 15 July 2010 Agile Mëtteg - Agile testing 40
41. ACCEPTANCE TESTING Implementing acceptance tests means automation Examples of automation tools: Framework for Integrated Test (Fit) is an open-source tool for automated acceptance test Fitnesse is a webserver, a wiki and an automated testing tool based on Fit 15 July 2010 Agile Mëtteg - Agile testing 41
44. BEHAVIOUR DRIVEN DEVELOPMENT Behaviour Driven Development (BDD) Evolution of TDD introduced by Dan North Using terminology focused on the behavioural aspects of the system rather than testing Unit ≠ behaviour Focus on why the code should be created Business value > Code Specification > Test 15 July 2010 Agile Mëtteg - Agile testing 44
45. BEHAVIOUR DRIVEN DEVELOPMENT Outside-in methodology from the known to the unknown Helps the developer to think YAGNI Leads to better design BDD = Behaviour Driven Design Don‘t forget about the roots (TDD) Red – Green – Refactor 15 July 2010 Agile Mëtteg - Agile testing 45
46. BEHAVIOUR DRIVEN DEVELOPMENT Programmer Ubiquitous language based on the business domain Common vocabulary between participants Minimizes translation Avoids miscommunication Makes it easier to validate early Domain Expert Tester 15 July 2010 Agile Mëtteg - Agile testing 46
47. BEHAVIOUR DRIVEN DEVELOPMENT Story framework Each feature is captured in a „story“, which defines the scope of the feature along with its acceptance criteria Feature Feature: Title As a [role] I want [feature] so that [benefit] Feature: Crystal quest As a player I want to collect time crystals so that I am able to complete the crystal quest 15 July 2010 Agile Mëtteg - Agile testing 47
48. BEHAVIOUR DRIVEN DEVELOPMENT Scenario / Acceptance criteria Scenario:Title Given some initial context, And some additional context, When an event occurs, Then ensure some outcomes Scenario 1:Tim loses a crystal Given a Tim is on screen And a crystal is on screen, When Tim dies, Then the crystal disappears And Tim‘s player score is decreased by 20 Scenario 2:Tim collects a crystal Given Tim is on screen And a crystal is on screen, When Tim touches the crystal, Then the crystal disappears And a nice music is played And Tim‘s player score is increased by 100 15 July 2010 Agile Mëtteg - Agile testing 48
49. BEHAVIOUR DRIVEN DEVELOPMENT Several existing tools for automation JBehave, NBehave, JSpec, NSpec, CppSpec, PHPSpec, SpecFlow, RSpec, Cucumber, … Executable specification Quick feedback and regression testing Requirements are tests Tests are documentation 15 July 2010 Agile Mëtteg - Agile testing 49
52. SUMMARY Some things to remember about Agile Testing: Testing is part of the development process Whole-team approach: roles not that strictly separated as in traditional approach Building a testable architecture leads to a better design ... and don‘t forget! Setup a working environment 15 July 2010 Agile Mëtteg - Agile testing 52
SZThe goal of unit testing is to isolate each part of the program and show that the individual parts are correct.Unit tests find problems early in the development cycle.A unit test provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits.
SZ
SZMore confidence in the codeAvoid regression: If tests are run frequently the developer can see when new code breaks old code.The tests themselves are documentationEncourages better software design: simpler, smaller methods; less coupling instead of strongly coupled code[Compare introduction, maybe too similar?]
SZPrinciples for unit testsIt’s much easier to see:What is being set up and initialized in the arrange section What method is being executed in the act section What determines the outcome of the test in the assert section
SZ
SZOriginated in XP.Unit tests are essential parts of XP and other agile methods.
SZ
ERF
ERF
ERF
ERF
ERF
ERF
ERF
SZ
SZAcceptance tests are specifications for the desired behavior and functionality of a system. WHY?Although acceptance testing traditionally takes place at the end of development or major milestones, in agile software development acceptance testing needs to be performed at the user story level. There are several reasons for why this is important:A passed test case becomes a measure of completeness of a user story; that is, a user story cannot be considered complete till it has passed all acceptance tests associated with it. Even though there is thorough unit testing performed, this is not enough. Unit tests, by their nature, test for a localized used case and are not concerned about the overall system. When we have iterations longer than a couple of weeks, it becomes easy to loose focus on initial agreements; acceptance test cases made for each story at the beginning of each iteration help the developers to keep things within the expectations. Acceptance test cases can serve as an excellent guide to developers to better interpret the requirements from a user story
SZFit – the engineThe customers' examples are formatted in tables and saved as HTML using ordinary business tools such as Microsoft Excel. When Fit checks the document, it creates a copy and colors the tables green, red, and yellow according to whether the software behaved as expected. Fitnesse – Also the wiki on topFitNesse allows users of a developed system to enter specially formatted input (its format is accessible to non-programmers). This input is interpreted and tests are created automatically. These tests are then executed by the system and output is returned back to the user. The advantage of this approach is very fast feedback from users. The developer of the system to be tested needs to provide some support (classes named "fixtures", conforming to certain conventions). fast user feedbackERF demo -> score computation dino legs
ERF
SZI
SZBehavior-driven developmentBDD aims to help focus on the delivery of prioritised, verifiable business value by providing a common vocabularyBy using terminology focused on the behavioural aspects of the system rather than testing, BDD attempts to help direct developers towards a focus on the real value to be found in TDD at its most successful. "Behavior-driven development is what you are doing already, if you are doing Test-driven development well." (Dave Astels)Behavior Driven Development is more about interactions with the application than just unit testing. It forces the developer to understand the responsibility of the method he is about to write. Using good tools, the specs written to test the application can be used as specifications. Doing what comes naturallyBDD isn't anything new or revolutionary. It's just an evolutionary offshoot of TDD in which the word "test" is replaced by the word "should." Semantics aside, many people find the concept of should a much more natural development driver than the concept of testing. Thinking in terms of behavior (shoulds) somehow paves the way into writing specification classes first, which, in turn, can be a very efficient implementation driver.For many developers, the shift from test-driven development to BDD is a smart move. With BDD, you don't have to think about tests, you can just pay attention to the requirements of your application and ensure that the application behavior does what it should to meet those requirements. Using BDD to drive development Behavior driven development (BDD) is an evolutionary result of test driven development (TDD) in the sense that rather than thinking in terms of tests (which have the tendency to make you think after the fact) you can more easily think in terms of a specification. By thinking about an application’s specification or behavior, it becomes easier to validate things early– in fact, when thinking in terms of a specification, it becomes quite easy to write things upfront.
SZ
SZBDD relies on the use of a very specific (and small) vocabulary to minimize miscommunication and to ensure that everyone – the business, developers, testers, analysts and managers – are not only on the same page but using the same words. BDD provides a “ubiquitous language” for analysis Around this time, Eric Evans published his bestselling book Domain-Driven Design. In it, he describes the concept of modeling a system using a ubiquitous language based on the business domain, so that the business vocabulary permeates right into the codebase.
SZIStructural templatesFeature:As a [X]I want [Y]so that [Z] (In order)The template had to be loose enough that it wouldn’t feel artificial or constraining to analysts but structured enough that we could break the story into its constituent fragments and automate them. We started describing the acceptance criteria in terms of scenarios, which took the following form:Scenarios:Given some initial context (the givens),When an event occurs,then ensure some outcomes.
SZIStructural templatesFeature:As a [X]I want [Y]so that [Z] (In order)The template had to be loose enough that it wouldn’t feel artificial or constraining to analysts but structured enough that we could break the story into its constituent fragments and automate them. We started describing the acceptance criteria in terms of scenarios, which took the following form:Scenarios:Given some initial context (the givens),When an event occurs,then ensure some outcomes.