Tech breakfast at Lab49
•Download as PPTX, PDF•
0 likes•270 views
The document discusses Behavior Driven Development (BDD) as an agile approach. It outlines how traditional projects can fail by delivering late, the wrong thing, or being unstable. BDD focuses on working software, customer collaboration, and responding to change. It describes the costs of going agile and three principles of BDD: only do enough upfront work to get started, deliver stakeholder value, and describe behavior at any level of detail. BDD tests what an object does, versus traditional test-driven development (TDD) testing what an object is. An example is provided of building a Set implementation in Java using BDD.
Report
Share
Report
Share
Recommended
Agile Development in .NET
The is from the book Agile Development in .NET by Dan Hermes. Most Agile methodologies used in .NET shops nationwide are variations of Scrum and Extreme Programming(XP). This booklet covers these tools and techniques: Test-driven Development (TDD), Behavior-driven Development (BDD), Continuous Integration (CI), and Refactoring to Patterns. The QuickNotes series covers relevant topics in software development to provide the reader with a swift overview of important trends, terms, and concepts. This book is available at Amazon.com.
Droidcon Create Your Gradle Plugin
Code sample: https://github.com/nhachicha/sample_gradle_plugin
Video:
http://youtu.be/xoSkz0ICWG4
Gradle is becoming more & more adopted by developers as their main build system especially after the release of Android Studio.
Thanks to the plugins architecture, Gradle allows users to reuse patterns and practices, avoiding boilerplate build code.
In this session, we will focus on creating a Plugin that cooperate with the existing "android plugin", in order to demonstrate some key concepts like: Tasks, Lifecycle, defining a custom DSL, incremental build and testing ...
we conclude by giving an overview of some useful Plugins that will boost your CI process.
Spec(ing) Out Your Workflow with SpecFlow
The document introduces SpecFlow, an open source tool for .NET that supports behavior-driven development (BDD) and acceptance test-driven development (ATDD). It discusses BDD and ATDD workflows and guidelines. The document also overview SpecFlow's features like support for platforms, test runners, and installation methods. It demonstrates using Gherkin language to write executable specifications and SpecFlow's workflow of specifying features, developing code, and testing.
Into the domain
Domain-driven design (DDD) is an approach to developing software for complex needs by deeply connecting the implementation to an evolving model of the core business concepts.
TDD with Ruby
The document discusses Test-Driven Development (TDD) with Ruby. It notes that the primary goal of TDD is specification and design, not just validation, by thinking through requirements and design before writing code. The TDD cycle involves adding a test, running all tests to see the new one fail, writing code to pass the test, refactoring code, and repeating. There are two levels of TDD: acceptance TDD which writes a single acceptance test and just enough code to pass it; and developer TDD which writes a single unit test and code to pass that test.
BDD API Tests with Gherkin and Behat
Given the prominence of API-first development when developing web applications, projects then need to be tested beyond unit and functional tests. Authoring tests using the Gherkin language with the framework Behat provides a way to achieve BDD with APIs. We'll dive right into writing Gherkin, how to create your own scenarios in Gherkin, and how to hook those tests up with custom PHP test methods. See tests in action with live coding and live demos, including writing new tests. Leave excited to produce fully-tested APIs!
Agile engineering practices – a short overview
This document provides a short overview of agile engineering practices, including Scrum, XP, Kanban, FDD, and DSDM. It summarizes key practices such as pair programming, test-driven development, behavior driven development, acceptance testing, exploratory testing, polyglot programming, domain specific languages, continuous integration, continuous testing, static code checking, agile databases, lightweight domain modeling, and continuous delivery. Each practice is briefly described in one slide with information on feedback time, styles, and challenges.
Scala from the Trenches - Java One 2016
This document summarizes a presentation on test-driven development (TDD) and clean code. It introduces TDD concepts like writing tests before code, refactoring, and using fakes, stubs, and mocks for testing. It then demonstrates a use case of developing a throttling mechanism to prevent denial-of-service attacks on a prize game service. Code for the throttler and demo app are provided in GitHub links. The presentation concludes with information about the speaker and an invitation for questions.
Recommended
Agile Development in .NET
The is from the book Agile Development in .NET by Dan Hermes. Most Agile methodologies used in .NET shops nationwide are variations of Scrum and Extreme Programming(XP). This booklet covers these tools and techniques: Test-driven Development (TDD), Behavior-driven Development (BDD), Continuous Integration (CI), and Refactoring to Patterns. The QuickNotes series covers relevant topics in software development to provide the reader with a swift overview of important trends, terms, and concepts. This book is available at Amazon.com.
Droidcon Create Your Gradle Plugin
Code sample: https://github.com/nhachicha/sample_gradle_plugin
Video:
http://youtu.be/xoSkz0ICWG4
Gradle is becoming more & more adopted by developers as their main build system especially after the release of Android Studio.
Thanks to the plugins architecture, Gradle allows users to reuse patterns and practices, avoiding boilerplate build code.
In this session, we will focus on creating a Plugin that cooperate with the existing "android plugin", in order to demonstrate some key concepts like: Tasks, Lifecycle, defining a custom DSL, incremental build and testing ...
we conclude by giving an overview of some useful Plugins that will boost your CI process.
Spec(ing) Out Your Workflow with SpecFlow
The document introduces SpecFlow, an open source tool for .NET that supports behavior-driven development (BDD) and acceptance test-driven development (ATDD). It discusses BDD and ATDD workflows and guidelines. The document also overview SpecFlow's features like support for platforms, test runners, and installation methods. It demonstrates using Gherkin language to write executable specifications and SpecFlow's workflow of specifying features, developing code, and testing.
Into the domain
Domain-driven design (DDD) is an approach to developing software for complex needs by deeply connecting the implementation to an evolving model of the core business concepts.
TDD with Ruby
The document discusses Test-Driven Development (TDD) with Ruby. It notes that the primary goal of TDD is specification and design, not just validation, by thinking through requirements and design before writing code. The TDD cycle involves adding a test, running all tests to see the new one fail, writing code to pass the test, refactoring code, and repeating. There are two levels of TDD: acceptance TDD which writes a single acceptance test and just enough code to pass it; and developer TDD which writes a single unit test and code to pass that test.
BDD API Tests with Gherkin and Behat
Given the prominence of API-first development when developing web applications, projects then need to be tested beyond unit and functional tests. Authoring tests using the Gherkin language with the framework Behat provides a way to achieve BDD with APIs. We'll dive right into writing Gherkin, how to create your own scenarios in Gherkin, and how to hook those tests up with custom PHP test methods. See tests in action with live coding and live demos, including writing new tests. Leave excited to produce fully-tested APIs!
Agile engineering practices – a short overview
This document provides a short overview of agile engineering practices, including Scrum, XP, Kanban, FDD, and DSDM. It summarizes key practices such as pair programming, test-driven development, behavior driven development, acceptance testing, exploratory testing, polyglot programming, domain specific languages, continuous integration, continuous testing, static code checking, agile databases, lightweight domain modeling, and continuous delivery. Each practice is briefly described in one slide with information on feedback time, styles, and challenges.
Scala from the Trenches - Java One 2016
This document summarizes a presentation on test-driven development (TDD) and clean code. It introduces TDD concepts like writing tests before code, refactoring, and using fakes, stubs, and mocks for testing. It then demonstrates a use case of developing a throttling mechanism to prevent denial-of-service attacks on a prize game service. Code for the throttler and demo app are provided in GitHub links. The presentation concludes with information about the speaker and an invitation for questions.
Kimmo Hakala. Comaqa Spring 2018. Challenges and good QA practices in softwar...
This presentation is based on Kimmo’s experiences in product component QA at Qvantel and it is aimed at everyone willing to know and understand, what are the challenges we’re facing in QA during software product development in BSS & Telco domain and, in the other hand, what are the good practices and success factors, so that we are able to 1. Test the product properly 2. Deliver smoothly and also 3. Continuously improve. The perspective of the presentation is “managerial”. However, we will also discuss about the technical and methodical aspects in component testing like different test levels, methods, test automation, test data management and testing tools. We also take a look at the different expectations towards testing personnel, like documentation, visibility of test activities, re-usable test assets etc. Finally we discuss about the key success factors in QA for software product development.
Spec flow – functional testing made easy
The document introduces behavioral driven development (BDD) and the tools SpecFlow and WatiN. It discusses how BDD emerged from traditional testing practices to address limitations. SpecFlow allows writing tests in a readable format and generates unit tests. WatiN enables browser testing. The combination of SpecFlow and WatiN facilitates automated functional testing by writing tests in a business-readable format and executing them in a browser.
Scala from the Trenches
Kfir Bloch gave a presentation on test-driven development (TDD) and clean code. He defined some common TDD and clean code terms like unit testing, fakes, collaborators, stubs, matchers, integration tests, refactoring, and mocks. Bloch also demonstrated a use case of implementing a throttling mechanism for a prize server to prevent players from repeatedly requesting prizes. He showed how to refactor the code using TDD principles. Finally, Bloch invited the audience to connect with him on LinkedIn and GitHub or email him about open roles at Wix.
Enhance Your Code Quality with Code Contracts
http://stiller.co.il/blog/2013/03/wf-4-5-and-code-contracts-slide-decks-and-code/
If you ever used a 3rd party API, you surely know the importance of proper documentation - Can this method return "null"? Do I have to check this return value? What are the valid values of this argument? You also probably know that the only way to discover if your assumptions are correct is to execute the code and pray that exceptions won't be flying around. There must be a better way!
Enter "Code Contracts". Code Contracts is an experimental project from Microsoft Research which provides a language-agnostic way to express coding assumptions in .NET programs, thus allowing for improved testability, static verification at compile time and automatic API documentation.
In this session we'll take a tour around Code Contracts, understand when and how we can use them, and show how correct usage of these constructs can significantly increase the quality of your code.
Introduction to Aspect Oriented Programming (DDD South West 4.0)
Introduction to AOP talk at DDD SouthWest 4.0, including examples of AOP using dynamic proxies, functional programming, dynamic language and PostSharp.
Presentation of agile engineering practices
Overview of the different aspects of agile engineering practices (the modern practices for software development) and how they can be adopted in [agile] teams.
Behavior Driven GUI Testing
This presentation introduces the audience to BDD - the Behavior-Driven Development method and how it can be applied to development and testing of GUI applications. We will also try to debunk myths and false hopes surrounding it.
BDD centers around stories written in an "ubiquitous language" that describe the expected behavior of an application. The use of a human-readable language allows for technical as well as non-technical project stakeholders to participate in authoring of feature descriptions. Those descriptions then serve as a base for the work of both developers and testers.
Classic agile and test-driven programming takes an inside-out approach by focussing on the specification and testing of the API of individual software components. BDD, on the other hand, looks at the application as a whole and puts interaction sequences and their expected outcomes into the foreground.
An introduction to the de-facto standard BDD language Gherkin will be given. It became popular as part of the Cucumber Ruby testing framework but has found its way into various free and commercial tools that will be listed.
A sample feature file including scenarios, outlines and backgrounds descriptions will be developed live using the Squish GUI Tester. This feature file can already be "run" in dry mode. We'll see different types of usage of this input:
* A mean to communicate with the customer.
* Documentation for the acceptance test before delivery
* A sequence to walk through for manual testing
* Automated GUI testing through tools like Squish.
Continuous Delivery with Jenkins: the Good, the Bad and the Ugly - JAX DevOps...
Jenkins is one of the most popular tools for Continuous Integration and Continuous Delivery today. It’s easy to set up and get started with. But what are the best practices for building delivery pipelines with Jenkins? Should you use the traditional build jobs or opt for the new Jenkins pipelines? What options are there for, e.g. visualization or infrastructure as code support? How do I structure my shared libraries so that they’re easy to maintain?
In this talk, I’ll share my many years of experiences from working with Jenkins for Continuous Delivery. We’ll take a look at pros and cons of different approaches but also how Jenkins compares to its competitors, where it shines, and where it leaves room for improvement.
Presented at JAX DevOps & Finance, London, United Kingdom on April 10th 2018.
Understanding Why Testing is Importaint
The document discusses the importance of testing code through test-driven development (TDD) and behavior-driven development (BDD). It explains that TDD involves writing tests, watching them fail, making them pass, refactoring, and repeating. BDD is more complex and involves business analysts, developers, and stakeholders specifying desired behaviors as user stories. The document encourages writing unit tests because it allows for quick code changes with confidence, helps understand code design, and documents expected behavior, though it takes time initially.
Death to project documentation with eXtreme Programming
How to connect the agile principle "Working software over comprehensive documentation" with eXtreme Programming values of Honest communication and Rapid feedback and practices as TDD, Continuous integration, Whole team and Small releases.
We will analyze why blending those ideas and techniques together in the real world, remove any need of upfront documentation and increases quality, communication and confidence.
(Agile) engineering best practices - What every project manager should know
Non technical guide to engineering best practices. Should be applied on IT projects, regardless of Agile or not.
DOES14 - David Ashman - Blackboard Learn - Keep Your Head in the Clouds
Blackboard, a provider of educational technology software, transitioned from an on-premise model to a cloud-based model through DevOps practices. They faced issues like long development cycles, poor communication between teams, and high failure rates during testing. By adopting automation, using cloud infrastructure, and shifting their culture, Blackboard was able to reduce lead times, improve feedback loops, and have developers take ownership of production issues. This included fully automating their testing pipeline, standardizing deployments across environments, and gaining executive support for cultural changes.
Agile testing principles and practices - Anil Karade
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Test Driven Development
Test Driven Development (TDD) involves writing tests before code to drive the development process. It emphasizes:
1. Starting with writing an acceptance test for the thinnest slice of functionality, known as a "walking skeleton".
2. Writing unit tests by following the "write tests backwards" approach of specifying the test name, call to code, and expectations before writing code to pass the test.
3. Using mock objects to guide interface design by specifying the required services of an object rather than its provided features, promoting narrow, role-based interfaces between objects.
QA Fest 2015. Gáspár Nagy. BDD Crash Course for Testers
I'm a developer. Similarly to other developers, I like dealing with technologies, architectures and solutions. I also like thinking about ways how to do this better and better. 2009 was the first time I encountered behavior driven development (BDD) -- as a tool to extend our agile development process to the entire project, including testers and product owners. BDD works like a glue that connects and reinforces agile methods you already use, making one plus one more than two.
BDD is still often regarded as a developer tool, so in this session, I would like to explain why Testers should care about BDD: What it is good for? What benefits you might expect? What is the role and responsibility of a tester in a BDD process? What is Gherkin and why do we care about vegetables at all?
TDD For Mortals
This document discusses test-driven development (TDD) and provides an agenda for a workshop on TDD. It begins by outlining the essence of TDD as write a failing test, make the test pass, refactor. It then uses an example of building a throttler to limit requests to demonstrate TDD. It notes some challenges with TDD like flaky tests and discusses architectural approaches like hexagonal architecture and using ports and adapters. It concludes by proposing a live coding example of designing a server using TDD and tests.
HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearB
Github Copilot and tools that help us code better are cool. But I’m lucky if I spend 90 minutes a day writing code. We really need to optimize the hours we spend reviewing code, updating tickets and tracing where our code is deployed. Learn how I save an hour a day streamlining non-coding tasks.
This talk is unique because 99% of developer productivity tools and hacks are about coding faster, better, smarter. And yet the vast majority of our time is spent doing all of this other stuff. After I started focusing on optimizing the 10 hours I spend every day on non-coding tasks, I found I my productivity went up and my frustration at annoying stuff went way down. I cover how to save time by reducing cognitive load and by cutting menial, non-coding tasks that we have to perform 10-50 times every day. For example:
Bug or hotfix comes through and you want to start working on it right away so you create a branch and start fixing. What you don’t do is create a Jira ticket but then later your boss/PM/CSM yells at your due to lack of visibility. I share how I automated ticket creation in Slack by correlating Github to Jira.
You have 20 minutes until your next meeting and you open a pull request and start a review. But you get pulled away half way through and when you come back the next day you forgot everything and have to start over. Huge waste of time. I share an ML job I wrote that tells me how long the review will take so I can pick PRs that fit the amount of time I have.
You build. You ship it. You own it. Great. But after I merge my code I never know where it actually is. Did the CI job fail? Is it release under feature flag? Did it just go GA to everyone? I share a bot I wrote that personally tells me where my code is in the pipeline after it leaves my hands so I can actually take full ownership without spending tons of time figuring out what code is in what release.
Sustainable agile testing
The agile community has done a very good job over the last few years in re-thinking the software development process and practices. What about testing though ? Are we really agile about it ? For most companies testing and QAs are still a bottleneck. In this session we will explore practices and techniques which will enable us to bring testing to the next level. We will focus particurarly on the concept of acceptance tests driven development and the role played by the "software developer in test"
Continuous delivery in practice (public)
Continuous delivery practices were implemented for an RTB project at Kenshoo to allow for faster development and delivery. This included having a single code branch, comprehensive testing at the unit, integration, behavioral, and staging levels, keeping builds stable, ensuring the master branch is always deployable, conducting rigorous code reviews, using real-time feedback, managing upgrades carefully, and A/B testing. It is important to constantly monitor builds and collect feedback to own the process.
Alexander Andelkovic. Comaqa Spring 2018. Using Artificial Intelligence to Te...
This document discusses using artificial intelligence to test levels in the Candy Crush Saga game. It describes King.com, the developer of Candy Crush, and their use of QA teams. It then covers using AI techniques like Monte Carlo tree search and neuroevolution to have automated bots play levels and provide feedback. This could help level designers, reduce human testing workload, and assist data scientists. Challenges include maintaining the bots and integrating them into King's development process.
Enter the mind of an Agile Developer
This document discusses BSG's approach to agile software development. It covers their use of agile methodologies like Scrum, test-driven development, behavior-driven development, and pair programming. It also describes their testing strategy, which uses a hybrid of BDD and TDD with a domain specific language. Tests are written at multiple levels, from acceptance to unit, and are run locally and through continuous integration with Jenkins.
Inside Behavior Driven Development
• What is Behavior Driven Development?
• What is its value?
• How does BDD differ from Test-Driven Development?
• What is the role of the customer/product owner in BDD?
• What about teams that have traditional manual testers?
• What about teams that have developers but not testers?
• What is a good BDD test?
• What should be tested manually?
More Related Content
What's hot
Kimmo Hakala. Comaqa Spring 2018. Challenges and good QA practices in softwar...
This presentation is based on Kimmo’s experiences in product component QA at Qvantel and it is aimed at everyone willing to know and understand, what are the challenges we’re facing in QA during software product development in BSS & Telco domain and, in the other hand, what are the good practices and success factors, so that we are able to 1. Test the product properly 2. Deliver smoothly and also 3. Continuously improve. The perspective of the presentation is “managerial”. However, we will also discuss about the technical and methodical aspects in component testing like different test levels, methods, test automation, test data management and testing tools. We also take a look at the different expectations towards testing personnel, like documentation, visibility of test activities, re-usable test assets etc. Finally we discuss about the key success factors in QA for software product development.
Spec flow – functional testing made easy
The document introduces behavioral driven development (BDD) and the tools SpecFlow and WatiN. It discusses how BDD emerged from traditional testing practices to address limitations. SpecFlow allows writing tests in a readable format and generates unit tests. WatiN enables browser testing. The combination of SpecFlow and WatiN facilitates automated functional testing by writing tests in a business-readable format and executing them in a browser.
Scala from the Trenches
Kfir Bloch gave a presentation on test-driven development (TDD) and clean code. He defined some common TDD and clean code terms like unit testing, fakes, collaborators, stubs, matchers, integration tests, refactoring, and mocks. Bloch also demonstrated a use case of implementing a throttling mechanism for a prize server to prevent players from repeatedly requesting prizes. He showed how to refactor the code using TDD principles. Finally, Bloch invited the audience to connect with him on LinkedIn and GitHub or email him about open roles at Wix.
Enhance Your Code Quality with Code Contracts
http://stiller.co.il/blog/2013/03/wf-4-5-and-code-contracts-slide-decks-and-code/
If you ever used a 3rd party API, you surely know the importance of proper documentation - Can this method return "null"? Do I have to check this return value? What are the valid values of this argument? You also probably know that the only way to discover if your assumptions are correct is to execute the code and pray that exceptions won't be flying around. There must be a better way!
Enter "Code Contracts". Code Contracts is an experimental project from Microsoft Research which provides a language-agnostic way to express coding assumptions in .NET programs, thus allowing for improved testability, static verification at compile time and automatic API documentation.
In this session we'll take a tour around Code Contracts, understand when and how we can use them, and show how correct usage of these constructs can significantly increase the quality of your code.
Introduction to Aspect Oriented Programming (DDD South West 4.0)
Introduction to AOP talk at DDD SouthWest 4.0, including examples of AOP using dynamic proxies, functional programming, dynamic language and PostSharp.
Presentation of agile engineering practices
Overview of the different aspects of agile engineering practices (the modern practices for software development) and how they can be adopted in [agile] teams.
Behavior Driven GUI Testing
This presentation introduces the audience to BDD - the Behavior-Driven Development method and how it can be applied to development and testing of GUI applications. We will also try to debunk myths and false hopes surrounding it.
BDD centers around stories written in an "ubiquitous language" that describe the expected behavior of an application. The use of a human-readable language allows for technical as well as non-technical project stakeholders to participate in authoring of feature descriptions. Those descriptions then serve as a base for the work of both developers and testers.
Classic agile and test-driven programming takes an inside-out approach by focussing on the specification and testing of the API of individual software components. BDD, on the other hand, looks at the application as a whole and puts interaction sequences and their expected outcomes into the foreground.
An introduction to the de-facto standard BDD language Gherkin will be given. It became popular as part of the Cucumber Ruby testing framework but has found its way into various free and commercial tools that will be listed.
A sample feature file including scenarios, outlines and backgrounds descriptions will be developed live using the Squish GUI Tester. This feature file can already be "run" in dry mode. We'll see different types of usage of this input:
* A mean to communicate with the customer.
* Documentation for the acceptance test before delivery
* A sequence to walk through for manual testing
* Automated GUI testing through tools like Squish.
Continuous Delivery with Jenkins: the Good, the Bad and the Ugly - JAX DevOps...
Jenkins is one of the most popular tools for Continuous Integration and Continuous Delivery today. It’s easy to set up and get started with. But what are the best practices for building delivery pipelines with Jenkins? Should you use the traditional build jobs or opt for the new Jenkins pipelines? What options are there for, e.g. visualization or infrastructure as code support? How do I structure my shared libraries so that they’re easy to maintain?
In this talk, I’ll share my many years of experiences from working with Jenkins for Continuous Delivery. We’ll take a look at pros and cons of different approaches but also how Jenkins compares to its competitors, where it shines, and where it leaves room for improvement.
Presented at JAX DevOps & Finance, London, United Kingdom on April 10th 2018.
Understanding Why Testing is Importaint
The document discusses the importance of testing code through test-driven development (TDD) and behavior-driven development (BDD). It explains that TDD involves writing tests, watching them fail, making them pass, refactoring, and repeating. BDD is more complex and involves business analysts, developers, and stakeholders specifying desired behaviors as user stories. The document encourages writing unit tests because it allows for quick code changes with confidence, helps understand code design, and documents expected behavior, though it takes time initially.
Death to project documentation with eXtreme Programming
How to connect the agile principle "Working software over comprehensive documentation" with eXtreme Programming values of Honest communication and Rapid feedback and practices as TDD, Continuous integration, Whole team and Small releases.
We will analyze why blending those ideas and techniques together in the real world, remove any need of upfront documentation and increases quality, communication and confidence.
(Agile) engineering best practices - What every project manager should know
Non technical guide to engineering best practices. Should be applied on IT projects, regardless of Agile or not.
DOES14 - David Ashman - Blackboard Learn - Keep Your Head in the Clouds
Blackboard, a provider of educational technology software, transitioned from an on-premise model to a cloud-based model through DevOps practices. They faced issues like long development cycles, poor communication between teams, and high failure rates during testing. By adopting automation, using cloud infrastructure, and shifting their culture, Blackboard was able to reduce lead times, improve feedback loops, and have developers take ownership of production issues. This included fully automating their testing pipeline, standardizing deployments across environments, and gaining executive support for cultural changes.
Agile testing principles and practices - Anil Karade
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Test Driven Development
Test Driven Development (TDD) involves writing tests before code to drive the development process. It emphasizes:
1. Starting with writing an acceptance test for the thinnest slice of functionality, known as a "walking skeleton".
2. Writing unit tests by following the "write tests backwards" approach of specifying the test name, call to code, and expectations before writing code to pass the test.
3. Using mock objects to guide interface design by specifying the required services of an object rather than its provided features, promoting narrow, role-based interfaces between objects.
QA Fest 2015. Gáspár Nagy. BDD Crash Course for Testers
I'm a developer. Similarly to other developers, I like dealing with technologies, architectures and solutions. I also like thinking about ways how to do this better and better. 2009 was the first time I encountered behavior driven development (BDD) -- as a tool to extend our agile development process to the entire project, including testers and product owners. BDD works like a glue that connects and reinforces agile methods you already use, making one plus one more than two.
BDD is still often regarded as a developer tool, so in this session, I would like to explain why Testers should care about BDD: What it is good for? What benefits you might expect? What is the role and responsibility of a tester in a BDD process? What is Gherkin and why do we care about vegetables at all?
TDD For Mortals
This document discusses test-driven development (TDD) and provides an agenda for a workshop on TDD. It begins by outlining the essence of TDD as write a failing test, make the test pass, refactor. It then uses an example of building a throttler to limit requests to demonstrate TDD. It notes some challenges with TDD like flaky tests and discusses architectural approaches like hexagonal architecture and using ports and adapters. It concludes by proposing a live coding example of designing a server using TDD and tests.
HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearB
Github Copilot and tools that help us code better are cool. But I’m lucky if I spend 90 minutes a day writing code. We really need to optimize the hours we spend reviewing code, updating tickets and tracing where our code is deployed. Learn how I save an hour a day streamlining non-coding tasks.
This talk is unique because 99% of developer productivity tools and hacks are about coding faster, better, smarter. And yet the vast majority of our time is spent doing all of this other stuff. After I started focusing on optimizing the 10 hours I spend every day on non-coding tasks, I found I my productivity went up and my frustration at annoying stuff went way down. I cover how to save time by reducing cognitive load and by cutting menial, non-coding tasks that we have to perform 10-50 times every day. For example:
Bug or hotfix comes through and you want to start working on it right away so you create a branch and start fixing. What you don’t do is create a Jira ticket but then later your boss/PM/CSM yells at your due to lack of visibility. I share how I automated ticket creation in Slack by correlating Github to Jira.
You have 20 minutes until your next meeting and you open a pull request and start a review. But you get pulled away half way through and when you come back the next day you forgot everything and have to start over. Huge waste of time. I share an ML job I wrote that tells me how long the review will take so I can pick PRs that fit the amount of time I have.
You build. You ship it. You own it. Great. But after I merge my code I never know where it actually is. Did the CI job fail? Is it release under feature flag? Did it just go GA to everyone? I share a bot I wrote that personally tells me where my code is in the pipeline after it leaves my hands so I can actually take full ownership without spending tons of time figuring out what code is in what release.
Sustainable agile testing
The agile community has done a very good job over the last few years in re-thinking the software development process and practices. What about testing though ? Are we really agile about it ? For most companies testing and QAs are still a bottleneck. In this session we will explore practices and techniques which will enable us to bring testing to the next level. We will focus particurarly on the concept of acceptance tests driven development and the role played by the "software developer in test"
Continuous delivery in practice (public)
Continuous delivery practices were implemented for an RTB project at Kenshoo to allow for faster development and delivery. This included having a single code branch, comprehensive testing at the unit, integration, behavioral, and staging levels, keeping builds stable, ensuring the master branch is always deployable, conducting rigorous code reviews, using real-time feedback, managing upgrades carefully, and A/B testing. It is important to constantly monitor builds and collect feedback to own the process.
Alexander Andelkovic. Comaqa Spring 2018. Using Artificial Intelligence to Te...
This document discusses using artificial intelligence to test levels in the Candy Crush Saga game. It describes King.com, the developer of Candy Crush, and their use of QA teams. It then covers using AI techniques like Monte Carlo tree search and neuroevolution to have automated bots play levels and provide feedback. This could help level designers, reduce human testing workload, and assist data scientists. Challenges include maintaining the bots and integrating them into King's development process.
What's hot (20)
Kimmo Hakala. Comaqa Spring 2018. Challenges and good QA practices in softwar...
Kimmo Hakala. Comaqa Spring 2018. Challenges and good QA practices in softwar...
Introduction to Aspect Oriented Programming (DDD South West 4.0)
Introduction to Aspect Oriented Programming (DDD South West 4.0)
Continuous Delivery with Jenkins: the Good, the Bad and the Ugly - JAX DevOps...
Continuous Delivery with Jenkins: the Good, the Bad and the Ugly - JAX DevOps...
Death to project documentation with eXtreme Programming
Death to project documentation with eXtreme Programming
(Agile) engineering best practices - What every project manager should know
(Agile) engineering best practices - What every project manager should know
DOES14 - David Ashman - Blackboard Learn - Keep Your Head in the Clouds
DOES14 - David Ashman - Blackboard Learn - Keep Your Head in the Clouds
Agile testing principles and practices - Anil Karade
Agile testing principles and practices - Anil Karade
QA Fest 2015. Gáspár Nagy. BDD Crash Course for Testers
QA Fest 2015. Gáspár Nagy. BDD Crash Course for Testers
HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearB
HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearB
Alexander Andelkovic. Comaqa Spring 2018. Using Artificial Intelligence to Te...
Alexander Andelkovic. Comaqa Spring 2018. Using Artificial Intelligence to Te...
Similar to Tech breakfast at Lab49
Enter the mind of an Agile Developer
This document discusses BSG's approach to agile software development. It covers their use of agile methodologies like Scrum, test-driven development, behavior-driven development, and pair programming. It also describes their testing strategy, which uses a hybrid of BDD and TDD with a domain specific language. Tests are written at multiple levels, from acceptance to unit, and are run locally and through continuous integration with Jenkins.
Inside Behavior Driven Development
• What is Behavior Driven Development?
• What is its value?
• How does BDD differ from Test-Driven Development?
• What is the role of the customer/product owner in BDD?
• What about teams that have traditional manual testers?
• What about teams that have developers but not testers?
• What is a good BDD test?
• What should be tested manually?
Javascript Tests with Jasmine for Front-end Devs
Jasmine isn't just for Rubyists - it's for anyone that wants to revolutionize their Javascript code and development workflow. I give a tutorial in getting up and running with an agile, Test Driven Development workflow using nothing but HTML and Javascript.
SanDiego_DevOps_Meetup_9212016
Mitchell International has been providing property and casualty claims services for 70 years. They are moving to continuous integration and delivery (CI/CD) to rapidly build and deliver quality software. Previously they had a slow "big build" system and manual testing. Now developers maintain componentized builds and immediately get feedback on check-ins through automated testing. It has been a journey over 7 years from centralized systems to empowering developers. They use tools like Jenkins and Artifactory to run over 1400 jobs daily across many platforms and deliver capabilities as a service.
SanDiego_DevOps_Meetup_9212016-v8
Mitchell International has been providing property and casualty claims services for 70 years. Raj Makkar and Richard Fong discuss Mitchell's journey to continuous integration and delivery over the past 7 years. They moved from a slow "big build" process controlled by one team to a componentized approach where developers control builds. Today, builds occur on every check-in with immediate feedback. They use tools like Jenkins and Artifactory to manage over 1400 jobs per day across many platforms. Their goal is rapid, quality software delivery through a culture of automation, testing, and collaboration across teams.
Behavior Driven Development by Example
A practical approach BDD using Cucumber-jvm and web driver with introduction to process and technology integration.
Colombo Selenium meetup group.
DevOps 及 TDD 開發流程哲學
This document discusses DevOps test-driven development (TDD). It introduces DevOps and TDD concepts and practices. It provides an example of using a Node.js test framework and API testing to implement TDD for a login feature. The document emphasizes that TDD is about designing better code through testing rather than just writing tests. It also discusses using continuous integration/delivery (CI/CD) pipelines to automatically run tests on code changes.
BDD presentation
The document discusses best practices for writing software that matters through techniques like behavior-driven development (BDD). It compares test-driven development (TDD) to BDD, noting that BDD shifts the focus from verification to specification by describing desired behaviors. The document also provides examples of how to structure user stories and define scenarios using a given-when-then format to plan development around customer needs.
Design For Testability
If you had an opportunity to build an application from the ground up, with testability a key design goal, what would you do?
In this presentation, we will look at just such a situation - a major, two year rewrite of a suite of core business systems. We will discuss how a system looks when testability is as important as functionality - and what it looks like when quality concerns are part of the initial design. We will look at the role of test automation and manual test in a modern project, and look at the tools and processes. The session will conclude with a demo of the latest visual test automation tool from MIT and a Q&A.
Tdd and bdd
a brief introduction to Test Driven Development and Behavior Driven Development and the main differences between both.
DevOps for AI Apps
DevOps for AI Applications - How to apply best practices from software engineering to the world of data science and machine learning
{10.0} Test Driven Development.pptx
Test driven development involves writing tests before writing code to make the tests pass. This ensures code is built to satisfy explicit requirements. The TDD process is: write a failing test, write code to pass the test, refactor code. This improves quality by preventing defects and ensuring code is maintainable through extensive automated testing. Acceptance TDD applies this process on a system level to build the right functionality.
Test driven development v1.0
This document outlines an agenda for a presentation on Test Driven Development (TDD) best practices. The agenda includes sections on an overview and introduction to TDD, what TDD is and the process, challenges of TDD, learning and best practices for sustaining TDD, frameworks and variations of TDD, and a question and answer period. Some key best practices discussed are writing tests before code, focusing tests on functionality rather than code structure, and establishing governance and training to ensure proper adoption of TDD.
Dev/Test scenarios in DevOps world
Do you want a deep dive into the dev/test portion of DevOps and application lifecycle management (ALM)?
Do you want an overview of unit testing, functional UI testing and load testing?
Do you want to learn about continuous deployment?
Do you want to walk through how testers ensure that business value is delivered?
This session is for you.
Lean-Agile Development with SharePoint - Bill Ayers
SharePoint gives us a great platform for developing sophisticated intranet portals and collaboration sites and many other workloads. But it can also be a challenge to use modern software development frameworks like Scrum and XP. Wouldn’t it be great if we could get all the benefits of Agile practices – faster development, predictable deliveries, better quality, less stress and happy stakeholders? In this session we will cover the definitions of Lean, Agile, Scrum, Kanban, XP, and TDD. Then we will look at the specific challenges around Agile SharePoint development and some development techniques to overcome these obstacles. This talk covers both project delivery and engineering. We’ll look at unit tests, integration tests, UI tests, continuous integration and, of course, test-driven development (TDD) with practical experiences from real-life Agile SharePoint projects.
Bdd with m spec
- BDD is an agile development methodology that focuses on defining software system behaviors through examples and specifications. It aims to improve engagement between developers and business stakeholders.
- BDD uses examples written in a Given-When-Then format to describe features. Frameworks like MSpec implement BDD using context/specification patterns with keywords like Establish context and It should.
- BDD specifications can describe behaviors at multiple levels of abstraction. Lower-level specs still maintain a focus on behavior over implementation details through practices like heavy mocking. This helps drive out design and catch errors early.
CBDW2014 - Behavior Driven Development with TestBox
This document introduces behavior driven development (BDD) and the TestBox testing framework for ColdFusion. It discusses how BDD builds upon test-driven development (TDD) principles by focusing on user stories and scenarios over isolated functions. TestBox allows writing BDD-style tests with expectations and supports different styles like xUnit. It provides features for parallel testing, mocking, reporting and integrating with build tools.
Implementation of Agile SDLC with JIRA and CICD.pptx
This document discusses implementing an Agile software development lifecycle with JIRA and CI/CD. It describes the benefits of Agile methodology, key Agile methods like Scrum and Kanban, and how JIRA supports Agile workflows through features like issues, projects, and agile boards. It also outlines how to set up continuous integration and delivery using Jenkins and Git to automate building, testing, and deploying code changes.
Scrum plus – why scrum is not enough for successful delivery
Why, where and how to include engineering practices in Scrum to maximize value of work done by development in Sprint.
Cleaner Code Through Test-Driven Development
Test-driven development (TDD) involves writing unit tests before production code to ensure features are correctly implemented and prevent future bugs. Following TDD best practices like writing only enough test code to fail and then just enough production code to pass helps improve code quality and productivity. Leading open source projects emphasize the importance of testing, with some requiring over 90% test coverage. Resources like books and articles provide guidance on techniques like TDD, refactoring, and working with legacy code.
Similar to Tech breakfast at Lab49 (20)
Lean-Agile Development with SharePoint - Bill Ayers
Lean-Agile Development with SharePoint - Bill Ayers
CBDW2014 - Behavior Driven Development with TestBox
CBDW2014 - Behavior Driven Development with TestBox
Implementation of Agile SDLC with JIRA and CICD.pptx
Implementation of Agile SDLC with JIRA and CICD.pptx
Scrum plus – why scrum is not enough for successful delivery
Scrum plus – why scrum is not enough for successful delivery
Recently uploaded
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Astute Business Solutions | Oracle Cloud Partner |
Your goto partner for Oracle Cloud, PeopleSoft, E-Business Suite, and Ellucian Banner. We are a firm specialized in managed services and consulting.
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Leveraging the Graph for Clinical Trials and Standards
Katja Glaß
OpenStudyBuilder Community Manager - Katja Glaß Consulting
Marius Conjeaud
Principal Consultant - Neo4j
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Gursev Pirge, PhD
Senior Data Scientist - JohnSnowLabs
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Mutation Testing for Task-Oriented Chatbots
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Principle of conventional tomography-Bibash Shahi ppt..pptx
before the computed tomography, it had been widely used.
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
What is an RPA CoE? Session 1 – CoE Vision
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Recently uploaded (20)
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Leveraging the Graph for Clinical Trials and Standards
Leveraging the Graph for Clinical Trials and Standards
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Principle of conventional tomography-Bibash Shahi ppt..pptx
Principle of conventional tomography-Bibash Shahi ppt..pptx
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Tech breakfast at Lab49
- 2. How traditional projects fail • Delivering Late or Over Budget • Delivering the Wrong Thing • Unstable in Production • Costly to Maintain
- 3. Agile • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan
- 4. Cost of going agile • Outcome-Based Planning • Streaming Requirements • Evolving Design • Changing Existing Code • Frequent Code Integration • Continual Regression Testing • Frequent Production Releases
- 5. Three principles of BDD • Enough is enough - Up-front planning, analysis, and design all have a diminishing return. We shouldn’t do less than we need to get started, but any more than that is wasted effort. • Deliver stakeholder value - If you are doing something that isn’t either delivering value or increasing your ability to deliver value, stop doing it, and do something else instead. • It’s all behavior - Whether at the code level, the application level, or beyond, we can use the same thinking and the same linguistic constructs to describe behavior at any level of granularity.
- 6. TDD vs BDD • TDD tests what an object is… • BDD tests what an object does…
- 7. Code Exercise • Build a Set implementation n java with the following APIs- • empty() • size() • add() • contains() • remove() • Dynamic expansion
- 8. Eclipse perspective Specification Code Test Runner
- 9. empty( ) specification Name of the test Pre conditions Expectation
- 10. empty( ) implementation Just enough to pass test case!!!!
- 13. BDD Lifecycle