phpDay 2012: Scaling Communication via Continuous Integration
5 likes1,919 views
The document discusses the importance of developer culture and continuous deployment practices at Etsy, emphasizing trust, clean coding, and communication strategies. It explores the challenges and benefits of continuous integration and quality assurance within the development pipeline. Key insights include strategies for enhancing developer confidence and improving testing quality while fostering a culture of continuous improvement.
1 of 54
Ad
Recommended
PHP UK Conference 2012: Scaling Communication via Continuous Integration
PHP UK Conference 2012: Scaling Communication via Continuous IntegrationLB Denker The document discusses the importance of developer culture and continuous deployment at Etsy, emphasizing the cultural elements that facilitate effective communication and integration processes. It highlights the need for clean code and tests, confidence in deployment practices, and strategies for improving developer happiness. Additionally, the document outlines approaches to managing test quality and streamlining coding standards within a constantly evolving engineering environment.
Best pratice
Best praticeEugenio Romano The document discusses several important topics for software development including unit testing, clean coding principles, design patterns, and useful development tools. It emphasizes that tests are important for preventing bugs and should be included in all projects. Clean coding principles like DRY, KISS and SRP help produce code that is easier to read, change and maintain. Design patterns provide solutions to common problems and a shared vocabulary for developers. Useful tools include IDEs, version control systems, code analysis tools and text editors which can help programmers work more efficiently if used properly.
Testing and DevOps Culture: Lessons Learned
Testing and DevOps Culture: Lessons LearnedLB Denker This document discusses the speaker's background and experiences with software engineering practices. It covers his education in computational mathematics and computer science, past roles at Universal Instruments developing machine software and at Google and Etsy implementing DevOps practices. Key topics covered include the benefits of continuous integration, deployment and delivery; the importance of testing including test-driven development; and embracing interdependence between developers and other IT roles. Best practices are noted to be situational and relationships must be respected.
Distributed agile testing_for_enterprises
Distributed agile testing_for_enterprisesThoughtWorks Studios This document discusses distributed agile testing for enterprises. It covers challenges with distributed teams like reduced communication bandwidth and increased noise. It presents practices for distributed testing like using executable specifications, test automation, continuous integration (CI), and collaborating across functional teams. The presenters are Anand Bagmar and Manish Kumar from ThoughtWorks who have many years of experience in software testing.
Essential practices and thinking tools for Agile Adoption
Essential practices and thinking tools for Agile AdoptionSteven Mak Steven Mak presented tools and practices for adopting Agile, including:
- Thinking tools like systems thinking and lean thinking can help with adoption.
- Organizational practices like self-managing cross-functional teams and continuous improvement are important.
- Engineering practices like test-driven development, refactoring, and continuous integration can reduce technical debt.
- Adoption requires changing mindsets and habits through training, coaching, and leading by example.
Core Principles Of Ci
Core Principles Of CiOpenSource Connections Core Principles of CI was a presentation that covered:
1) The definition of continuous integration as automated builds that run many times a day.
2) The key aspects of CI including source code compilation, database integration, testing, inspection, deployment, feedback, and producing deployable software.
3) The benefits of CI like reduced human error, rapid feedback cycles, increased project visibility and confidence, and facilitating communication.
Agile Testing: The Role Of The Agile Tester
Agile Testing: The Role Of The Agile TesterDeclan Whelan The presentation by Declan Whelan on agile testing outlines the principles of agility, success factors for agile testing, and the roles of testers within agile teams. It emphasizes the importance of collaboration, continuous integration, and adapting testing practices to promote quality throughout the software development process. Additionally, the document discusses session-based testing as a method for auditable exploratory testing and the role of automated tests in supporting rapid iterations.
Agile testing for agile sparks kanban clients
Agile testing for agile sparks kanban clientsYuval Yeret The document discusses agile testing practices like continuous integration, test automation, and behavior driven development. It emphasizes delivering working, tested software frequently through smaller batches and providing early feedback. Automating tests is part of the definition of done to enable continuous integration. Quality assurance experts focus on riskier areas like performance and security testing rather than manual testing. Behavior driven development uses examples and acceptance tests to drive development and automation. Technical debt can be addressed incrementally by automating tests for new features and riskier areas first.
Continuous integration (eng)
Continuous integration (eng)Anatoliy Okhotnikov Continuous Integration (CI) is a software development practice where team members integrate their work frequently, tested through automated builds to identify errors quickly. This document outlines CI's practices, benefits, and tools, emphasizing communication, fast feedback, and the importance of maintaining a common source repository. The advantages of CI include reduced risks, easier bug detection, and improved developer collaboration, ultimately leading to a more efficient development process.
Agile Acceptance testing with Fitnesse
Agile Acceptance testing with FitnesseClareMcLennan The document discusses the implementation of Agile acceptance testing and FitNesse to improve software quality and testability. It details the challenges faced in achieving a 99.99% uptime and the evolution of testing processes over 12 months, highlighting the roles of testers and developers in creating a collaborative testing environment. Key outcomes include reduced testing time, positive shifts in programmer attitudes towards testing, and the establishment of a self-improving QA process.
Continuous Integration testing based on Selenium and Hudson
Continuous Integration testing based on Selenium and HudsonZbyszek Mockun This article discusses the use of open-source tools for automating tests in continuous integration environments, emphasizing the need for efficient regression testing within agile methodologies. It outlines the benefits of integrating automated tests with tools like Hudson and Selenium, as well as strategies for optimizing testing processes to minimize time spent while maximizing functionality. The author shares insights from personal experience in QA and highlights the advantages of utilizing open-source solutions.
Open Source tools in Continuous Integration environment (case study for agil...
Open Source tools in Continuous Integration environment (case study for agil...suwalki24.pl The document discusses the integration of automated testing into continuous integration (CI) environments using open-source tools like Hudson and Selenium. It highlights strategies to maintain high-quality releases while minimizing the regression testing time within agile methodologies. The article also emphasizes the necessity of running automated tests frequently after code commits to detect errors early and ensure efficient testing processes.
Turbocharge your automated tests with ci
Turbocharge your automated tests with ciOpenSource Connections The document details the importance and benefits of continuous integration (CI) in software development, including a definition and value proposition of CI, as well as the challenges teams face in implementing it. It discusses the need for cultural changes, effective communication, and addressing structural and tool-related challenges to successfully adopt CI practices. The presentation also outlines strategies for scaling CI efforts and emphasizes the significance of a well-maintained CI system for fostering a productive development environment.
Flexing your Agile Muscle - Agile Technical Concepts Explained
Flexing your Agile Muscle - Agile Technical Concepts ExplainedSandy Mamoli The document outlines agile technical practices, focusing on user stories, acceptance testing, unit testing, and continuous integration. It explains the agile framework's history, key features, and emphasizes the importance of collaboration among developers, testers, and business stakeholders for effective implementation. Additionally, it provides guidance on deploying a pipeline and best practices for maintaining quality through automated testing and feedback.
Testing in an Open Source Middleware Platform Space The WSO2 Way.
Testing in an Open Source Middleware Platform Space The WSO2 Way.WSO2 The document discusses testing practices at WSO2, an open source middleware company. It describes WSO2's engineering process, which is people-centric and influenced by the Apache way. It also outlines WSO2's agile testing principles and practices for testing SOA middleware, including unit, integration, end-to-end, performance, security, and cloud native testing. WSO2 utilizes a dedicated testing team that designs detailed test plans and executes tests in cycles to find and fix issues.
Beyond TDD: Enabling Your Team to Continuously Deliver Software
Beyond TDD: Enabling Your Team to Continuously Deliver SoftwareChris Weldon The document discusses advanced practices for software development beyond Test-Driven Development (TDD), emphasizing continuous integration and delivery to enhance the software release process. It highlights the importance of rapid feedback, collaboration among all team members, and strategies like Minimum Viable Product and feature toggles to manage incomplete features. The overall goal is to eliminate barriers to release, facilitate regular deployments, and improve the team's efficiency and confidence in delivering software.
Introduction To Continuous Integration
Introduction To Continuous IntegrationChristopher Read This document discusses continuous integration (CI), including why it is important, how it works through its core practices, and how CI evolves over time. CI is meant to catch bugs early, reduce merge conflicts, and make development teams more efficient by implementing automated builds, testing, and code integration. The core practices involve using a single source code repository, automating builds and testing, and publishing the latest version. CI is an evolving practice that changes as tools, languages, and development approaches change over time.
Audrys Kažukauskas - Introduction into Extreme Programming
Audrys Kažukauskas - Introduction into Extreme ProgrammingAgile Lietuva The document introduces extreme programming (XP) as an agile software development methodology that focuses on improving code quality, reducing bugs, and simplifying releases. It highlights key practices of XP such as test-driven development, pair programming, and continuous integration while comparing XP with Scrum methodologies. The document emphasizes that while agile practices have become mainstream, XP remains relevant and can be adapted alongside other approaches to fit specific team needs.
High Performance Software Engineering Teams
High Performance Software Engineering TeamsLars Thorup The document details best practices for creating high-performance engineering teams in software development, emphasizing the importance of automation, continuous integration, and collaboration between engineering and QA. Key strategies include reducing non-productive activities, enhancing testing frequency and quality, and prioritizing bug fixes. It also highlights the significance of using frameworks for automated unit and acceptance testing, as well as encouraging a culture of continuous improvement and transparency.
Agile Manifesto & XP
Agile Manifesto & XPSemen Arslan The document discusses the principles and practices of extreme programming (XP), an agile software development methodology. It outlines 12 core practices of XP including planning games, small releases, simple design, testing, pair programming, and continuous integration. Benefits include frequent feedback, adapting to change, and delivering working software early. Challenges involve customer availability and determining appropriate levels of documentation and planning.
extreme Programming
extreme ProgrammingBilal Shah As a user, I want to register for an account so that I can access the system.
PHX Session #3 - "It Works on My Machine!" Closing the Loop Between Developme...
PHX Session #3 - "It Works on My Machine!" Closing the Loop Between Developme...Steve Lange The document discusses closing the loop between development and testing. It emphasizes that quality is a shared responsibility of both developers and testers. Effective communication between these teams is important, and automation can help reduce manual testing effort. The document argues that by working together and applying lessons learned through each iteration, development and testing teams can improve their process and deliver high quality software.
Automate your way to agility
Automate your way to agilityYuval Yeret The document discusses the importance of automation in achieving agility within software development, emphasizing the positive impacts of continuous integration and automated testing on quality and delivery timelines. It highlights past challenges such as technical debt and partial automation, suggesting that comprehensive test automation is vital for successful agile practices. The author advocates for starting projects collaboratively with a focus on automation to enhance efficiency and customer satisfaction.
Scaling Quality by Building it in - Agile Tour Ottawa 2017
Scaling Quality by Building it in - Agile Tour Ottawa 2017Maurizio Mancini The document discusses the importance of building quality into software from the beginning, emphasizing that agile methodologies should include a focus on quality and testing at every stage. It identifies common pitfalls teams face when scaling quality, offers guidelines for effective test automation, and highlights the necessity for collaboration across agile roles to establish a quality mindset. Key recommendations include adopting a test-first approach and integrating testing practices throughout the development process to ensure robust software delivery.
Slides from "Taking an Holistic Approach to Product Quality"
Slides from "Taking an Holistic Approach to Product Quality"Peter Marshall The document discusses how adopting a DevOps culture, continuous testing, and a user-centric development approach can enhance software quality by aligning products with user expectations. It emphasizes the importance of operability, communication, and structured processes in creating a holistic quality strategy while also highlighting the need for automation in building, testing, and deployment. Additionally, it critiques traditional testing methods and promotes continuous testing as a fundamental practice in today’s fast-paced development environment.
Integreation
IntegreationSean Killeen The document describes the challenges of integrating technology and human processes in project management, emphasizing the need for a structured, unemotional approach to handle uncertainties. It outlines a 12-step process utilizing various tools (like Subversion, NUnit, and Octopus) to ensure code quality, traceability, and automation. The goal is to foster a dependable development environment that allows for efficient code management and customer satisfaction.
Creating change from within - Agile Practitioners 2012
Creating change from within - Agile Practitioners 2012Dror Helper The document discusses the challenges of implementing Agile methodologies within a development team, sharing the author's personal experiences and strategies over a year and a half. Key topics include the importance of TDD (Test-Driven Development), effective code reviews, continuous integration, and the necessity of making incremental changes for long-term improvement. The author emphasizes a collaborative and positive approach to change, highlighting that successful Agile implementation requires team involvement and persistence.
Are Your Continuous Tests Too Fragile for Agile?
Are Your Continuous Tests Too Fragile for Agile?Parasoft The document discusses the challenges and importance of continuous testing within agile development, emphasizing the need for effective quality assurance (QA) practices integrated throughout the development process. It highlights best practices for unit and functional testing, including creating maintainable test suites, establishing clear testing policies, and addressing common issues in testing such as developer resistance and the perception of testing as burdensome. The document also advocates for a 'spring cleaning' approach to eliminate ineffective tests and prioritize quality over quantity in testing practices.
Php|tek '12 It's More Than Just Style
Php|tek '12 It's More Than Just StyleLB Denker The document discusses coding standards and practices within PHP development, emphasizing the importance of style and adherence to specific coding rules. It highlights tools like PHP_CodeSniffer for maintaining code quality and ensures compatibility with various PHP versions. The article also encourages developing custom coding standards and integrating continuous testing within workflows.
Developer testing 201: When to Mock and When to Integrate
Developer testing 201: When to Mock and When to IntegrateLB Denker The document outlines advanced techniques for developer testing, focusing on unit, integration, and functional testing, while providing resources and tools such as PHPUnit and Mockery. It covers test sizes, custom assertions, and specific testing strategies for databases, filesystems, and networks. The aim is to build a comprehensive understanding of testing needs without being an introductory guide.
More Related Content
Similar to phpDay 2012: Scaling Communication via Continuous Integration (20)
Continuous integration (eng)
Continuous integration (eng)Anatoliy Okhotnikov Continuous Integration (CI) is a software development practice where team members integrate their work frequently, tested through automated builds to identify errors quickly. This document outlines CI's practices, benefits, and tools, emphasizing communication, fast feedback, and the importance of maintaining a common source repository. The advantages of CI include reduced risks, easier bug detection, and improved developer collaboration, ultimately leading to a more efficient development process.
Agile Acceptance testing with Fitnesse
Agile Acceptance testing with FitnesseClareMcLennan The document discusses the implementation of Agile acceptance testing and FitNesse to improve software quality and testability. It details the challenges faced in achieving a 99.99% uptime and the evolution of testing processes over 12 months, highlighting the roles of testers and developers in creating a collaborative testing environment. Key outcomes include reduced testing time, positive shifts in programmer attitudes towards testing, and the establishment of a self-improving QA process.
Continuous Integration testing based on Selenium and Hudson
Continuous Integration testing based on Selenium and HudsonZbyszek Mockun This article discusses the use of open-source tools for automating tests in continuous integration environments, emphasizing the need for efficient regression testing within agile methodologies. It outlines the benefits of integrating automated tests with tools like Hudson and Selenium, as well as strategies for optimizing testing processes to minimize time spent while maximizing functionality. The author shares insights from personal experience in QA and highlights the advantages of utilizing open-source solutions.
Open Source tools in Continuous Integration environment (case study for agil...
Open Source tools in Continuous Integration environment (case study for agil...suwalki24.pl The document discusses the integration of automated testing into continuous integration (CI) environments using open-source tools like Hudson and Selenium. It highlights strategies to maintain high-quality releases while minimizing the regression testing time within agile methodologies. The article also emphasizes the necessity of running automated tests frequently after code commits to detect errors early and ensure efficient testing processes.
Turbocharge your automated tests with ci
Turbocharge your automated tests with ciOpenSource Connections The document details the importance and benefits of continuous integration (CI) in software development, including a definition and value proposition of CI, as well as the challenges teams face in implementing it. It discusses the need for cultural changes, effective communication, and addressing structural and tool-related challenges to successfully adopt CI practices. The presentation also outlines strategies for scaling CI efforts and emphasizes the significance of a well-maintained CI system for fostering a productive development environment.
Flexing your Agile Muscle - Agile Technical Concepts Explained
Flexing your Agile Muscle - Agile Technical Concepts ExplainedSandy Mamoli The document outlines agile technical practices, focusing on user stories, acceptance testing, unit testing, and continuous integration. It explains the agile framework's history, key features, and emphasizes the importance of collaboration among developers, testers, and business stakeholders for effective implementation. Additionally, it provides guidance on deploying a pipeline and best practices for maintaining quality through automated testing and feedback.
Testing in an Open Source Middleware Platform Space The WSO2 Way.
Testing in an Open Source Middleware Platform Space The WSO2 Way.WSO2 The document discusses testing practices at WSO2, an open source middleware company. It describes WSO2's engineering process, which is people-centric and influenced by the Apache way. It also outlines WSO2's agile testing principles and practices for testing SOA middleware, including unit, integration, end-to-end, performance, security, and cloud native testing. WSO2 utilizes a dedicated testing team that designs detailed test plans and executes tests in cycles to find and fix issues.
Beyond TDD: Enabling Your Team to Continuously Deliver Software
Beyond TDD: Enabling Your Team to Continuously Deliver SoftwareChris Weldon The document discusses advanced practices for software development beyond Test-Driven Development (TDD), emphasizing continuous integration and delivery to enhance the software release process. It highlights the importance of rapid feedback, collaboration among all team members, and strategies like Minimum Viable Product and feature toggles to manage incomplete features. The overall goal is to eliminate barriers to release, facilitate regular deployments, and improve the team's efficiency and confidence in delivering software.
Introduction To Continuous Integration
Introduction To Continuous IntegrationChristopher Read This document discusses continuous integration (CI), including why it is important, how it works through its core practices, and how CI evolves over time. CI is meant to catch bugs early, reduce merge conflicts, and make development teams more efficient by implementing automated builds, testing, and code integration. The core practices involve using a single source code repository, automating builds and testing, and publishing the latest version. CI is an evolving practice that changes as tools, languages, and development approaches change over time.
Audrys Kažukauskas - Introduction into Extreme Programming
Audrys Kažukauskas - Introduction into Extreme ProgrammingAgile Lietuva The document introduces extreme programming (XP) as an agile software development methodology that focuses on improving code quality, reducing bugs, and simplifying releases. It highlights key practices of XP such as test-driven development, pair programming, and continuous integration while comparing XP with Scrum methodologies. The document emphasizes that while agile practices have become mainstream, XP remains relevant and can be adapted alongside other approaches to fit specific team needs.
High Performance Software Engineering Teams
High Performance Software Engineering TeamsLars Thorup The document details best practices for creating high-performance engineering teams in software development, emphasizing the importance of automation, continuous integration, and collaboration between engineering and QA. Key strategies include reducing non-productive activities, enhancing testing frequency and quality, and prioritizing bug fixes. It also highlights the significance of using frameworks for automated unit and acceptance testing, as well as encouraging a culture of continuous improvement and transparency.
Agile Manifesto & XP
Agile Manifesto & XPSemen Arslan The document discusses the principles and practices of extreme programming (XP), an agile software development methodology. It outlines 12 core practices of XP including planning games, small releases, simple design, testing, pair programming, and continuous integration. Benefits include frequent feedback, adapting to change, and delivering working software early. Challenges involve customer availability and determining appropriate levels of documentation and planning.
extreme Programming
extreme ProgrammingBilal Shah As a user, I want to register for an account so that I can access the system.
PHX Session #3 - "It Works on My Machine!" Closing the Loop Between Developme...
PHX Session #3 - "It Works on My Machine!" Closing the Loop Between Developme...Steve Lange The document discusses closing the loop between development and testing. It emphasizes that quality is a shared responsibility of both developers and testers. Effective communication between these teams is important, and automation can help reduce manual testing effort. The document argues that by working together and applying lessons learned through each iteration, development and testing teams can improve their process and deliver high quality software.
Automate your way to agility
Automate your way to agilityYuval Yeret The document discusses the importance of automation in achieving agility within software development, emphasizing the positive impacts of continuous integration and automated testing on quality and delivery timelines. It highlights past challenges such as technical debt and partial automation, suggesting that comprehensive test automation is vital for successful agile practices. The author advocates for starting projects collaboratively with a focus on automation to enhance efficiency and customer satisfaction.
Scaling Quality by Building it in - Agile Tour Ottawa 2017
Scaling Quality by Building it in - Agile Tour Ottawa 2017Maurizio Mancini The document discusses the importance of building quality into software from the beginning, emphasizing that agile methodologies should include a focus on quality and testing at every stage. It identifies common pitfalls teams face when scaling quality, offers guidelines for effective test automation, and highlights the necessity for collaboration across agile roles to establish a quality mindset. Key recommendations include adopting a test-first approach and integrating testing practices throughout the development process to ensure robust software delivery.
Slides from "Taking an Holistic Approach to Product Quality"
Slides from "Taking an Holistic Approach to Product Quality"Peter Marshall The document discusses how adopting a DevOps culture, continuous testing, and a user-centric development approach can enhance software quality by aligning products with user expectations. It emphasizes the importance of operability, communication, and structured processes in creating a holistic quality strategy while also highlighting the need for automation in building, testing, and deployment. Additionally, it critiques traditional testing methods and promotes continuous testing as a fundamental practice in today’s fast-paced development environment.
Integreation
IntegreationSean Killeen The document describes the challenges of integrating technology and human processes in project management, emphasizing the need for a structured, unemotional approach to handle uncertainties. It outlines a 12-step process utilizing various tools (like Subversion, NUnit, and Octopus) to ensure code quality, traceability, and automation. The goal is to foster a dependable development environment that allows for efficient code management and customer satisfaction.
Creating change from within - Agile Practitioners 2012
Creating change from within - Agile Practitioners 2012Dror Helper The document discusses the challenges of implementing Agile methodologies within a development team, sharing the author's personal experiences and strategies over a year and a half. Key topics include the importance of TDD (Test-Driven Development), effective code reviews, continuous integration, and the necessity of making incremental changes for long-term improvement. The author emphasizes a collaborative and positive approach to change, highlighting that successful Agile implementation requires team involvement and persistence.
Are Your Continuous Tests Too Fragile for Agile?
Are Your Continuous Tests Too Fragile for Agile?Parasoft The document discusses the challenges and importance of continuous testing within agile development, emphasizing the need for effective quality assurance (QA) practices integrated throughout the development process. It highlights best practices for unit and functional testing, including creating maintainable test suites, establishing clear testing policies, and addressing common issues in testing such as developer resistance and the perception of testing as burdensome. The document also advocates for a 'spring cleaning' approach to eliminate ineffective tests and prioritize quality over quantity in testing practices.
More from LB Denker (6)
Php|tek '12 It's More Than Just Style
Php|tek '12 It's More Than Just StyleLB Denker The document discusses coding standards and practices within PHP development, emphasizing the importance of style and adherence to specific coding rules. It highlights tools like PHP_CodeSniffer for maintaining code quality and ensures compatibility with various PHP versions. The article also encourages developing custom coding standards and integrating continuous testing within workflows.
Developer testing 201: When to Mock and When to Integrate
Developer testing 201: When to Mock and When to IntegrateLB Denker The document outlines advanced techniques for developer testing, focusing on unit, integration, and functional testing, while providing resources and tools such as PHPUnit and Mockery. It covers test sizes, custom assertions, and specific testing strategies for databases, filesystems, and networks. The aim is to build a comprehensive understanding of testing needs without being an introductory guide.
Developer testing 101: Become a Testing Fanatic
Developer testing 101: Become a Testing FanaticLB Denker The document provides an overview of developer testing, focusing on the goals and methodologies of developer testing such as test-driven development (TDD) and the use of xUnit testing frameworks. It discusses the importance of testing types, assertions, and tools while highlighting the agile approach to software development. Key topics include the pyramid of testing, handling external dependencies, and various testing strategies to ensure software correctness and confidence in development.
QC Merge 2012: Growing community
QC Merge 2012: Growing communityLB Denker The document discusses the evolution of Etsy's culture and organizational structure, emphasizing the importance of communication in system design. It highlights the growth of the workforce and the shift from SVN to Git to manage their repository more effectively. Key takeaways include the continuous effort needed to cultivate culture and the importance of simplicity in operations.
Are Your Tests Really Helping You?
Are Your Tests Really Helping You?LB Denker The document discusses different types of software tests and their purposes. It suggests that unit tests should focus on verifying correctness through line and branch coverage and gaining confidence in individual functions. Integration tests are best for experimenting with third-party code but may be a waste of time testing functionality that is not your own. Functional tests work well early in development to verify requirements and key features but may do too much as code changes rapidly.
Php com con-2011
Php com con-2011LB Denker 1) The document discusses the evolution of test automation and continuous deployment practices at a company over time.
2) Early on, deployments were weekly and error-prone, but tools like Deployinator automated deployments and increased the frequency to several per day.
3) Continuous integration tools like Buildbot and Jenkins were implemented to run tests on code commits and provide feedback, helping eliminate bugs and speeding development cycles.
4) Over time, the company refined their testing practices, moving more tests to PHPUnit for consistency, classifying test types, and implementing features like database mocking to make tests more reliable and maintainable.
Ad
Recently uploaded (20)
FIDO Seminar: Perspectives on Passkeys & Consumer Adoption.pptx
FIDO Seminar: Perspectives on Passkeys & Consumer Adoption.pptxFIDO Alliance FIDO Seminar: Perspectives on Passkeys & Consumer Adoption
AI VIDEO MAGAZINE - June 2025 - r/aivideo
AI VIDEO MAGAZINE - June 2025 - r/aivideo1pcity Studios, Inc AI VIDEO MAGAZINE - r/aivideo community newsletter – Exclusive Tutorials: How to make an AI VIDEO from scratch, PLUS: How to make AI MUSIC, Hottest ai videos of 2025, Exclusive Interviews, New Tools, Previews, and MORE - JUNE 2025 ISSUE -
Integration of Utility Data into 3D BIM Models Using a 3D Solids Modeling Wor...
Integration of Utility Data into 3D BIM Models Using a 3D Solids Modeling Wor...Safe Software Jacobs has developed a 3D utility solids modelling workflow to improve the integration of utility data into 3D Building Information Modeling (BIM) environments. This workflow, a collaborative effort between the New Zealand Geospatial Team and the Australian Data Capture Team, employs FME to convert 2D utility data into detailed 3D representations, supporting enhanced spatial analysis and clash detection.
To enable the automation of this process, Jacobs has also developed a survey data standard that standardizes the capture of existing utilities. This standard ensures consistency in data collection, forming the foundation for the subsequent automated validation and modelling steps. The workflow begins with the acquisition of utility survey data, including attributes such as location, depth, diameter, and material of utility assets like pipes and manholes. This data is validated through a custom-built tool that ensures completeness and logical consistency, including checks for proper connectivity between network components. Following validation, the data is processed using an automated modelling tool to generate 3D solids from 2D geometric representations. These solids are then integrated into BIM models to facilitate compatibility with 3D workflows and enable detailed spatial analyses.
The workflow contributes to improved spatial understanding by visualizing the relationships between utilities and other infrastructure elements. The automation of validation and modeling processes ensures consistent and accurate outputs, minimizing errors and increasing workflow efficiency.
This methodology highlights the application of FME in addressing challenges associated with geospatial data transformation and demonstrates its utility in enhancing data integration within BIM frameworks. By enabling accurate 3D representation of utility networks, the workflow supports improved design collaboration and decision-making in complex infrastructure projects
Floods in Valencia: Two FME-Powered Stories of Data Resilience
Floods in Valencia: Two FME-Powered Stories of Data ResilienceSafe Software In October 2024, the Spanish region of Valencia faced severe flooding that underscored the critical need for accessible and actionable data. This presentation will explore two innovative use cases where FME facilitated data integration and availability during the crisis. The first case demonstrates how FME was used to process and convert satellite imagery and other geospatial data into formats tailored for rapid analysis by emergency teams. The second case delves into making human mobility data—collected from mobile phone signals—accessible as source-destination matrices, offering key insights into population movements during and after the flooding. These stories highlight how FME's powerful capabilities can bridge the gap between raw data and decision-making, fostering resilience and preparedness in the face of natural disasters. Attendees will gain practical insights into how FME can support crisis management and urban planning in a changing climate.
Enabling BIM / GIS integrations with Other Systems with FME
Enabling BIM / GIS integrations with Other Systems with FMESafe Software Jacobs has successfully utilized FME to tackle the complexities of integrating diverse data sources in a confidential $1 billion campus improvement project. The project aimed to create a comprehensive digital twin by merging Building Information Modeling (BIM) data, Construction Operations Building Information Exchange (COBie) data, and various other data sources into a unified Geographic Information System (GIS) platform. The challenge lay in the disparate nature of these data sources, which were siloed and incompatible with each other, hindering efficient data management and decision-making processes.
To address this, Jacobs leveraged FME to automate the extraction, transformation, and loading (ETL) of data between ArcGIS Indoors and IBM Maximo. This process ensured accurate transfer of maintainable asset and work order data, creating a comprehensive 2D and 3D representation of the campus for Facility Management. FME's server capabilities enabled real-time updates and synchronization between ArcGIS Indoors and Maximo, facilitating automatic updates of asset information and work orders. Additionally, Survey123 forms allowed field personnel to capture and submit data directly from their mobile devices, triggering FME workflows via webhooks for real-time data updates. This seamless integration has significantly enhanced data management, improved decision-making processes, and ensured data consistency across the project lifecycle.
ENERGY CONSUMPTION CALCULATION IN ENERGY-EFFICIENT AIR CONDITIONER.pdf
ENERGY CONSUMPTION CALCULATION IN ENERGY-EFFICIENT AIR CONDITIONER.pdfMuhammad Rizwan Akram DC Inverter Air Conditioners are revolutionizing the cooling industry by delivering affordable,
energy-efficient, and environmentally sustainable climate control solutions. Unlike conventional
fixed-speed air conditioners, DC inverter systems operate with variable-speed compressors that
modulate cooling output based on demand, significantly reducing energy consumption and
extending the lifespan of the appliance.
These systems are critical in reducing electricity usage, lowering greenhouse gas emissions, and
promoting eco-friendly technologies in residential and commercial sectors. With advancements in
compressor control, refrigerant efficiency, and smart energy management, DC inverter air conditioners
have become a benchmark in sustainable climate control solutions
Can We Use Rust to Develop Extensions for PostgreSQL? (POSETTE: An Event for ...
Can We Use Rust to Develop Extensions for PostgreSQL? (POSETTE: An Event for ...NTT DATA Technology & Innovation Can We Use Rust to Develop Extensions for PostgreSQL?
(POSETTE: An Event for Postgres 2025)
June 11, 2025
Shinya Kato
NTT DATA Japan Corporation
FME for Distribution & Transmission Integrity Management Program (DIMP & TIMP)
FME for Distribution & Transmission Integrity Management Program (DIMP & TIMP)Safe Software Peoples Gas in Chicago, IL has changed to a new Distribution & Transmission Integrity Management Program (DIMP & TIMP) software provider in recent years. In order to successfully deploy the new software we have created a series of ETL processes using FME Form to transform our gas facility data to meet the required DIMP & TIMP data specifications. This presentation will provide an overview of how we used FME to transform data from ESRI’s Utility Network and several other internal and external sources to meet the strict data specifications for the DIMP and TIMP software solutions.
The State of Web3 Industry- Industry Report
The State of Web3 Industry- Industry ReportLiveplex Web3 is poised for mainstream integration by 2030, with decentralized applications potentially reaching billions of users through improved scalability, user-friendly wallets, and regulatory clarity. Many forecasts project trillions of dollars in tokenized assets by 2030 , integration of AI, IoT, and Web3 (e.g. autonomous agents and decentralized physical infrastructure), and the possible emergence of global interoperability standards. Key challenges going forward include ensuring security at scale, preserving decentralization principles under regulatory oversight, and demonstrating tangible consumer value to sustain adoption beyond speculative cycles.
Providing an OGC API Processes REST Interface for FME Flow
Providing an OGC API Processes REST Interface for FME FlowSafe Software This presentation will showcase an adapter for FME Flow that provides REST endpoints for FME Workspaces following the OGC API Processes specification. The implementation delivers robust, user-friendly API endpoints, including standardized methods for parameter provision. Additionally, it enhances security and user management by supporting OAuth2 authentication. Join us to discover how these advancements can elevate your enterprise integration workflows and ensure seamless, secure interactions with FME Flow.
TrustArc Webinar - 2025 Global Privacy Survey
TrustArc Webinar - 2025 Global Privacy SurveyTrustArc How does your privacy program compare to your peers? What challenges are privacy teams tackling and prioritizing in 2025?
In the sixth annual Global Privacy Benchmarks Survey, we asked global privacy professionals and business executives to share their perspectives on privacy inside and outside their organizations. The annual report provides a 360-degree view of various industries' priorities, attitudes, and trends. See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar features an expert panel discussion and data-driven insights to help you navigate the shifting privacy landscape. Whether you are a privacy officer, legal professional, compliance specialist, or security expert, this session will provide actionable takeaways to strengthen your privacy strategy.
This webinar will review:
- The emerging trends in data protection, compliance, and risk
- The top challenges for privacy leaders, practitioners, and organizations in 2025
- The impact of evolving regulations and the crossroads with new technology, like AI
Predictions for the future of privacy in 2025 and beyond
Bridging the divide: A conversation on tariffs today in the book industry - T...
Bridging the divide: A conversation on tariffs today in the book industry - T...BookNet Canada A collaboration-focused conversation on the recently imposed US and Canadian tariffs where speakers shared insights into the current legislative landscape, ongoing advocacy efforts, and recommended next steps. This event was presented in partnership with the Book Industry Study Group.
Link to accompanying resource: https://bnctechforum.ca/sessions/bridging-the-divide-a-conversation-on-tariffs-today-in-the-book-industry/
Presented by BookNet Canada and the Book Industry Study Group on May 29, 2025 with support from the Department of Canadian Heritage.
Reducing Conflicts and Increasing Safety Along the Cycling Networks of East-F...
Reducing Conflicts and Increasing Safety Along the Cycling Networks of East-F...Safe Software In partnership with the Belgian Province of East-Flanders this project aimed to reduce conflicts and increase safety along a cycling route between the cities of Oudenaarde and Ghent. To achieve this goal, the current cycling network data needed some extra key information, including: Speed limits for segments, Access restrictions for different users (pedestrians, cyclists, motor vehicles, etc.), Priority rules at intersections. Using a 360° camera and GPS mounted on a measuring bicycle, we collected images of traffic signs and ground markings along the cycling lanes building up mobile mapping data. Image recognition technologies identified the road signs, creating a dataset with their locations and codes. The data processing entailed three FME workspaces. These included identifying valid intersections with other networks (e.g., roads, railways), creating a topological network between segments and intersections and linking road signs to segments and intersections based on proximity and orientation. Additional features, such as speed zones, inheritance of speed and access to neighbouring segments were also implemented to further enhance the data. The final results were visualized in ArcGIS, enabling analysis for the end users. The project provided them with key insights, including statistics on accessible road segments, speed limits, and intersection priorities. These will make the cycling paths more safe and uniform, by reducing conflicts between users.
Creating Inclusive Digital Learning with AI: A Smarter, Fairer Future
Creating Inclusive Digital Learning with AI: A Smarter, Fairer FutureImpelsys Inc. Have you ever struggled to read a tiny label on a medicine box or tried to navigate a confusing website? Now imagine if every learning experience felt that way—every single day.
For millions of people living with disabilities, poorly designed content isn’t just frustrating. It’s a barrier to growth. Inclusive learning is about fixing that. And today, AI is helping us build digital learning that’s smarter, kinder, and accessible to everyone.
Accessible learning increases engagement, retention, performance, and inclusivity for everyone. Inclusive design is simply better design.
June Patch Tuesday
June Patch TuesdayIvanti Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
“Why It’s Critical to Have an Integrated Development Methodology for Edge AI,...
“Why It’s Critical to Have an Integrated Development Methodology for Edge AI,...Edge AI and Vision Alliance For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2025/06/why-its-critical-to-have-an-integrated-development-methodology-for-edge-ai-a-presentation-from-lattice-semiconductor/
Sreepada Hegade, Director of ML Systems and Software at Lattice Semiconductor, presents the “Why It’s Critical to Have an Integrated Development Methodology for Edge AI” tutorial at the May 2025 Embedded Vision Summit.
The deployment of neural networks near sensors brings well-known advantages such as lower latency, privacy and reduced overall system cost—but also brings significant challenges that complicate development. These challenges can be addressed effectively by choosing the right solution and design methodology. The low-power FPGAs from Lattice are well poised to enable efficient edge implementation of models, while Lattice’s proven development methodology helps to mitigate the challenges and risks associated with edge model deployment.
In this presentation, Hegade explains the importance of an integrated framework that tightly consolidates different aspects of edge AI development, including training, quantization of networks for edge deployment, integration with sensors and inferencing. He also illustrates how Lattice’s simplified tool flow helps to achieve the best trade-off between power, performance and efficiency using low-power FPGAs for edge deployment of various AI workloads.
Crypto Super 500 - 14th Report - June2025.pdf
Crypto Super 500 - 14th Report - June2025.pdfStephen Perrenod This OrionX's 14th semi-annual report on the state of the cryptocurrency mining market. The report focuses on Proof-of-Work cryptocurrencies since those use substantial supercomputer power to mint new coins and encode transactions on their blockchains. Only two make the cut this time, Bitcoin with $18 billion of annual economic value produced and Dogecoin with $1 billion. Bitcoin has now reached the Zettascale with typical hash rates of 0.9 Zettahashes per second. Bitcoin is powered by the world's largest decentralized supercomputer in a continuous winner take all lottery incentive network.
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdf
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdfcaoyixuan2019 A presentation at Internetware 2025.
Can We Use Rust to Develop Extensions for PostgreSQL? (POSETTE: An Event for ...
Can We Use Rust to Develop Extensions for PostgreSQL? (POSETTE: An Event for ...NTT DATA Technology & Innovation
“Why It’s Critical to Have an Integrated Development Methodology for Edge AI,...
“Why It’s Critical to Have an Integrated Development Methodology for Edge AI,...Edge AI and Vision Alliance
Ad
phpDay 2012: Scaling Communication via Continuous Integration
- 1. Scaling Communication via Continuous Integration Th e Fi n di ngs Th us Fa r!
- 2. LB Denker Anthropologist of Developer Culture @ Etsy
- 3. Anthropologist?!? ... only sort of ...
- 4. Methods of an Anthropologist Participant Observation Interviews Surveys
- 5. Developer Culture “The most important component of The Etsy Way is culture and that is as difficult to teach as it is important” — Chad Dickerson, CEO
- 6. Acquiring Culture “... humans acquire culture through the learning processes of enculturation and socialization ...”
- 7. Developer Culture “Always Be Pushing” Developer Happiness We trust people
- 8. “Anthropology demands the open-mindedness with which one must look and listen, record in astonishment and that which one would not have been able to guess.” — Margaret Mead
- 9. Deployinating All the Pushes One Button (stage) Logging Monitoring No Child Safety Locks
- 10. Anyone Can Deploy! Board Members Included
- 11. 20 Minutes or Less The Power of Continuous Deployment
- 12. Continuous What?!? Continuous... Unceremoniously... Initiated By... Push New Code Deployment Anyone To Production Apply Quality Integration Anyone Process Release New Delivery Product Feature
- 18. Communication Theory 1. The Basic Elements of Communication Source Destination Sender Message Channel Feedback Receiver 2. Goal-Oriented Communication
- 19. Goals “Always Be Pushing” You Shouldn’t Push on Red You Should Write Clean Tests You Should Write Clean Code Trust Everyone To Do The Right Thing
- 20. “Always Be Pushing” Instilling Confidence Th e Fi rs t In te r v ie ws
- 21. Confidence Continuous Deployment is... Scary A Safety Net Depends on Your Point of View
- 22. Branching was Too Costly
- 23. Always Ship Trunk Branch in Code, not in Version Control Write Tools to Work with Trunk Do not Write Tools to Work with Branches Write Transparent Tools
- 24. Quality Process was Coupled to Pipeline
- 25. ‘Try’ Before You Commit Ability to Run Tests in CI Environment Actually Continuous Integration! Community Enforced! No Excuses!
- 26. Confidence Boost! The Impact of Knowing that Changes Pass the Tests Before Getting in the Pipeline
- 27. Why ‘Try’? No more clogging the pipeline CI in Pipeline was Final Sanity Check
- 28. Goal Achieved “Always Be Pushing”
- 29. You Should Not Push on Red De-Noising the Communication Channel Pa rt ic ip a n t Ob se r v ati on s over IRC
- 30. Where We Started From... Number of Total Time Flakiness Support Tests ~30 Practically Legacy Unknown ~50% Minutes None ~8 Platform ~1200 ~20% Small Core Minutes
- 31. A Bunch of Noise Need to Know How Much is Being Covered Need to Know What is Being Tested Need to Be Able to Detect Test Runner Errors Need to Have Actionable Test Results (Ownership)
- 32. De-Noise Number of Total Time Flakiness Support Tests ~30 Practically Legacy Unknown ~50% Minutes None >8 Platform >1200 ~5% Small Core Minutes
- 33. Goal Achieved You Should Not Push on Red
- 34. You Should Write Clean Tests Writing Simple Tests Isn’t Always So Simple Alter n ati ve Te ach ing Met h od s
- 35. How To Improve Test Quality Teach Them! But People Need to Want to Learn
- 36. Prove It! Number of Average Test Time Tests Time per Test Platform Tests 7:01 2332 0.18 seconds 0.00337 Unit Tests 0:10 2432 seconds DBUnit Tests 0:32 70 0.09 seconds December 2010
- 37. Test Classification PHPUnit @group PHPUnit XML Configuration + Some Pake Split By Point of Error ie. cache, database, network, sleep, time, etc. Flaky Test Silo
- 38. Goal Achieved You Should Write Clean Tests
- 39. Too Much To Read ... and to Communicate
- 40. How Do Communicate This? E-Mail? Nope! Wiki? Nope! Blog? Nope! Simplify Jenkins UI? YES!
- 41. Silent Green Taking a Chapter Out of xUnit Principles
- 42. Jenkins Plugins Master Project Plugin Triggering User Plugin Deployinator Plugin * All Available on github.com/etsy
- 43. You Should Write Clean Code Not Everyone Can Read (and Follow) a Coding Standard En a bl ing C ul tu re In fl ue n ce
- 44. Clean Code Start with Syntax Move to Style Then to Design Level
- 45. PHP Lint Run Locally Run on Pre-Commit Run on CI
- 46. Using CodeSniffer Draft Coding Style Guidelines Experiment With Various Sniffs Discover Actual Coding Syntax Tendencies Decide on Changes to Coding Style Guidelines Create a Strategy on How to Get to Green
- 47. Work in Progress You Should Write Clean Code
- 48. Getting to Green Send ‘Blame’ E-Mails Use a Staging Job in Try Do a Fix-It Competition
- 49. Trust Everyone To Do The Right Thing Balancing Enforcement with Freedom Fu tu re Wor k
- 50. Continuously Growing a Continuously Evolving Culture
- 51. Recently Done Code Reviews, Second Pair of Eyes PHPUnit --strict Standards PHPUnit Testing Standards Log All the Errors E_ALL | E_STRICT
- 52. More To Do Entire Coding Standard in CI Mess Detector Standards More PHPUnit Testing Standards ...
- 53. Developer Culture “Always Be Pushing” Developer Happiness We trust people
- 54. Company etsy.com About Our Craft codeascraft.com More From Me elblinkin.info
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: \n
- #54: \n
- #55: \n
- #56: \n
- #57: \n