Cucumber
•
1 like•544 views
BDD was created by Dan North in 2003 as an evolution of TDD to improve communication between customers and developers. It uses examples written in a business-readable language to define requirements and tests. Cucumber is a tool that supports BDD using a natural language syntax for writing tests in Ruby.
Report
Share
Report
Share
Download to read offline
Recommended
Creating multillingual apps for android
The document discusses creating multilingual Android applications. It defines key concepts like globalization, internationalization and localization. It then provides guidance on identifying localizable items, separating them from code, performing development, translating content, and integrating different languages into the app. The document recommends using resource folders to organize localized assets and strings. It also offers tips for ensuring high quality localization, including being politically correct and evaluating translation needs.
Mobile App-game Profile- personalive
This document describes Swapnica, a team of software developers and programmers with over 20 years of experience developing mobile apps, games, web, and server software. The team has experience using technologies like PHP, Ruby, Python, C++, and is licensed to develop for Nintendo, Xbox, and PlayStation. They offer full-cycle development including design, architecture, programming, visuals, and support. The team focuses on problem solving and has experience with popular web frameworks and technologies. They also discuss the importance of app design and their development process.
Flutter Interact Viewing Party - GDG, Abu dhabi
GDGs are local developer groups run by volunteers to support Google's developer technologies. They host events ranging from small technical video discussions to larger code sprints and hackathons. The presented document discusses an upcoming GDG event focused on Flutter, Google's UI toolkit that allows building mobile, web, and desktop apps using one codebase. The agenda includes introductions to Flutter, codelabs, networking, and a keynote on Flutter's capabilities and momentum in the industry.
Test and Behaviour Driven Development (TDD/BDD)
In this introduction to Test Driven Development (TDD) or Behaviour Driven Development (BDD) we give a high level description of what it is and why it is useful for developers. Then we go into some details on stubs and mocks, test data, UI testing, SQL testing, JavaScript testing, web services testing and how to start doing TDD/BDD on an existing code base.
BDD
The document discusses Behaviour Driven Development (BDD), which structures automated tests as executable specifications for software features and scenarios. BDD tests are written in a Given/When/Then format and serve as documentation of requirements and acceptance criteria. An example BDD test written in JavaScript is provided for a "Green Bottles" feature, testing that the number of bottles on the wall decreases by one each time one falls. BDD provides benefits like user-focused tests linked to stories that are technology-agnostic and refactor-friendly.
The Power of BDD
The document discusses different development techniques including test-driven development (TDD), acceptance-test-driven development (ATDD), and behavior-driven development (BDD). It explains that TDD focuses on unit tests, ATDD ensures shared understanding of acceptance criteria, and BDD follows TDD principles at a higher level and makes acceptance tests more readable. The document also presents BDD as a solution to bridge communication gaps between business and IT by using a domain-specific language with keywords like Feature, Scenario, Given, When, Then. Cucumber is introduced as a popular BDD tool that supports multiple programming languages and has a strong community.
Bdd
This document discusses Behavior Driven Development (BDD), an evolution of Test-Driven Development (TDD). BDD focuses on designing tests before implementation based on customer needs using a single language. It aims to improve software design, testability and decrease bugs through executable documentation and acceptance tests written by domain experts rather than developers. A list of common BDD tools is also provided.
greach 2014 marco vermeulen bdd using cucumber jvm and groovy
Using examples at multiple levels, Behavior Driven Development (BDD) creates a shared understanding to deliver software that matters. Cucumber allows writing executable specifications in a simple markup language called Gherkin and parsing them into tests. The Cucumber anatomy includes Gherkin features, step definitions that parse and execute the steps, and hooks to run code before and after scenarios. The Grails Cucumber plugin makes BDD easy in Grails through conventions, and was demonstrated in an example using GORM, Geb pages, and Spock specifications.
Recommended
Creating multillingual apps for android
The document discusses creating multilingual Android applications. It defines key concepts like globalization, internationalization and localization. It then provides guidance on identifying localizable items, separating them from code, performing development, translating content, and integrating different languages into the app. The document recommends using resource folders to organize localized assets and strings. It also offers tips for ensuring high quality localization, including being politically correct and evaluating translation needs.
Mobile App-game Profile- personalive
This document describes Swapnica, a team of software developers and programmers with over 20 years of experience developing mobile apps, games, web, and server software. The team has experience using technologies like PHP, Ruby, Python, C++, and is licensed to develop for Nintendo, Xbox, and PlayStation. They offer full-cycle development including design, architecture, programming, visuals, and support. The team focuses on problem solving and has experience with popular web frameworks and technologies. They also discuss the importance of app design and their development process.
Flutter Interact Viewing Party - GDG, Abu dhabi
GDGs are local developer groups run by volunteers to support Google's developer technologies. They host events ranging from small technical video discussions to larger code sprints and hackathons. The presented document discusses an upcoming GDG event focused on Flutter, Google's UI toolkit that allows building mobile, web, and desktop apps using one codebase. The agenda includes introductions to Flutter, codelabs, networking, and a keynote on Flutter's capabilities and momentum in the industry.
Test and Behaviour Driven Development (TDD/BDD)
In this introduction to Test Driven Development (TDD) or Behaviour Driven Development (BDD) we give a high level description of what it is and why it is useful for developers. Then we go into some details on stubs and mocks, test data, UI testing, SQL testing, JavaScript testing, web services testing and how to start doing TDD/BDD on an existing code base.
BDD
The document discusses Behaviour Driven Development (BDD), which structures automated tests as executable specifications for software features and scenarios. BDD tests are written in a Given/When/Then format and serve as documentation of requirements and acceptance criteria. An example BDD test written in JavaScript is provided for a "Green Bottles" feature, testing that the number of bottles on the wall decreases by one each time one falls. BDD provides benefits like user-focused tests linked to stories that are technology-agnostic and refactor-friendly.
The Power of BDD
The document discusses different development techniques including test-driven development (TDD), acceptance-test-driven development (ATDD), and behavior-driven development (BDD). It explains that TDD focuses on unit tests, ATDD ensures shared understanding of acceptance criteria, and BDD follows TDD principles at a higher level and makes acceptance tests more readable. The document also presents BDD as a solution to bridge communication gaps between business and IT by using a domain-specific language with keywords like Feature, Scenario, Given, When, Then. Cucumber is introduced as a popular BDD tool that supports multiple programming languages and has a strong community.
Bdd
This document discusses Behavior Driven Development (BDD), an evolution of Test-Driven Development (TDD). BDD focuses on designing tests before implementation based on customer needs using a single language. It aims to improve software design, testability and decrease bugs through executable documentation and acceptance tests written by domain experts rather than developers. A list of common BDD tools is also provided.
greach 2014 marco vermeulen bdd using cucumber jvm and groovy
Using examples at multiple levels, Behavior Driven Development (BDD) creates a shared understanding to deliver software that matters. Cucumber allows writing executable specifications in a simple markup language called Gherkin and parsing them into tests. The Cucumber anatomy includes Gherkin features, step definitions that parse and execute the steps, and hooks to run code before and after scenarios. The Grails Cucumber plugin makes BDD easy in Grails through conventions, and was demonstrated in an example using GORM, Geb pages, and Spock specifications.
Learning To Learn
A talk about how we learn and think, how we teach, and how our approach to thinking has remained largely unchanged in the West for over 2000 years.
First presented at the Better Software Conference in Las Vegas, June 2009.
Exactpro Systems for KSTU Students in Kostroma
This document discusses Exactpro Systems, an innovative trading systems company. It provides information on the company's history, team compositions for different offices including Kostroma, statistics on employee retention and attrition, the breakdown of departments, and descriptions of products developed including ClearTH, Mini-Robots, Dolphin, Shsha, and Load Injector. It also discusses the company's conference in Kostroma on software development and analysis topics.
Why Your Agile Rollout Is Failing
The Agile rollout is failing due to issues with the kick-off, planning, finance, communications, and facilitating change. The kick-off did not properly engage developers in the reasons for adopting Agile. Planning involved turning traditional plans on their side rather than adopting Agile practices. Finance prioritized existing tools and infrastructure over effectiveness. Communications failed to inform all stakeholders of the Agile approach. Facilitating change was hindered by short timescales and resistance to new technical practices and responsibilities. Lasting adoption requires understanding change management, systems thinking, and frequent small improvements.
No best practices?
The document discusses best practices and argues that they are often used to limit risk and enforce control but can stifle creativity. It notes that most fear, which often drives the adoption of best practices, is irrational. While best practices can help novices and advanced beginners, experts often subvert practices. True best practices should be context-dependent patterns that describe pros and cons rather than absolute prescriptions of behavior. In summary, software development is a creative endeavor, and the best approach to best practices is to provide descriptive patterns rather than prescriptive rules that can frustrate skilled professionals.
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.
Bdd Introduction
1) Behaviour-driven development (BDD) is an agile methodology that focuses on delivering working, tested software through collaboration between developers, testers and stakeholders.
2) BDD implements an application by describing its behavior through features and scenarios written from the perspective of stakeholders. Stories, acceptance criteria, executable examples and other tools are used to define requirements and guide development.
3) BDD aims to produce software that provides tangible value to stakeholders by being delivered incrementally, being easy to deploy and manage, and by adapting quickly to feedback through frequent testing and deployment.
Cucumber_Training_ForQA
This document provides an overview of the Cucumber testing tool. It discusses Behavior Driven Development (BDD) and how Cucumber enables BDD. The document covers the key components of Cucumber including Gherkin language, feature files, step definitions, and tags. It also provides examples of how Cucumber can be used with Selenium for automated testing and discusses Cucumber reports.
Behavior Driven Development Pros and Cons
The Cons of Behavior Driven Development (BDD)
Ivan Bobrov, ClubQA Co-Founder, Kostroma
The Pros of Behavior Driven Development (BDD): Business User Scenarios
Natalia Zaitseva, Exchange Functional Test Automation Lead Innovative Trading Systems
EXTENT Conference.
October 29-30, 2011
Test Automation for Trading Systems
Renaissance Hotel Moscow
BDD with the Cucumber
Behaviour Driven Development with The Cucumber
Test Pyramid
BDD Concept
Why BDD
Traditional Loop
Collaboration
Cucumber is the Tool
Cucumber structure
Sample feature
Gherkin is the Language
Step Definitions
Reqular Expressions
How the Cucumber Works
Expressive Scenarios
Outside-in development
Keeping your cucumbers sweet
Environment
Conclusion
BDD testing with cucumber
How to do behavior driven development with cucumber, generate easy readable and understandable test reports for your business.
Behavior Driven Development and Automation Testing Using Cucumber
This document discusses behavior-driven development (BDD) and automation testing using Cucumber. It begins with an example of a Cucumber scenario for logging into a system. It then demonstrates an automation test case written in Java and discusses how Cucumber executes scenarios. The rest of the document outlines an agenda to discuss BDD, Cucumber automation, developing a Cucumber framework, and the pros and cons of BDD and Cucumber.
Cucumber-III
The document discusses Cucumber, a tool for behavior driven development. It introduces Cucumber and how it is used for writing acceptance tests. Key components of Cucumber include feature files that contain scenarios in Given, When, Then format and step definitions that implement the scenario steps in code. The document provides examples of feature files and step definitions.
Behavior Driven Development (BDD) and Agile Testing
The document discusses Behaviour Driven Development (BDD) and how it uses frameworks like Cucumber to define user stories and acceptance criteria in a structured format known as feature files. This allows for collaboration between stakeholders and helps ensure quality by building tests into the requirements process from the start. Feature files also provide traceability and make adapting to changes easier.
BDD in Action – principles, practices and real-world application
Behaviour-driven development (BDD) started as an improved variation on test-driven development, but has evolved to become a formidable tool that helps teams communicate more effectively about requirements, using conversation and concrete examples to discover what features really matter to the business. BDD helps teams focus not only on building features that work, but on ensuring that the features they deliver are the ones that the client actually needs.
In this talk, we will discuss what BDD is about, its benefits, and how it affects teams and processes. We will discuss two case studies where BDD practices have been successfully introduced, including the benefits gained and challenges met. We will see how much benefit was gained when BDD was integrated into the broader development infrastructure, including issue tracking systems, requirements management, and project reporting.
We will also see how BDD can be applied to all levels of the development process, from requirements down to low-level coding. We will also look at the principle BDD tools available that can help teams implement executable specifications, BDD-style test automation, and living documentation effectively. Some of the tools discussed will include JBehave, Cucumber, Specflow, Jasmine and Spock.
We will also look at two case studies where BDD practices have been successfully integrated into several projects in large government and financial organizations. Teams that adopted BDD effectively benefited from significantly lower defect rates, much earlier discovery of errors and inconsistencies in the requirements, and better overall communication and collaboration within the team. However, practicing BDD does involve a significant change in mind-set compared to more traditional approaches, a different collaboration model between team members, and a high degree of stakeholder by-in and engagement, all of which should not be underestimated. We will discuss how the teams managed these various challenges during their BDD adoption story.
Behavior Driven Development
Annotated slides from my "Behavior Driven Development" course. Released under Creative Commons share-alike, commercial and derivatives allowed: http://creativecommons.org/licenses/by-sa/3.0/
BDD in Action - building software that matters
Behaviour-driven development (BDD) started as an improved variation on test-driven development, but has evolved to become a formidable tool that helps teams communicate more effectively about requirements, using conversation and concrete examples to discover what features really matter to the business. BDD helps teams focus not only on building features that work, but on ensuring that the features they deliver are the ones the client actually needs.
Learn what BDD is, and what it is not
Understand that the core of BDD is around conversation and requirements discovery, not around tools.
Understand the difference and similarities between BDD at the requirements level, and BDD at the coding level.
Learn what BDD tools exist for different platforms, and when to use them
Naming Things Book : Simple Book Review!
The document discusses principles for naming identifiers in code such as variables, classes, and functions. It notes that naming is important because identifiers make up 70% of code and influence comprehension, recall, and bug fixing time. Good naming follows principles like understandability, using names that describe concepts, and consistency. It provides specific rules for naming classes, variables, functions for conciseness, consistency, and distinguishability. The goal is to use names that are understandable to both current and future engineers working on the code.
Continuous Discovery Habits Book Review.pdf
This document summarizes key points from the book "Continuous Discovery Habits" by Diego Pacheco. It advocates for continuous discovery through an outcome-oriented and customer-centric mindset. Discovery requires the collaboration of product managers, designers, and engineers to iteratively test assumptions and validate ideas with customers. The goal is to ensure teams are creating value for users and addressing their needs, pain points, and desires on an ongoing basis through experimental and visual approaches.
Thoughts about Shape Up
This document discusses the Shape Up methodology for agile software development projects. It introduces Shape Up as similar to Dual Track Agile, with an initial 6-week discovery process. Key aspects of how shaping works include setting boundaries, roughing out elements, addressing risks, writing a pitch, and creating simple breadboarding prototypes. Other topics covered are cutting scope, how the pitch works, using betting tables instead of backlogs, dealing with bugs, and making progress on the whole stack through scope mapping and discovery charts.
Holacracy
This document discusses Holacracy, an alternative organizational structure to traditional hierarchies. It notes that current management structures were designed for factories, while Holacracy is designed for humans. Holacracy eliminates hierarchies and instead focuses on clearly defined roles and circles within an organization. It aims to embrace autonomy through separating people from roles and having roles, not managers, make decisions. While challenging to implement due to issues of power, some companies have adopted aspects of Holacracy.
AWS IAM
This document discusses AWS Identity and Access Management (IAM). It provides an overview of IAM including its ability to provide fine-grained access control and integrate with SAML 2.0 and LDAP. It notes issues with passwords and credentials like entropy and rainbow table attacks. The document outlines IAM roles and policies and recommends making credentials temporary to improve security.
CDKs
This document is a profile for Diego Pacheco, who is a cat's father, head of software architecture, agile coach, SOA/microservices expert, DevOps practitioner, speaker, and author. He has expertise in topics such as Terraform, CDKs, and CDKs code generation and maintains GitHub repositories on these subjects.
More Related Content
Viewers also liked
Learning To Learn
A talk about how we learn and think, how we teach, and how our approach to thinking has remained largely unchanged in the West for over 2000 years.
First presented at the Better Software Conference in Las Vegas, June 2009.
Exactpro Systems for KSTU Students in Kostroma
This document discusses Exactpro Systems, an innovative trading systems company. It provides information on the company's history, team compositions for different offices including Kostroma, statistics on employee retention and attrition, the breakdown of departments, and descriptions of products developed including ClearTH, Mini-Robots, Dolphin, Shsha, and Load Injector. It also discusses the company's conference in Kostroma on software development and analysis topics.
Why Your Agile Rollout Is Failing
The Agile rollout is failing due to issues with the kick-off, planning, finance, communications, and facilitating change. The kick-off did not properly engage developers in the reasons for adopting Agile. Planning involved turning traditional plans on their side rather than adopting Agile practices. Finance prioritized existing tools and infrastructure over effectiveness. Communications failed to inform all stakeholders of the Agile approach. Facilitating change was hindered by short timescales and resistance to new technical practices and responsibilities. Lasting adoption requires understanding change management, systems thinking, and frequent small improvements.
No best practices?
The document discusses best practices and argues that they are often used to limit risk and enforce control but can stifle creativity. It notes that most fear, which often drives the adoption of best practices, is irrational. While best practices can help novices and advanced beginners, experts often subvert practices. True best practices should be context-dependent patterns that describe pros and cons rather than absolute prescriptions of behavior. In summary, software development is a creative endeavor, and the best approach to best practices is to provide descriptive patterns rather than prescriptive rules that can frustrate skilled professionals.
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.
Bdd Introduction
1) Behaviour-driven development (BDD) is an agile methodology that focuses on delivering working, tested software through collaboration between developers, testers and stakeholders.
2) BDD implements an application by describing its behavior through features and scenarios written from the perspective of stakeholders. Stories, acceptance criteria, executable examples and other tools are used to define requirements and guide development.
3) BDD aims to produce software that provides tangible value to stakeholders by being delivered incrementally, being easy to deploy and manage, and by adapting quickly to feedback through frequent testing and deployment.
Cucumber_Training_ForQA
This document provides an overview of the Cucumber testing tool. It discusses Behavior Driven Development (BDD) and how Cucumber enables BDD. The document covers the key components of Cucumber including Gherkin language, feature files, step definitions, and tags. It also provides examples of how Cucumber can be used with Selenium for automated testing and discusses Cucumber reports.
Behavior Driven Development Pros and Cons
The Cons of Behavior Driven Development (BDD)
Ivan Bobrov, ClubQA Co-Founder, Kostroma
The Pros of Behavior Driven Development (BDD): Business User Scenarios
Natalia Zaitseva, Exchange Functional Test Automation Lead Innovative Trading Systems
EXTENT Conference.
October 29-30, 2011
Test Automation for Trading Systems
Renaissance Hotel Moscow
BDD with the Cucumber
Behaviour Driven Development with The Cucumber
Test Pyramid
BDD Concept
Why BDD
Traditional Loop
Collaboration
Cucumber is the Tool
Cucumber structure
Sample feature
Gherkin is the Language
Step Definitions
Reqular Expressions
How the Cucumber Works
Expressive Scenarios
Outside-in development
Keeping your cucumbers sweet
Environment
Conclusion
BDD testing with cucumber
How to do behavior driven development with cucumber, generate easy readable and understandable test reports for your business.
Behavior Driven Development and Automation Testing Using Cucumber
This document discusses behavior-driven development (BDD) and automation testing using Cucumber. It begins with an example of a Cucumber scenario for logging into a system. It then demonstrates an automation test case written in Java and discusses how Cucumber executes scenarios. The rest of the document outlines an agenda to discuss BDD, Cucumber automation, developing a Cucumber framework, and the pros and cons of BDD and Cucumber.
Cucumber-III
The document discusses Cucumber, a tool for behavior driven development. It introduces Cucumber and how it is used for writing acceptance tests. Key components of Cucumber include feature files that contain scenarios in Given, When, Then format and step definitions that implement the scenario steps in code. The document provides examples of feature files and step definitions.
Behavior Driven Development (BDD) and Agile Testing
The document discusses Behaviour Driven Development (BDD) and how it uses frameworks like Cucumber to define user stories and acceptance criteria in a structured format known as feature files. This allows for collaboration between stakeholders and helps ensure quality by building tests into the requirements process from the start. Feature files also provide traceability and make adapting to changes easier.
BDD in Action – principles, practices and real-world application
Behaviour-driven development (BDD) started as an improved variation on test-driven development, but has evolved to become a formidable tool that helps teams communicate more effectively about requirements, using conversation and concrete examples to discover what features really matter to the business. BDD helps teams focus not only on building features that work, but on ensuring that the features they deliver are the ones that the client actually needs.
In this talk, we will discuss what BDD is about, its benefits, and how it affects teams and processes. We will discuss two case studies where BDD practices have been successfully introduced, including the benefits gained and challenges met. We will see how much benefit was gained when BDD was integrated into the broader development infrastructure, including issue tracking systems, requirements management, and project reporting.
We will also see how BDD can be applied to all levels of the development process, from requirements down to low-level coding. We will also look at the principle BDD tools available that can help teams implement executable specifications, BDD-style test automation, and living documentation effectively. Some of the tools discussed will include JBehave, Cucumber, Specflow, Jasmine and Spock.
We will also look at two case studies where BDD practices have been successfully integrated into several projects in large government and financial organizations. Teams that adopted BDD effectively benefited from significantly lower defect rates, much earlier discovery of errors and inconsistencies in the requirements, and better overall communication and collaboration within the team. However, practicing BDD does involve a significant change in mind-set compared to more traditional approaches, a different collaboration model between team members, and a high degree of stakeholder by-in and engagement, all of which should not be underestimated. We will discuss how the teams managed these various challenges during their BDD adoption story.
Behavior Driven Development
Annotated slides from my "Behavior Driven Development" course. Released under Creative Commons share-alike, commercial and derivatives allowed: http://creativecommons.org/licenses/by-sa/3.0/
BDD in Action - building software that matters
Behaviour-driven development (BDD) started as an improved variation on test-driven development, but has evolved to become a formidable tool that helps teams communicate more effectively about requirements, using conversation and concrete examples to discover what features really matter to the business. BDD helps teams focus not only on building features that work, but on ensuring that the features they deliver are the ones the client actually needs.
Learn what BDD is, and what it is not
Understand that the core of BDD is around conversation and requirements discovery, not around tools.
Understand the difference and similarities between BDD at the requirements level, and BDD at the coding level.
Learn what BDD tools exist for different platforms, and when to use them
Viewers also liked (16)
Behavior Driven Development and Automation Testing Using Cucumber
Behavior Driven Development and Automation Testing Using Cucumber
Behavior Driven Development (BDD) and Agile Testing
Behavior Driven Development (BDD) and Agile Testing
BDD in Action – principles, practices and real-world application
BDD in Action – principles, practices and real-world application
More from Diego Pacheco
Naming Things Book : Simple Book Review!
The document discusses principles for naming identifiers in code such as variables, classes, and functions. It notes that naming is important because identifiers make up 70% of code and influence comprehension, recall, and bug fixing time. Good naming follows principles like understandability, using names that describe concepts, and consistency. It provides specific rules for naming classes, variables, functions for conciseness, consistency, and distinguishability. The goal is to use names that are understandable to both current and future engineers working on the code.
Continuous Discovery Habits Book Review.pdf
This document summarizes key points from the book "Continuous Discovery Habits" by Diego Pacheco. It advocates for continuous discovery through an outcome-oriented and customer-centric mindset. Discovery requires the collaboration of product managers, designers, and engineers to iteratively test assumptions and validate ideas with customers. The goal is to ensure teams are creating value for users and addressing their needs, pain points, and desires on an ongoing basis through experimental and visual approaches.
Thoughts about Shape Up
This document discusses the Shape Up methodology for agile software development projects. It introduces Shape Up as similar to Dual Track Agile, with an initial 6-week discovery process. Key aspects of how shaping works include setting boundaries, roughing out elements, addressing risks, writing a pitch, and creating simple breadboarding prototypes. Other topics covered are cutting scope, how the pitch works, using betting tables instead of backlogs, dealing with bugs, and making progress on the whole stack through scope mapping and discovery charts.
Holacracy
This document discusses Holacracy, an alternative organizational structure to traditional hierarchies. It notes that current management structures were designed for factories, while Holacracy is designed for humans. Holacracy eliminates hierarchies and instead focuses on clearly defined roles and circles within an organization. It aims to embrace autonomy through separating people from roles and having roles, not managers, make decisions. While challenging to implement due to issues of power, some companies have adopted aspects of Holacracy.
AWS IAM
This document discusses AWS Identity and Access Management (IAM). It provides an overview of IAM including its ability to provide fine-grained access control and integrate with SAML 2.0 and LDAP. It notes issues with passwords and credentials like entropy and rainbow table attacks. The document outlines IAM roles and policies and recommends making credentials temporary to improve security.
CDKs
This document is a profile for Diego Pacheco, who is a cat's father, head of software architecture, agile coach, SOA/microservices expert, DevOps practitioner, speaker, and author. He has expertise in topics such as Terraform, CDKs, and CDKs code generation and maintains GitHub repositories on these subjects.
Encryption Deep Dive
Encryption Deep Dive: Randomness, Entropy, RNG, PRNG, AES, AES Operational Modes, Data Rotations, Java Encryption APIs, Tradeoffs, challenges, Envelope Encryption, KMS, and much more on all things encryption.
Sec 101
This document profiles Diego Pacheco and provides an overview of key software security principles including defense in depth, the least privilege principle, encryption, TLS and mTLS, misconfiguration and error handling, input sanitization, cross-site scripting (XSS), insecure serialization/deserialization, known vulnerabilities, logging and audit trails, threat analysis, and engineering friction. The document emphasizes applying security best practices to protect customer experience, brand integrity, and compliance while avoiding friction for engineering teams.
Reflections on SCM
Reflections on SCM: DevOps, CI/CD, Branches, Architecture, PRs, and many more considerations and thoughts.
Management: Doing the non-obvious! III
This document discusses various management concepts and techniques, including:
- Biases that can negatively impact decision-making like planning fallacy and availability bias.
- How work is becoming indistinguishable from sabotage due to bureaucracy and predictability.
- The importance of having "skin in the game" and being willing to be wrong to drive change and learning.
- Dealing with scarcity by identifying high and low performance areas and reallocating resources accordingly.
Design is not Subjective
Design is Not Subjective! Software design and Lean UX, Ux, Design Thinking are not that different after all. UML was in the right direction the problem was where we applied. In this video, I will explain why Design is not subjective. Video https://www.youtube.com/watch?v=ijGR6Tbhr54
Architecture & Engineering : Doing the non-obvious!
Diego Pacheco is a software architect, agile coach, and speaker who focuses on non-traditional approaches. Some of his views include that requirements can change and duplication is okay, tests don't always improve design or find bugs, and complexity sometimes needs abstractions but other times they add unnecessary complexity. He also believes teams will always have technical debt so it's important to prioritize fixing quick wins over deep technical issues, and that architecture is about people and enabling teams.
Management doing the non-obvious II
This document discusses various management concepts and principles:
- You cannot regulate failure in complex systems and it is better to focus on recovering from failures rather than trying to predict and prevent them.
- Product teams are more effective than feature teams because they are focused on discovering customer needs rather than having predefined solutions.
- Sharing a vision rather than a detailed roadmap allows for more flexibility and ability to change tactics.
- Psychological safety and an environment where people feel included, safe to learn and contribute, and safe to challenge the status quo is important for teams.
- Discipline is needed to successfully execute digital transformations but often lacks longevity and focus shifts to short term goals.
Testing in production
The document discusses testing in production environments using "dark canaries". Dark canaries involve deploying code changes to a small percentage of real users without their knowledge to test for issues before broad deployment. The key benefits are that it allows testing with real users and traffic in the actual production environment and catching problems early before they affect everyone. Some challenges are potential privacy issues if users are not informed and ensuring changes don't negatively impact the small group of unaware users.
Nine lies about work
The document outlines 9 common lies about work and proposes alternative truths. The lies discussed include that people care most about the company they work for rather than their team, that the best plan wins rather than intelligence in real-time, and that feedback and performance reviews can reliably rate people. The author argues that people primarily care about their team, intelligence is needed to adapt to a dynamic world, and that reviews mostly reflect raters rather than ratees. The truths proposed emphasize caring for one's team, prioritizing real-time intelligence over static plans, and that people can best rate their own experiences.
Management: doing the nonobvious!
This document provides advice and perspectives on management and leadership from Diego Pacheco. Some of the key points discussed include:
- Ego can distort reality and inhibit innovation, so leaders should suppress ego with humility.
- Not all communication needs to happen between all people; structured teams are better models than rigid organization charts.
- Feedback is difficult to give and receive but is important for growth if approached without emotion or defensiveness.
- Scenario modeling and role playing exercises can help train leaders by anticipating problems before they occur.
AI and the Future
The document discusses several topics related to artificial intelligence and the future, including:
1) Whether AI-generated music has soul or not.
2) The possibility of AI judges making faster parallel decisions.
3) Elon Musk's view that we are all already cyborgs.
4) Musk's proposal that augmented humans could regenerate organs and tissues by 2100 through technologies like neuralink.
5) The potential to reengineer humans and expand lifespans to 120-150 years through these technologies.
Dealing with dependencies
This document discusses dealing with dependencies between teams when developing software. It acknowledges that fixed release schedules and monolithic codebases can create issues. Some potential solutions proposed include using contracts and mocks between teams, restructuring code using domain-driven design principles, and creating lean shared libraries to reduce duplication while allowing independence. The document advocates for moderate approaches between extremes rather than ignoring problems with dependencies.
Dealing with dependencies in tests
This document discusses different types of test doubles (fakes, stubs, mocks, spies, and dummies) that can be used to deal with dependencies in tests. It explains what each type is and provides examples of when each might be used. It also discusses how to design code for better test isolation by reducing coupling and avoiding tightly binding components together, though this can sometimes make the code harder to test. Cross-cutting concerns like authentication are discussed as things that may be difficult to fully isolate or mock at a component level.
Kanban 2020
This document discusses issues that can arise with Scrum implementations and introduces Kanban as an alternative. It notes problems with a focus on dates in Scrum and retaining the process rather than changing it. Kanban is presented as a lean approach that emphasizes continuous learning and improvement rather than utilization. The document outlines Kanban concepts like value stream mapping, cost of delay, Kanban boards, and metrics that can be used to test if a Kanban approach is being implemented.
More from Diego Pacheco (20)
Architecture & Engineering : Doing the non-obvious!
Architecture & Engineering : Doing the non-obvious!
Recently uploaded
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.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
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
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
UiPath Test Automation using UiPath Test Suite series, part 5
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Recently uploaded (20)
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
UiPath Test Automation using UiPath Test Suite series, part 5
UiPath Test Automation using UiPath Test Suite series, part 5
Cucumber
- 1. @diego_pacheco Software Architect | Agile Coach
- 2. BDD Creator: Dan North - 2003
- 4. BDD (Behavior Driven Development) TDD evolution to BDD
- 5. BDD Process
- 6. BDD improve communication (Customer to Developer | Developer to Developer ) NOT sure about it !
- 7. Cucumber ( Ruby BDD )
- 11. Thanks !!! @diego_pacheco Software Architect | Agile Coach