Expo qa from user stories to automated acceptance tests with bddEduardo Riol
The document discusses Behavior Driven Development (BDD) as a collaboration model between business users and developers to discover requirements through concrete examples. It describes how BDD involves writing scenarios in a simple language like Gherkin, translating them to automated acceptance tests, and using the tests to guide development and provide feedback. BDD aims to reduce assumptions and clarify what features truly provide value by establishing conversations based on usage examples. The document also notes some challenges with BDD, such as requiring stakeholder involvement throughout and experience to design maintainable tests.
Tdd vs bdd vs atdd — developers’ methodologies to navigate complex developmen...Katy Slemon
Know key differences between major development methodologies TDD vs BDD vs ATDD in this post that focus on the task of the developers and their creations
Behaviour-Driven Development (BDD) is a game changer for the whole team! More than just a testing technique, BDD is both a collaboration and a verification tool, and a vital step on the road to Continuous Delivery. In this session, you will learn what BDD is about, its benefits, and how it affects development teams and processes. But you will also see BDD techniques applied to a real project using tools like JBehave, Cucumber, Selenium 2, Thucydides and more!
- Learn how BDD helps teams focus on discovering and delivering the features that really matter! - Learn what it takes to write more relevant and more maintainable automated acceptance tests - Discover how a well-designed set of automated acceptance criteria can also be a powerful documentation and reporting tool. - See where BDD fits into a Continuous Delivery pipeline.
- And learn how product owners use BDD and Thucydides to drive, coordinate and document releases.
Learn how much more there is to BDD than just “Given..When..Then”!
This software development and consulting company has over 8 years of experience creating custom web and mobile applications for clients. They have a team of highly skilled professionals across various roles. The company follows agile development practices like Scrum and provides dedicated teams to ensure full attention to each project. They have experience in various industries and technologies.
ehaviour-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.
This is a variation on the talk I gave at Agile Australia, that I delivered at the Sydney Agile meetup on July 15 2014.
India’s Top Software Product Development CompanyPixel Crayons
PixelCrayons is a top software product development company that offers end-to-end SaaS development services. They have over 16 years of experience creating over 13,800 projects for 6,800+ customers globally. Their services include product strategy, design, development, testing and maintenance across web, mobile and embedded platforms using modern technologies. They provide dedicated teams or hourly engagements to suit different needs and ensure on-time delivery of high quality, scalable products.
Successfully Implementing BDD in an Agile WorldSmartBear
This document provides an overview of successfully implementing Behavior Driven Development (BDD) in an agile environment. It discusses shifting testing left by involving testers earlier in the development process. The document then covers the key aspects of a BDD process including discovery workshops to understand requirements, writing examples and scenarios in a Given/When/Then format, automating scenarios, and using continuous integration to ensure tests always pass. It emphasizes that adopting BDD requires changes to people, processes, and tools to facilitate collaboration between all teams.
Expo qa from user stories to automated acceptance tests with bddEduardo Riol
The document discusses Behavior Driven Development (BDD) as a collaboration model between business users and developers to discover requirements through concrete examples. It describes how BDD involves writing scenarios in a simple language like Gherkin, translating them to automated acceptance tests, and using the tests to guide development and provide feedback. BDD aims to reduce assumptions and clarify what features truly provide value by establishing conversations based on usage examples. The document also notes some challenges with BDD, such as requiring stakeholder involvement throughout and experience to design maintainable tests.
Tdd vs bdd vs atdd — developers’ methodologies to navigate complex developmen...Katy Slemon
Know key differences between major development methodologies TDD vs BDD vs ATDD in this post that focus on the task of the developers and their creations
Behaviour-Driven Development (BDD) is a game changer for the whole team! More than just a testing technique, BDD is both a collaboration and a verification tool, and a vital step on the road to Continuous Delivery. In this session, you will learn what BDD is about, its benefits, and how it affects development teams and processes. But you will also see BDD techniques applied to a real project using tools like JBehave, Cucumber, Selenium 2, Thucydides and more!
- Learn how BDD helps teams focus on discovering and delivering the features that really matter! - Learn what it takes to write more relevant and more maintainable automated acceptance tests - Discover how a well-designed set of automated acceptance criteria can also be a powerful documentation and reporting tool. - See where BDD fits into a Continuous Delivery pipeline.
- And learn how product owners use BDD and Thucydides to drive, coordinate and document releases.
Learn how much more there is to BDD than just “Given..When..Then”!
This software development and consulting company has over 8 years of experience creating custom web and mobile applications for clients. They have a team of highly skilled professionals across various roles. The company follows agile development practices like Scrum and provides dedicated teams to ensure full attention to each project. They have experience in various industries and technologies.
ehaviour-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.
This is a variation on the talk I gave at Agile Australia, that I delivered at the Sydney Agile meetup on July 15 2014.
India’s Top Software Product Development CompanyPixel Crayons
PixelCrayons is a top software product development company that offers end-to-end SaaS development services. They have over 16 years of experience creating over 13,800 projects for 6,800+ customers globally. Their services include product strategy, design, development, testing and maintenance across web, mobile and embedded platforms using modern technologies. They provide dedicated teams or hourly engagements to suit different needs and ensure on-time delivery of high quality, scalable products.
Successfully Implementing BDD in an Agile WorldSmartBear
This document provides an overview of successfully implementing Behavior Driven Development (BDD) in an agile environment. It discusses shifting testing left by involving testers earlier in the development process. The document then covers the key aspects of a BDD process including discovery workshops to understand requirements, writing examples and scenarios in a Given/When/Then format, automating scenarios, and using continuous integration to ensure tests always pass. It emphasizes that adopting BDD requires changes to people, processes, and tools to facilitate collaboration between all teams.
"Given..When..Then"...a common perception of Behaviour Driven Development focuses on writing and automating SpecFlow-style scenarios. In fact this is just a small part of BDD: the full scope of BDD ranges from requirements discovery and description, through to driving technical design and implementation, helping testers focus their testing efforts more effectively, and even providing reliable, useful and accurate technical documentation. In this talk, you will learn about how much more there is to BDD than just "Given..When..Then"!
A common perception of behavior-driven development (BDD) focuses on test automation with Cucumber-style “Given..When..Then” scenarios. But this is just the tip of the iceberg: in fact BDD ranges from requirements discovery and description through to driving technical design and implementation; helping testers focus their testing efforts more effectively; and even providing reliable, useful, and accurate technical documentation.
This session discusses what BDD is about, its benefits, and how it affects development teams and processes. You will see how JVM teams can effectively implement BDD with tools such as JBehave, Cucumber, Thucydides, and Spock. Come learn how much more there is to BDD than just “Given..When..Then.”
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
The document discusses the operational costs of technical debt, including direct costs like system outages and development slowdowns, and indirect costs like prioritizing new features over infrastructure updates. It provides examples of technical debt at LinkedIn like upgrading Kafka from version 0.7 to 0.8 and using an outdated version of memcached. The document advocates recognizing and evaluating all costs to make active decisions about balancing new development work with retiring technical debt.
Contents:
Behavior Driven Development (BDD)
Features of BDD
BDD Tools
BDD Framework
Examples of Cucumber/SpecFlow/BDD test
Gherkin – BDD Language
The Problem
Example of Gherkin
The Conclusion
SpecFlow Feature File
Keywords for the Feature File creation
This document discusses test-driven development (TDD) and behavior-driven development (BDD). It notes that TDD is a design strategy that helps write better-designed, more confident, and easily changeable code that accurately meets user requirements. It also incidentally builds up automated tests. The document then discusses various Java 8 features like lambda expressions, streams, and date/time APIs that are useful for BDD and improving test code quality and maintainability. It advocates for layering acceptance tests from business rules and flows to page interactions and details. It provides examples of using streams and parallel streams to more optimally query pages in tests.
Behaviour Driven Development is a powerful collaboration technique that can empower teams to deliver higher value features to the business faster and more effectively. But although Behaviour Driven Development is based on a number of simple principles, it can go dramatically wrong in a myriad of different ways.
In this talk we discuss twelve BDD anti-patterns we frequently encounter in real-world BDD projects, anti-patterns that can dramatically reduce the effectiveness of BDD as a practice, and that can even cause BDD adoption to fail entirely. Looking at everything from insufficient collaboration practices to poor use of test automation tooling, from teams that test too much to teams that forget the most important scenarios, we will look at the many different ways that BDD can go wrong, and how it should be done.
We will use real-world examples to illustrate each of these anti-patterns. You will learn how to spot these issues in your own projects, and more importantly how to avoid them in the first place.
Meeting Strict Documentation Requirements in AgileTechWell
The document discusses an presentation by Craeg Strong on meeting documentation requirements in agile projects. Craeg has 25 years of experience in IT and technical lead experience on large government projects. The presentation covers strategies for planning, tracking, and reducing documentation work in agile while still meeting requirements, including improving documentation capabilities, reducing unnecessary documents, and streamlining document templates and processes.
Behaviour Driven Development (BDD) - Closing the Loop on a Great Fiori UXJohn Patterson
BDD (Behavior Driven Development) involves defining requirements as structured scenarios to guide development and act as automated tests. It promotes collaboration between developers, testers, and customers. User stories and acceptance criteria written in a common language like Gherkin provide requirements, documentation, and tests. Automating tests based on these scenarios provides fast, reliable feedback to close the development loop.
This document discusses how to integrate Scrum and Behavior Driven Development (BDD). It recommends starting with refining the product backlog by splitting user stories, defining acceptance criteria through examples, and collaborating with stakeholders. Examples show how to write specifications using the Given-When-Then format. The document emphasizes starting each sprint by writing automated tests based on the specifications before writing code. This ensures the team builds the right product by focusing on delivering value through small, testable increments.
An introduction to Behavior-Driven Development (BDD)Suman Guha
BDD helps develop the correct software by codifying customer requirements into automated test scenarios. Traditional QA focuses on adherence to documented requirements but often misses the actual requirements. BDD establishes a feedback loop through automated scenarios to ensure requirements are met. BDD scenarios describe real user behaviors to test software in a continuous integration process. This catches defects early and reduces costs and time compared to traditional waterfall development.
Slides from the London Agile Testing Meetup of November 25 2014:
John Ferguson Smart is a specialist in BDD, automated testing and software life cycle development optimization. John is a well-known speaker at many international conferences and events and an accomplished author (John's new book BDD in Action was published last month).
John presents a talk discussing how to write solid, reliable and maintainable automated web tests using the best-of-breed open source technologies like Selenium WebDriver, Serenity, JBehave and Cucumber.
Behaviour Driven Development is an increasingly popular Agile practice that turns testing on its head, and involves a major shift in the role testers play in a project. Although popularly associated with automated acceptance testing and tools like Cucumber, BDD actually has much broader applications. In this talk, we will look at how Behaviour Driven Development radically changes the traditional tester role in Agile projects, and empowers them to tangibly contribute much more to the successful outcomes of the project. We will see how collaboratively discussing and defining acceptance criteria help reduce assumptions and errors in the early phases of the project, and help ensure that the features being built are well understood, testable, and valuable to the business. We will look at ways to write more effective, easier to maintain automated acceptance criteria, that free testers to do more productive testing tasks such as exploratory testing. And we will see how automated and manual acceptance test reporting can be combined to provide valuable progress, product documentation and release preparation reporting.
This CodeIT company presentation gives a short description of the way CodeIT outsourcing company provides software development services and cooperate with clients from 32 countries around the world.
ProtoTech Solutions have expertise is 3D software development. We have experience in Graphics technologies (HOOPS,OpenGL,RedSDK), Geometry kernel (ACIS, Parasolid) and Interoperability solutions (HOOPS Exchange, InterOp, RealDWG, Teigha). Our development expertise includes for, Onshape, Fusion 360, cloud technologies (REST, PHP etc.) and User Interface.
The document discusses using Behavior Driven Development (BDD) and Test Driven Development (TDD) for software development. It provides background on several speakers for an upcoming event on BDD including their experience and qualifications. Finally, it outlines the agenda for the event which will cover XP, BDD, and a panel discussion on practices for the approaches.
Building In Quality: The Beauty Of Behavior Driven Development (BDD)Synerzip
Behavior Driven Development (BDD) began as a means of helping developers practice Test Driven Development (TDD).
In this it was successful, but it quickly proved its value in many other ways. In this presentation, Larry Apke quotes heavily from the work of Uncle Bob Martin to make the case for TDD and then explains how developers can use BDD to take advantage of this excellent software development practice.
Larry also talks about his “Ten Reasons BDD Changes Everything” along with some easy ways to begin implementation of BDD in your software development organization immediately and what the corresponding future steps would be to take full advantage of this technique.
This resume is for Shivdeep Kumar Gupta, who has over 5 years of experience developing applications on the Salesforce platform. He has worked on numerous projects for clients like Snapdeal and Thomson Reuters, taking on roles like senior developer and L3 support. Some of the key projects listed include implementing a case management system for Snapdeal sellers, integrating Snapdeal's system with external APIs, and customizing Salesforce for Thomson Reuters' internal use.
BDD is a software development process that improves communication between business and development teams. It uses examples written in a ubiquitous language to define desired product behaviors. The examples serve as requirements for automated tests and drive development. Key aspects of BDD include impact mapping to prioritize features, planning in examples with the three amigos (business, development, testing), and developing using examples as automated tests. This ensures the system meets business needs while delivering working software.
Jhon Arzu-Gil
Application Development Specialist
Houston, TX 77026
Jarzugil20@gmail.com
+1 248 938 5567
Application Developer Programming Specialist
I spent my first 5 years programming learning the Vanillas they never change and with those you can build any framework. My foundation started with HTML, CSS, JavaScript, SQL, and PHP because almost 80% of the internet uses it. Then I chose "Write Once Run Everywhere “Java '' as my main language knowing 58.99 percent of global website traffic is mobile and Over 60% of the world’s population has a cell phone. Of those mobile phones, almost 80% of those are smartphones. I have certification in everything from Big Data, A.I, Machine Learning, Blockchain, Data Science and Security. Working in the data analytics department at a Big Tech Company has
taught me that everything from utilizing open-source software and applications like Python and Juniper Notebook's to proprietary applications like SAP Analytics Cloud concepts like Master Data, Transaction Data etc are universal with not only project experience but hands on experience as well. If you check out the google play store and my android developer account you can see the 3 apps I developed and uploaded where anyone on the planet with an Android phone can download and run in minutes.. If you visit my personal website you can view the source code and libraries https://www.arzugil.com you browse through my portfolio. Also I’m experienced in marketing like Amazon PPC Advertising, Facebook Advertising, Google Advertising, Snapchat Advertising, TikTok Advertising, and Twitter Advertising.
Skills
• Full-stack development (5 years) • Azure (3 years)
• Python (5 years)
• Agile (3 years)
• AWS (3 years)
• SAP Analytics Cloud (3 years)
• Mobile applications (5 years)
• Android development (5 years)
• Java (5 years)
• PHP (5 years)
• MySQL (5 years)
• SAP HANA (3 years)
• Software Development (5 years) • Machine learning (4 years)
• JavaScript (5 years)
• iOS development (1 year)
• Jira (3 years)
• SQL (5 years)
• Git (5 years)
• C/C++ (5 years)
• Scrum (3 years)
• User Interface (UI) (5 years)
• Microsoft SQL Server (5 years)
• Application Development (5 years) • Unit Testing (3 years)
• Bootstrap (5 years)
• XML (5 years)
• Business Requirements (5 years) • GitHub (5 years)
• Test Cases (3 years)
• HTML5 (5 years)
• Cloud Computing (5 years)
• APIs (4 years)
• Computer Networking (3 years) • Linux (5 years)
• Data Warehouse (5 years)
• Scripting (5 years)
• REST (3 years)
• Docker (3 years)
• Web Services (5 years)
• Node.js (3 years)
• CI/CD (5 years)
Languages
• English - Expert
• Spanish - Intermediate
Links
https://cloudtechnologycomputing.com
https://arzugil.com
https://github.com/Jgil20 https://play.google.com/store/apps/dev?id=8040499476760752928&hl=en_US&gl=US https://www.credly.com/users/jhon-arzu-gil.8cf7cffc/badges
https://www.linkedin.com/in/jhongil
Specification-by-Example: A Cucumber ImplementationTechWell
We've all been there. You work incredibly hard to develop a feature and design tests based on written requirements. You build a detailed test plan that aligns the tests with the software and the documented business needs. When you put the tests to the software, it all falls apart because the requirements were updated without informing everyone. But help is at hand. Enter business-driven development and Cucumber, a tool for running automated acceptance tests. Join Mary Thorn as she explores the nuances of Cucumber and shows you how to implement specification-by-example, behavior-driven development, and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber bridges the communication gap between business stakeholders and implementation teams. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don't get what they ask for, be here!
"Given..When..Then"...a common perception of Behaviour Driven Development focuses on writing and automating SpecFlow-style scenarios. In fact this is just a small part of BDD: the full scope of BDD ranges from requirements discovery and description, through to driving technical design and implementation, helping testers focus their testing efforts more effectively, and even providing reliable, useful and accurate technical documentation. In this talk, you will learn about how much more there is to BDD than just "Given..When..Then"!
A common perception of behavior-driven development (BDD) focuses on test automation with Cucumber-style “Given..When..Then” scenarios. But this is just the tip of the iceberg: in fact BDD ranges from requirements discovery and description through to driving technical design and implementation; helping testers focus their testing efforts more effectively; and even providing reliable, useful, and accurate technical documentation.
This session discusses what BDD is about, its benefits, and how it affects development teams and processes. You will see how JVM teams can effectively implement BDD with tools such as JBehave, Cucumber, Thucydides, and Spock. Come learn how much more there is to BDD than just “Given..When..Then.”
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
The document discusses the operational costs of technical debt, including direct costs like system outages and development slowdowns, and indirect costs like prioritizing new features over infrastructure updates. It provides examples of technical debt at LinkedIn like upgrading Kafka from version 0.7 to 0.8 and using an outdated version of memcached. The document advocates recognizing and evaluating all costs to make active decisions about balancing new development work with retiring technical debt.
Contents:
Behavior Driven Development (BDD)
Features of BDD
BDD Tools
BDD Framework
Examples of Cucumber/SpecFlow/BDD test
Gherkin – BDD Language
The Problem
Example of Gherkin
The Conclusion
SpecFlow Feature File
Keywords for the Feature File creation
This document discusses test-driven development (TDD) and behavior-driven development (BDD). It notes that TDD is a design strategy that helps write better-designed, more confident, and easily changeable code that accurately meets user requirements. It also incidentally builds up automated tests. The document then discusses various Java 8 features like lambda expressions, streams, and date/time APIs that are useful for BDD and improving test code quality and maintainability. It advocates for layering acceptance tests from business rules and flows to page interactions and details. It provides examples of using streams and parallel streams to more optimally query pages in tests.
Behaviour Driven Development is a powerful collaboration technique that can empower teams to deliver higher value features to the business faster and more effectively. But although Behaviour Driven Development is based on a number of simple principles, it can go dramatically wrong in a myriad of different ways.
In this talk we discuss twelve BDD anti-patterns we frequently encounter in real-world BDD projects, anti-patterns that can dramatically reduce the effectiveness of BDD as a practice, and that can even cause BDD adoption to fail entirely. Looking at everything from insufficient collaboration practices to poor use of test automation tooling, from teams that test too much to teams that forget the most important scenarios, we will look at the many different ways that BDD can go wrong, and how it should be done.
We will use real-world examples to illustrate each of these anti-patterns. You will learn how to spot these issues in your own projects, and more importantly how to avoid them in the first place.
Meeting Strict Documentation Requirements in AgileTechWell
The document discusses an presentation by Craeg Strong on meeting documentation requirements in agile projects. Craeg has 25 years of experience in IT and technical lead experience on large government projects. The presentation covers strategies for planning, tracking, and reducing documentation work in agile while still meeting requirements, including improving documentation capabilities, reducing unnecessary documents, and streamlining document templates and processes.
Behaviour Driven Development (BDD) - Closing the Loop on a Great Fiori UXJohn Patterson
BDD (Behavior Driven Development) involves defining requirements as structured scenarios to guide development and act as automated tests. It promotes collaboration between developers, testers, and customers. User stories and acceptance criteria written in a common language like Gherkin provide requirements, documentation, and tests. Automating tests based on these scenarios provides fast, reliable feedback to close the development loop.
This document discusses how to integrate Scrum and Behavior Driven Development (BDD). It recommends starting with refining the product backlog by splitting user stories, defining acceptance criteria through examples, and collaborating with stakeholders. Examples show how to write specifications using the Given-When-Then format. The document emphasizes starting each sprint by writing automated tests based on the specifications before writing code. This ensures the team builds the right product by focusing on delivering value through small, testable increments.
An introduction to Behavior-Driven Development (BDD)Suman Guha
BDD helps develop the correct software by codifying customer requirements into automated test scenarios. Traditional QA focuses on adherence to documented requirements but often misses the actual requirements. BDD establishes a feedback loop through automated scenarios to ensure requirements are met. BDD scenarios describe real user behaviors to test software in a continuous integration process. This catches defects early and reduces costs and time compared to traditional waterfall development.
Slides from the London Agile Testing Meetup of November 25 2014:
John Ferguson Smart is a specialist in BDD, automated testing and software life cycle development optimization. John is a well-known speaker at many international conferences and events and an accomplished author (John's new book BDD in Action was published last month).
John presents a talk discussing how to write solid, reliable and maintainable automated web tests using the best-of-breed open source technologies like Selenium WebDriver, Serenity, JBehave and Cucumber.
Behaviour Driven Development is an increasingly popular Agile practice that turns testing on its head, and involves a major shift in the role testers play in a project. Although popularly associated with automated acceptance testing and tools like Cucumber, BDD actually has much broader applications. In this talk, we will look at how Behaviour Driven Development radically changes the traditional tester role in Agile projects, and empowers them to tangibly contribute much more to the successful outcomes of the project. We will see how collaboratively discussing and defining acceptance criteria help reduce assumptions and errors in the early phases of the project, and help ensure that the features being built are well understood, testable, and valuable to the business. We will look at ways to write more effective, easier to maintain automated acceptance criteria, that free testers to do more productive testing tasks such as exploratory testing. And we will see how automated and manual acceptance test reporting can be combined to provide valuable progress, product documentation and release preparation reporting.
This CodeIT company presentation gives a short description of the way CodeIT outsourcing company provides software development services and cooperate with clients from 32 countries around the world.
ProtoTech Solutions have expertise is 3D software development. We have experience in Graphics technologies (HOOPS,OpenGL,RedSDK), Geometry kernel (ACIS, Parasolid) and Interoperability solutions (HOOPS Exchange, InterOp, RealDWG, Teigha). Our development expertise includes for, Onshape, Fusion 360, cloud technologies (REST, PHP etc.) and User Interface.
The document discusses using Behavior Driven Development (BDD) and Test Driven Development (TDD) for software development. It provides background on several speakers for an upcoming event on BDD including their experience and qualifications. Finally, it outlines the agenda for the event which will cover XP, BDD, and a panel discussion on practices for the approaches.
Building In Quality: The Beauty Of Behavior Driven Development (BDD)Synerzip
Behavior Driven Development (BDD) began as a means of helping developers practice Test Driven Development (TDD).
In this it was successful, but it quickly proved its value in many other ways. In this presentation, Larry Apke quotes heavily from the work of Uncle Bob Martin to make the case for TDD and then explains how developers can use BDD to take advantage of this excellent software development practice.
Larry also talks about his “Ten Reasons BDD Changes Everything” along with some easy ways to begin implementation of BDD in your software development organization immediately and what the corresponding future steps would be to take full advantage of this technique.
This resume is for Shivdeep Kumar Gupta, who has over 5 years of experience developing applications on the Salesforce platform. He has worked on numerous projects for clients like Snapdeal and Thomson Reuters, taking on roles like senior developer and L3 support. Some of the key projects listed include implementing a case management system for Snapdeal sellers, integrating Snapdeal's system with external APIs, and customizing Salesforce for Thomson Reuters' internal use.
BDD is a software development process that improves communication between business and development teams. It uses examples written in a ubiquitous language to define desired product behaviors. The examples serve as requirements for automated tests and drive development. Key aspects of BDD include impact mapping to prioritize features, planning in examples with the three amigos (business, development, testing), and developing using examples as automated tests. This ensures the system meets business needs while delivering working software.
Jhon Arzu-Gil
Application Development Specialist
Houston, TX 77026
Jarzugil20@gmail.com
+1 248 938 5567
Application Developer Programming Specialist
I spent my first 5 years programming learning the Vanillas they never change and with those you can build any framework. My foundation started with HTML, CSS, JavaScript, SQL, and PHP because almost 80% of the internet uses it. Then I chose "Write Once Run Everywhere “Java '' as my main language knowing 58.99 percent of global website traffic is mobile and Over 60% of the world’s population has a cell phone. Of those mobile phones, almost 80% of those are smartphones. I have certification in everything from Big Data, A.I, Machine Learning, Blockchain, Data Science and Security. Working in the data analytics department at a Big Tech Company has
taught me that everything from utilizing open-source software and applications like Python and Juniper Notebook's to proprietary applications like SAP Analytics Cloud concepts like Master Data, Transaction Data etc are universal with not only project experience but hands on experience as well. If you check out the google play store and my android developer account you can see the 3 apps I developed and uploaded where anyone on the planet with an Android phone can download and run in minutes.. If you visit my personal website you can view the source code and libraries https://www.arzugil.com you browse through my portfolio. Also I’m experienced in marketing like Amazon PPC Advertising, Facebook Advertising, Google Advertising, Snapchat Advertising, TikTok Advertising, and Twitter Advertising.
Skills
• Full-stack development (5 years) • Azure (3 years)
• Python (5 years)
• Agile (3 years)
• AWS (3 years)
• SAP Analytics Cloud (3 years)
• Mobile applications (5 years)
• Android development (5 years)
• Java (5 years)
• PHP (5 years)
• MySQL (5 years)
• SAP HANA (3 years)
• Software Development (5 years) • Machine learning (4 years)
• JavaScript (5 years)
• iOS development (1 year)
• Jira (3 years)
• SQL (5 years)
• Git (5 years)
• C/C++ (5 years)
• Scrum (3 years)
• User Interface (UI) (5 years)
• Microsoft SQL Server (5 years)
• Application Development (5 years) • Unit Testing (3 years)
• Bootstrap (5 years)
• XML (5 years)
• Business Requirements (5 years) • GitHub (5 years)
• Test Cases (3 years)
• HTML5 (5 years)
• Cloud Computing (5 years)
• APIs (4 years)
• Computer Networking (3 years) • Linux (5 years)
• Data Warehouse (5 years)
• Scripting (5 years)
• REST (3 years)
• Docker (3 years)
• Web Services (5 years)
• Node.js (3 years)
• CI/CD (5 years)
Languages
• English - Expert
• Spanish - Intermediate
Links
https://cloudtechnologycomputing.com
https://arzugil.com
https://github.com/Jgil20 https://play.google.com/store/apps/dev?id=8040499476760752928&hl=en_US&gl=US https://www.credly.com/users/jhon-arzu-gil.8cf7cffc/badges
https://www.linkedin.com/in/jhongil
Specification-by-Example: A Cucumber ImplementationTechWell
We've all been there. You work incredibly hard to develop a feature and design tests based on written requirements. You build a detailed test plan that aligns the tests with the software and the documented business needs. When you put the tests to the software, it all falls apart because the requirements were updated without informing everyone. But help is at hand. Enter business-driven development and Cucumber, a tool for running automated acceptance tests. Join Mary Thorn as she explores the nuances of Cucumber and shows you how to implement specification-by-example, behavior-driven development, and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber bridges the communication gap between business stakeholders and implementation teams. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don't get what they ask for, be here!
We explore new techniques for selecting and tracking value-driven KPIs. The ResultsPositive team has years of experience building custom dashboards that emphasize and leverage key business metrics. These “business value dashboard” solutions can solve pressing visibility and workflow challenges, illuminating new opportunities for improvement. Enable informed decision making with unfettered insight and visualization into your ongoing business processes. By using the data you’ve already collected, you can create a more productive pipeline. In this webinar we will be presenting:
Overview of how business value dashboards consolidate and surface key metrics.
Customer Examples of successfully implemented dashboards:
Large Utility Corporation – Network and Distribution Dashboard
One of America’s largest food companies and leading distributors – Realtime distribution center status
ResultsPositive’s BVD-specific offerings and best practices.
This document discusses test-driven development (TDD) and behavior-driven development (BDD). It defines TDD as a process of writing automated tests before code to define desired functionality, then writing minimum code to pass tests and refactoring. BDD combines TDD techniques with domain-driven design and focuses on user stories over functions to promote communication. The document provides an example of using BDD to generate scenarios for a life insurance risk example, and shows how TestBox can be used to write automated tests based on those scenarios.
This document discusses test-driven development (TDD) and behavior-driven development (BDD). It defines TDD as a process of writing automated tests before code to define desired functionality, then writing minimum code to pass tests and refactoring. BDD combines TDD techniques with domain-driven design and aims to facilitate collaboration between developers and business stakeholders. The document provides an example of using BDD to specify scenarios for generating life insurance risk quotes. It also outlines how to structure tests in TestBox and run test bundles.
This document discusses test-driven development (TDD) and behavior-driven development (BDD). It defines TDD as a process of writing automated tests before code to define desired functionality, then writing minimum code to pass tests and refactoring. BDD combines TDD techniques with domain-driven design and focuses on user stories over functions to promote communication. The document provides an example of using BDD to generate scenarios for a life insurance risk example, and shows how TestBox can be used to write automated tests based on those scenarios.
The document is a presentation deck about technical debt that covers:
- What technical debt is and how it occurs through bad design decisions or quick development approaches that sacrifice quality
- How to identify technical debt through indicators like comments mentioning certain developers' code or difficulties with setup, deployment, or testing
- Sources of technical debt like time pressure, maintenance neglect, or using outdated libraries
- Why technical debt should be addressed to avoid issues like an uncontrollable codebase and development risks
- How to manage technical debt through practices like refactoring, continuous integration, and prioritizing technical debt in estimations
Xebia is a global IT consultancy firm specializing in agile software development and offshore outsourcing. They have over 200 employees across locations in the Netherlands, France, India, and Singapore. Xebia takes a collaborative and lean approach to software projects, with a focus on quality, agile methodologies like Scrum and XP, and domain expertise in areas like enterprise Java and financial systems. They have experience delivering projects for major banks and financial institutions.
The document provides an overview of ArxMind Consulting Services portfolio. It discusses ArxMind's clients which include Daymon Worldwide, Corona Projects, Skystem, and Penna. It also summarizes some of ArxMind's projects for these clients such as websites, business intelligence tools, supply chain management systems, and mobile applications for field force management and food safety audits. Client testimonials praise ArxMind's work, quality, and responsiveness.
Narayanan Doraiswamy is seeking technology-related job assignments with a growth-oriented organization. He has over 10 years of experience managing mission-critical financial services applications as a software engineer, programmer analyst, and manager. He has proficiency in areas like software development, project management, customer support, and application resiliency.
The document discusses Behavior Driven Development (BDD) and its implementation. It covers BDD topics like the Agile Manifesto, acceptance criteria, Cucumber framework, automation tools like Selenium. It also provides examples of feature files and step definitions in Cucumber. The document advocates that BDD helps align stakeholders, provides executable specifications, and finds defects early through automated tests.
Projekt202 is a software consulting firm that helps large organizations improve user experiences and reduce wasteful spending. They discover users' real needs through design research and data analysis to deliver meaningful solutions. Their process involves understanding business objectives, exploring the product space, investigating users, uncovering the current user experience, identifying threats, measuring data, and gaining a deep understanding of users. They then focus innovation efforts on defining success, identifying key features, and refining concepts. Finally, they build solutions through iterative testing and validation to refine their approach and launch effective digital marketing campaigns.
Similar to Webinar-From user stories to automated acceptance tests with BDD-Eduardo Riol (20)
Este documento describe cómo implantar de forma flexible y personalizada una solución de gestión de servicios de TI (ITSM) utilizando las herramientas de Atlassian. Explica cómo estas herramientas pueden ayudar a orientar la gestión de servicios TI hacia la plena satisfacción de los usuarios mediante la mejora de procesos, la medición de métricas y la automatización. También presenta la propuesta de valor de atSistemas para implantar soluciones ITSM con Atlassian de forma ágil e iterativa.
El ritmo de los cambios en el panorama empresarial se está acelerando cada vez más; y en parte es debido a que en los últimos años estamos siendo bombardeados por nuevas tecnologías digitales tales como: social, mobile, analytics, cloud, IoT, artificial intelligence, blockchain, biometrics, robotics, entre otras.
Lo interesantísimo acerca de estas tecnologías es como son capaces de cambiar la propuesta de valor que las organizaciones pueden ofrecer a sus clientes.
Para las organizaciones ya establecidas el reto es mayor, si cabe, debido a que deberán emprender un largo y complejo viaje para comprender y apalancarse en los beneficios de las tecnologías digitales. Este proceso es lo que llamamos metamorfosis digital y será el eje central de este webinar.
Agenda:
- Las tecnologías digitales y su impacto en la creación de nuevas propuestas de valor.
- La necesidad de re-diseño para ser capaz de crear nuevas propuestas de valor.
- Implicaciones de la metamorfosis digital en terminos de transformación.
- Los 5 bloques de construcción para la transformación.
NET5 es la nueva plataforma de desarrollo unificada, para programar cualquier tipo de aplicaciones modernas con Visual Studio. La construcción de nuevas aplicaciones .NET5, se pueden desarrollar y publicar en diferentes sistemas operativos, plataformas de nube, plataformas móviles, IoT y otros dispositivos con diferentes lenguajes y herramientas.
Webinar Speed Up Academy: Acelera la incorporación de talento.atSistemas
Presentamos el framework diseñado por atSistemas para la gestión del talento en las organizaciones y gestionado por DEXS. Es un concepto innovador dentro del contexto de la gestión del talento, cuyo objetivo es la gestión y distribución del conocimiento en los equipos distribuido en 4 etapas:
1ª. Dar cobertura al proceso de onboarding mediante un plan formativo estructurado que incluye toda la información necesaria para las nuevas incorporaciones.
2ª. Proceso de mentorización para mantener a los miembros de los equipos motivados y alineados con la estrategia global del proyecto.
3ª. Planes de Formación para adecuar continuamente las capacidades a las necesidades y evolución de las capacidades y habilidades.
4ª. Gestión del Conocimiento entre equipos y departamentos.
Webinar: Descubre los diferentes servicios Cloud Native en AzureatSistemas
En el contexto actual, las plataformas y tecnologías Cloud están impulsando una serie de cambios en la forma en que se analizan, desarrollan, implementan, despliegan y monitorizan las aplicaciones.
Las tecnologías y herramientas Cloud Native se utilizan para desarrollar y desplegar aplicaciones construidas con tecnologías de Containers, Microservicios o Serverless. En esta sesión os animamos a que conozcáis, los diferentes escenarios y enfoques para el diseño de Arquitecturas y Aplicaciones Cloud Native utilizando los servicios de Azure.
¿Qué descubrirás en este webinar?
Qué son las plataformas Cloud
Qué es Cloud Native y CNCF - Cloud Native Computing Foundation-.
Cómo funciona Cloud Native en Azure
Demo en Azure: planteando diferentes escenarios
El documento habla sobre el futuro del trabajo en equipo. Discuten tres áreas claves: 1) la reducción de jerarquías, 2) fomentar la innovación, 3) ser disruptivo. También cubre temas como el trabajo en equipo, liderazgo de proyectos, tendencias como la competencia y cambios rápidos, y la importancia de contratar a los mejores equipos distribuidos.
La tecnología al servicio de la agilidad empresarialatSistemas
Este documento describe cómo las herramientas de Atlassian pueden ayudar a las empresas a adoptar un enfoque ágil. Explica que Jira Software y Confluence son útiles para la gestión ágil de proyectos a nivel de equipo, mientras que herramientas adicionales como Tempo, BigPicture y Portfolio permiten escalar la gestión ágil a nivel de programa y organización completa mediante la planificación de múltiples equipos, la gestión económica y las roadmaps globales. El documento también menciona la nueva solución J
Este documento habla sobre la transformación ágil en TI. Explica que una transformación exitosa requiere más que sólo cambios tecnológicos, también se necesita cambiar la cultura organizacional. Propone un modelo de tres pasos para agilizar el negocio y la tecnología e indica que la transformación lleva tiempo, entre 3 a 5 años. Finalmente, ofrece consejos sobre cómo implementar una nueva cultura a través de planes de comunicación, capacitación, sensibilización y recompensas.
Este documento describe cómo la transformación cultural es clave para un proceso integral de transformación en las empresas. Explica que la transformación digital implica cambios en la estrategia, procesos, tecnología y, sobre todo, en la cultura y las personas de una compañía. Señala que la cultura es el ADN de una empresa y que los líderes deben enfocarse primero en promover cambios culturales a través de los valores y comportamientos de las personas. También destaca la importancia de definir una cultura deseada y trabajar en iniciativas para reducir las bre
Technical considerations for Blockchain networks with AWSatSistemas
The document discusses blockchain services available on AWS, including Amazon Quantum Ledger Database (QLDB) and Amazon Managed Blockchain. QLDB is a fully managed ledger database that allows users to query and analyze the full transaction history. Managed Blockchain makes it easy to create and manage scalable blockchain networks on AWS using frameworks like Hyperledger and Ethereum. The document also provides examples of using Blockchain-as-a-Service (BaaS) solutions and custom deploying an Ethereum network on AWS.
Blockchain Spain II Edición - Ángel Miguel MartínezatSistemas
El documento describe cómo incentivar la productividad de los empleados a través de la gamificación con criptomonedas. Se propone crear un token llamado ATCOIN que los empleados puedan ganar al completar tareas como cerrar issues en Jira o entregar informes a tiempo. Los empleados podrán canjear los tokens por artículos de la empresa. El sistema usaría una blockchain de prueba de autoridad como infraestructura y Metamask para las billeteras y transferencias de tokens.
Nestor Gandara nos hará un recorrido técnico por los componentes y las herramientas que ofrece Amazon Web Services (AWS) para construir y desarrollar soluciones Blockchain.
La tarea de conceptualizar, diseñar, desplegar y poner en producción una red Blockchain permisionada impone una serie de retos de carácter organizativo y tecnológico.
Estos retos adquieren una mayor dimensión cuando se involucran grandes actores del ecosistema español e internacional pertenecientes a múltiples sectores.
En esta presentación, Juan Luis Gozalo explicará los distintos componentes, las complejidades, los logros alcanzados y el roadmap de una red Blockchain permisionada.
SAP provides blockchain services and solutions to help customers address challenges around supply chain transparency, cross-company workflow orchestration, and verification of off-chain business rules, leveraging SAP Cloud Platform Blockchain and partnerships in the blockchain ecosystem. The document outlines several SAP exploration projects using blockchain technology to optimize processes, provide transparency, and establish trust across business networks.
En esta presentación, Santiago Chamat nos expondrá las repercusiones y los retos legales que debemos tener en cuenta a la hora de implementar contratos inteligentes para automatizar determinados procesos y atender propósitos específicos. Así mismo, nos mostrará los esfuerzos que, en materia de marco legal, se están desarrollando en el panorama español e internacional.
Muchos de los casos de uso interesantes de Blockchain se encuentran con problemas en el momento de desarrollarlos por la complejidad de la propia tecnología. Oracle Blockchain Plataform permite centrarse en el caso de negocio un beneficio rápido para las organizaciones. Antonio Gómez nos presentará la plataforma de Oracle y cómo está ayudando a compañías a obtener beneficios en producción.
1. The document discusses how blockchain can be used in the future of energy, particularly for distributed and decentralized energy trading.
2. It presents various use cases for how utilities are currently experimenting with and implementing blockchain technologies, with decentralized energy trading being the largest use case.
3. Blockchain is assessed to be a good foundation technology for distributed energy business models due to its ability to facilitate peer-to-peer energy trading in a decentralized manner.
The document discusses the Proof of Authority (PoA) blockchain project called LEDGER. LEDGER's mission is to empower citizens to control their own data by promoting alternative decentralized models where data is owned by citizens and wealth created from data is distributed equally. LEDGER is funding 32 projects building minimum viable products (MVPs) focused on privacy, open source software, and data sovereignty. The projects receive up to €200k in equity-free funding and support over 12 months to develop their MVPs across six sectors. LEDGER's principles require projects to build solutions to real problems using decentralization, have potential for large-scale impact, and balance radical innovation with business validation and sustainability of MVPs.
Blockchain Spain II Edición - Autoridad Portuaria de Cartagena, Ilboc, RepsolatSistemas
Este documento describe la plataforma Noms4all, una plataforma blockchain para gestionar las nominaciones de buques. Se detalla cómo Repsol, la Autoridad Portuaria de Cartagena y ILBOC están usando Noms4all para digitalizar y automatizar los procesos de nominación, mejorando la eficiencia, seguridad y trazabilidad. La plataforma permite a múltiples partes interesadas compartir y acceder a información de forma segura y transparente.
Blockchain Spain II Edición - Juan Manuel MartínezatSistemas
El documento describe cómo la tecnología blockchain puede aplicarse al sector del transporte y la logística para mejorar la trazabilidad, transparencia y eficiencia. Se explica brevemente qué es blockchain y sus beneficios. Luego, se caracteriza el sector del transporte y se proponen varios casos de uso potenciales de blockchain como un sistema de gestión de seguridad ferroviaria, una aplicación para la formación ferroviaria y una plataforma para la integración de la cadena de suministro. Finalmente, se concluyen las razones para la implementación de blockchain en
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
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.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
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.
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
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.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
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.
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.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
2. I’m Eduardo Riol, QA & Testing Community Technical Leader in
atSistemas, where we are enthusiasts of Software Quality Assurance,
Tests Automation and Testing best practices.
I started as developer in Java and .NET environments more than a decade
ago, but I’ve been involved the last eight years in Software Quality, both
products and development processes oriented.
Currently my interests are focused in the integration of QA activities in
Agile and DevOps environments, technical debt control and BDD.
Lately I research about other topics like Security and Blockchain.
twitter.com/eduriol
github.com/eduriol
linkedin.com/in/eduriol
Who am I?
3. 3
We are a dependable partner, with a long trajectory and a solid
future in the industry
of revenue in 2017
54,5 M€ estimated for
2018
Present in every
industry
Spanish capital
Presence in Madrid,
Barcelona, Cádiz,
Zaragoza, A Coruña,
Mallorca and Huelva
International vocation
And currently IT referent in Innovation
Expert Centers and cutting-edge
Technological Communities,
leaders in Digital Transformation
IT professionals
of proved Technical Solvency
growth in international
interannual billing at 2017
closure
atSistemas
45,6 M€
100%
1994Founded in
R&D
1000
16,5%
4. Houston, we have a problem!
“This is not what we asked for” Does that ring a bell?
5. Houston, we have a problem!
Chine
se
whisp
ers The Gossips, Norman Rockwell, 1948
“This is not what we asked for” Does that ring a bell?
6. We focused on developing software CORRECTLY…
Functional
testing Unit testing
Performance
testing
Integration
testing
Static analysis
Ethical
hacking
Process audits
UAT
7. … but do we develop the CORRECT software?
Features Used
The Standish Group estimate of features used in custom application development, 2014
Hardly Ever
50%
Often
20%
Infrequently
30%
8. Features Used
The Standish Group estimate of features used in custom application development, 2014
Hardly
Ever
50%
Often
20%
Infrequently
30%
… but do we develop the CORRECT software?
10. Most of the time we don’t have an
acceptance tests suite robust and
complete enough to be trusted
We don’t trust releases
11. Lack of documentation
Individuals and interactions OVER processes and tools
Working software OVER comprehensive documentation
Customer collaboration OVER contract negotiation
Responding to change OVER following a plan
We are
uncovering better
ways of
developing
software by doing
it and helping
others do it.
Through this work
we have come to
value:
That is, while
there is value
in the items on
the right, we
value the items
on the left
more.
The Agile manifestoThe Agile manifesto
12. How often have you finished a project in which technical
documentation is up-to-date with what software really does?
Individuals and interactions OVER processes and tools
Working software OVER comprehensive documentation
Customer collaboration OVER contract negotiation
Responding to change OVER following a plan
We are uncovering
better ways of
developing
software by doing
it and helping
others do it.
Through this work
we have come to
value:
That is, while
there is value
in the items on
the right, we
value the items
on the left
more.
The Agile manifestoThe Agile manifesto
Lack of documentation
13. And collaboration within the team?
We have
Quality issues
Ain’t my problem,
Software Quality is
what testers should
care about, isn’t it?
14. Devs? I think those are the
guys in the 4th floor or
something
Dev people keep returning
unresolved bugs
And collaboration within the team?
We have
Quality issues
Ain’t my problem,
Software Quality is
what testers should
care about, isn’t it?
15. This problem starts from here
• Analysis
• Development
• Testing
• Operations
As separated phases, estimated
and planned from the beginning of
the project
16. This problem starts from here
As separated phases, estimated
and planned from the beginning of
the project
• Analysis
• Development
• Testing
• Operations
17. BDD: How Devs and Business collaborate
BDD is a collaboration model between Business users and
Development team…
… consisting of establishing conversations based in concrete
examples of the application use, with the objective of reducing
misconceptions and assumptions…
… discovering during the process the features that truly provide
value
18. • Examples describing a new feature are
translated to a simple and common language,
without ambiguities (for example Gherkin)
• Development team transforms these examples
to a series of executable specifications as
automated tests
• A software feature will be completed whenever
every specification executes correctly
BD
D
TDD
Write a failing test
N cycles
BDD: How Devs and Business collaborate
19. Then, what is (and what not) BDD?
• Writing requirements
in Gherkin language
• Automating tests with
Cucumber
• Documenting
functionalities after
programming them
• A collaboration model
• A discovering process
• Understanding
Business needs
• Describing software
with examples
What it is What it’s not
21. Three amigos
1. PO talks with
Business about its
needs
2. The PO, a Dev and
a Tester meet to
elaborate scenarios
jointly
4. The scenarios
guide the dev and act
as automated tests
3. The tester
implements the
scenarios as
acceptance tests
5. Automated tests
provide feedback
about progress and
document the
application
22. A collaboration scenario
We want our application to
require a password with at least 8
characters, a number and a
capital letter
Don’t you mean you want
the application to require a
strong password?
23. Password strenght, xkcd, Randall Munroe
Password Security Accepta
ble?
secret Weak No
password Weak No
password1 Weak No
aBcdEfg1 Weak No
qwertY12 Weak No
dJeZDip1 Medium Yes
SeagullHedgehog Strong Yes
SeagullHedgehogC
atapult
Very
strong
Yes
A collaboration scenario
We want our application to
require a password with at least
8 characters, a number and a
capital letter
Don’t you mean you
want the application to
require a strong
password?
24. Discovering our Business
“In software development, ignorance is the constraint. You know a lot more about the
best way to build a particular solution after you’ve finished building it, but by then it’s
too late to take advantage of your knowledge.”
John Ferguson Smart, BDD in action, 2015
25. Implementing BDD: Describing scenarios
SCENARIO
Sending
Contact Form
Given John Doe enters contact form
And he fills the fields with his data and the
message
And accept legal clause
When he sends the query
Then the confirmation message is received
Given: Defines the context in which the
scenario is executed. In this step the starting
point for the example is established.
When: It’s the action that triggers the
example. It consists of an interaction with the
application, usually by a user, whose behavior
we want to validate.
Then: In this step the result expected by the
Business is defined, meaning the condition
that must be fulfilled for the scenario to be
considered correctly executed.
26. Implementing BDD: Automating scenarios
Scenario: Transfer money to a Savings account
Given my Checking account has a balance of 1000.00
And my Savings account has a balance of 2000.00
When I transfer 500.00 from my Checking account to my Savings account
Then I should have 500.00 in my Checking account
And I should have 2500.00 in my Savings account
27. Scenario: Transfer money to a Savings account
Given my Checking account has a balance of 1000.00
And my Savings account has a balance of 2000.00
When I transfer 500.00 from my Checking account to my Savings account
Then I should have 500.00 in my Checking account
And I should have 2500.00 in my Savings account
@Given(“^my (.*) account has a balance of (d+)$")
public void setupInitialAccount(AccountType accountType,
double amount) {
// Setup account
}
@When(“^I transfer (d+) from my (.*) account to my (.*) account$")
public void transferAmountBetweenAccounts(double amount, AccountType source, AccountType destination) {
// Perform action
}
@Then(“^I should have (d+) in my (.*) account$")
public void checkAccountAmount(double amount, AccountType accountType) {
// Assert amount
}
Implementing BDD: Automating scenarios
29. UI (manual & automatic)
API / Services
Unit
Detect errors / Certify releases
Exploratory
Testing
BDD levels: The Testing pyramid
UI
API / Services
Unit
Prevent errors / Provide value
30. BDD in the software building process
Scenarios execution should be part of the software integration,
building and deployment process.
Each scenario should be able to be executed separately, without any
concrete order. There should be no dependency between scenarios.
Scenarios are a code asset to be maintained under version control
systems.
The software building and deployment process additionally becomes a
process for building and deploying documentation and reports.
31. Reports: feature readiness
A feature is considered
ready to be deployed in
production whenever its
scenarios execute
correctly.
Feature readiness
Your business does not care whether your tests pass or not. What they want to know is
if the functionality is ready to be deployed in production.
32. Reports: feature coverage
Feature coverage shows
the % of features with
every defined scenario
executing correctly.
Feature coverage
33. Warning!, BDD is not a silver bullet
Business implication: We need the stakeholders involved
since the beginning of the project.
BDD is thought for Agile: it is a collaboration model to
fostering an iterative discovering of the requirements.
BDD doesn’t like silos: if the organization works in
isolated silos and collaboration doesn’t flow, the
progressive clarification of goals disappears.
Risk of high cost in test maintenance: experience and
knowledge are required in order to design maintainable
functional specifications and implement them correctly.
35. Nuestro catálogo de servicos
QA de GOBIERNO• Testing funcional
• Pruebas de Sistema
• Pruebas de Seguridad
• Pruebas de carga/rendimiento
• Análisis y control de la deuda técnica
• Definición y mejora de los procesos de
gobierno, ingeniería y calidad para la
Transformación Digital
• Formación en buenas prácticas de
desarrollo
• Implantación de una Oficina de Calidad
AGILE QA
• Apoyo metodológico
• Servicios de automatización en el
marco de un proceso de Entrega
Continua
• Automatización de pruebas
QA OPERATIVO
36. www.atsistemas.com
902 888 902
GRACIAS
Madrid
Oficinas Centrales:
C/Valle de Alcudia 3, Ed. 2
28232 - Las Rozas - Madrid
Selección y Recursos Humanos:
C/Acanto 22, Plta. 3
28045 - Madrid
C/Retama 7, Plta. 1
28045 - Madrid
Barcelona
Plaça de Catalunya 21, Plta. 2
08002 - Barcelona
Cádiz
Edificio Jerez Parque Empresarial, C/ del Desarrollo 2, Plta. 1
11047 - Jerez de la Frontera - Cádiz
Zaragoza
Centro Tecnológico TIC XXI, C/Bari 57, Plataforma Logística (PLA-ZA)
50197 - Zaragoza
A Coruña
Edificio Mans Polígono de Pocomaco, Parcela D22
15190 - A Coruña
Palma de Mallorca
Regus Palma Polígono de Son Castello, C/ Gremi de Sabaters 21, Plta. 2
07009 - Palma de Mallorca
Huelva
Parque Científico Tecnológico de Huelva, Edificio PCTH2000
21 110 - Aljaraque - Huelva