100 tests per second - 40 releases per week
•
2 likes•386 views
This talk shows how the Triggerz engineering team continuously deliver new software versions to our users. The Triggerz product is a web application built with React, Node.js and PostgreSQL. The product has been live since October 2017 with users worldwide. We have built a simple continuous deployment pipeline, also mostly in JavaScript, that we use to validate every push to master before deploying it automatically to production. This talk demonstrates how we write tests and how the pipeline is scripted. We discuss the thinking behind and the tools that we've used to do continuous delivery.
Report
Share
Report
Share
Download to read offline
Recommended
Automated Testing for Embedded Software in C or C++
This document discusses automated testing for embedded C software. It introduces Lars Thorup and provides an agenda for the document. It then defines automated testing, describes the Unity testing framework for embedded C, and provides an example of how to handle dependencies in testing. It advocates for continuous integration, breaking dependencies through abstraction and injection, and explains how automated testing can improve software quality through faster development and preventing bugs.
Python in Test automation
This document discusses using Python for test automation. It introduces the author as a senior developer in test automation using Python. The document outlines topics to be covered, including testing, automation, different Python modules for test automation, and demos. It promotes Python for test automation due to its ease of use, readability, cross-platform capabilities, large community and support libraries.
Continuous performance: Load testing for developers with gatling
Slide deck of my presentation on Load testing for developers with Gatling at the J-Fall 2015 conference (November 5th 2015 in Ede, The Netherlands).
Никита Манько “Code review”
Code review is recommended when code contains complex business logic, external API changes, or high risk of introducing bugs. It helps reduce bugs by having another developer review changes before merging. Effective code review involves over-the-shoulder reviews or pair programming to catch issues early, as well as unit and integration tests to prevent regressions.
Automation testing
This document discusses automated testing and provides an overview of the automation process. It covers the benefits of automated testing such as being fast, reliable and repeatable. The document recommends tests that are good candidates for automation like regression and data-driven tests. It also outlines the preparation needed before automating tests. Examples of popular automation tools are provided, including QTP, Selenium and LoadRunner. The automation process is shown as executing test steps and verifying checkpoints with test data to validate initial and end conditions.
Continuous performance: Load testing for developers with gatling @ JavaOne 2016
Slide deck on my presentation on Continuous performance: Load testing for developers with gatling given at JavaOne 2016
TestWorks Conf Performance testing made easy with gatling - Guillaume Corré
The document outlines an agenda for a Gatling workshop. It covers exercises on using Gatling's architecture and DSL for load testing. The exercises range from basic to more advanced topics like making dynamic requests, capturing response data, and iterating over elements. Guidelines are provided for each exercise on things like the appropriate checks, feeders, and DSL elements to use. The document also notes that solutions to the exercises will be made available after the workshop.
Qtp training session I
This document provides an overview and agenda for a QTP training session. It discusses the advantages of automation testing over manual testing, introduces QTP and its purpose as a functional and regression test automation tool. It outlines the key elements of the QTP tool window and describes the testing process which involves analyzing the application, preparing test infrastructure, building tests, enhancing tests with checkpoints and logic, debugging and running tests, and reporting defects. The document also covers the basics of recording tests in QTP and the different recording types (normal, analogue, low level), and provides an overview of playback.
Recommended
Automated Testing for Embedded Software in C or C++
This document discusses automated testing for embedded C software. It introduces Lars Thorup and provides an agenda for the document. It then defines automated testing, describes the Unity testing framework for embedded C, and provides an example of how to handle dependencies in testing. It advocates for continuous integration, breaking dependencies through abstraction and injection, and explains how automated testing can improve software quality through faster development and preventing bugs.
Python in Test automation
This document discusses using Python for test automation. It introduces the author as a senior developer in test automation using Python. The document outlines topics to be covered, including testing, automation, different Python modules for test automation, and demos. It promotes Python for test automation due to its ease of use, readability, cross-platform capabilities, large community and support libraries.
Continuous performance: Load testing for developers with gatling
Slide deck of my presentation on Load testing for developers with Gatling at the J-Fall 2015 conference (November 5th 2015 in Ede, The Netherlands).
Никита Манько “Code review”
Code review is recommended when code contains complex business logic, external API changes, or high risk of introducing bugs. It helps reduce bugs by having another developer review changes before merging. Effective code review involves over-the-shoulder reviews or pair programming to catch issues early, as well as unit and integration tests to prevent regressions.
Automation testing
This document discusses automated testing and provides an overview of the automation process. It covers the benefits of automated testing such as being fast, reliable and repeatable. The document recommends tests that are good candidates for automation like regression and data-driven tests. It also outlines the preparation needed before automating tests. Examples of popular automation tools are provided, including QTP, Selenium and LoadRunner. The automation process is shown as executing test steps and verifying checkpoints with test data to validate initial and end conditions.
Continuous performance: Load testing for developers with gatling @ JavaOne 2016
Slide deck on my presentation on Continuous performance: Load testing for developers with gatling given at JavaOne 2016
TestWorks Conf Performance testing made easy with gatling - Guillaume Corré
The document outlines an agenda for a Gatling workshop. It covers exercises on using Gatling's architecture and DSL for load testing. The exercises range from basic to more advanced topics like making dynamic requests, capturing response data, and iterating over elements. Guidelines are provided for each exercise on things like the appropriate checks, feeders, and DSL elements to use. The document also notes that solutions to the exercises will be made available after the workshop.
Qtp training session I
This document provides an overview and agenda for a QTP training session. It discusses the advantages of automation testing over manual testing, introduces QTP and its purpose as a functional and regression test automation tool. It outlines the key elements of the QTP tool window and describes the testing process which involves analyzing the application, preparing test infrastructure, building tests, enhancing tests with checkpoints and logic, debugging and running tests, and reporting defects. The document also covers the basics of recording tests in QTP and the different recording types (normal, analogue, low level), and provides an overview of playback.
Automating Your Way to Greatness by Combining OutSystems CI/CD With the Power...
Having built-in CI/CD capabilities has always been a core tenet of the OutSystems platform. As customer factories have grown and CI/CD pipelines have become more complex, OutSystems has developed an integration with some of the leading CI/CD DevOps tools in the market, Jenkins, and Azure DevOps to tackle some of the challenges of managing enterprise-grade CI/CD pipelines.
Python Testing Fundamentals
This document provides an overview of the Python unittest module for writing and running automated tests. It discusses how the unittest.TestCase class is used to define test classes with methods named "test_" that contain assertions. The unittest module then handles running the tests and provides features like test organization, discovery of test methods, and integration with other tools.
Unit Testing your React / Redux app (@BucharestJS)
React and Redux took the world by storm. These JavaScript libraries allow you to write applications consisting of reusable components while avoiding bugs related to side-effects. But I suspect that developers do not unit test their React/Redux code. Or at least not as much as they could. During this talk, I will showcase the unit tests we have written for our eventriX product. These tests run fast and cover the most important aspects of our client-side code running in the browser. These practical real-world examples could inspire you to write more and better unit tests for your own React/Redux application.
Testing With OutSystems
This document provides an agenda for a lab on testing with OutSystems. The lab will give an overview of testing with OutSystems, introduce the BDD testing framework and Gherkin language, and include a hands-on portion. Attendees will learn about Behavior Driven Development, the OutSystems Forge Component for BDD, and how to get started using Gherkin through an interactive demo link.
Test driving QML
How to test-drive your Qt QML code. Overview on how you do simple testing, UI level testing, synchronous testing, data-driven testing.
These are the slides used on the Tampere MeeGo meetup on March 15, 2011 and text may not be super clear for those who didn't attend the meetup. You can still download the example and examine it.
User story workflow (eng)
This document outlines Softjourn Inc.'s user story workflow process. It discusses the differences between releases and versions, and the stages a user story goes through: start, progress, and end. Releases group together versions, which contain user stories. User stories go through analysis, development, and testing stages. Test cases are created and stored in the company's Redmine wiki to validate user stories.
[FullStack NYC 2019] Effective Unit Tests for JavaScript
The document discusses code coverage and mutation testing tools for JavaScript. It introduces karma-coverage as a code coverage plugin that can be used with Karma test runner. Traditional code coverage only measures executed code and does not guarantee tests will fail on logic changes. Mutation testing seeds code with faults to evaluate test strength by whether faults are killed by tests. The document demonstrates Stryker, a mutation testing tool for JavaScript that works with popular frameworks and provides test reports. It provides sample URLs and recommends using Stryker with Angular CLI 6.1+.
Test Driven Development Methodology and Philosophy
A technique for building software that guides software development by writing tests. This is the philosophy and state of mind that a developer should change and start following TDD
How to push a react js application in production and sleep better
“Everything fails all the time”. True for every software project, especially for a large and complex JS project. In this session we are gonna explore testing and monitoring techniques to deliver and maintain a ReactJS + Redux application, and at the same time being able to go back to sleep without the fear that everything is gonna explode during the night.
1.qtp basics
QTP supports functional testing of different environments like Windows, web, and .NET. It uses VBScript for scripting and allows normal, analog, and low-level recording. Tests in QTP can be run in normal or fast mode and utilize checkpoints for verification. Key aspects include the test object model, synchronization, and the expert view interface.
Dot all 2019 | Testing with Craft | Giel Tettelar
This document discusses testing Craft applications with Codeception. It covers the basics of unit and functional testing, including the anatomy of a test class and how to run tests. Common assertions and methods for Codeception and Craft are provided. The document recommends testing business logic rather than implementation and provides tips on Craft's own testing framework and starting testing. It also discusses using continuous integration/delivery to run tests automatically and reduce risks of breaking changes.
PHPUnit with Magento
This document introduces unit testing in PHP and Magento. It discusses what unit testing is, why it is important, and how it can help catch bugs and allow code to be refactored more easily. It then introduces PHPUnit as the de facto unit testing framework for PHP. Key PHPUnit techniques like assertions and mocking are covered. Finally, it discusses how the Magento PHPUnit integration extension allows unit testing of Magento code and modules using PHPUnit. Demo code is referenced to illustrate unit testing concepts and techniques.
How to go about testing in React?
Presentation for my talk at the JavaScript Matters meetup organized by Skills Matter on 11/03/2019 in London, UK.
Gatling - Bordeaux JUG
The document discusses the importance of performance and load testing web applications. It defines performance as how fast, robust, and resource-effective a system is. Load testing involves stressing an application with simulated user load to determine its capacity and stability under heavy usage. The document outlines best practices for load testing methodology, tooling, and interpreting results to optimize performance. It promotes using an asynchronous, non-blocking tool like Gatling for efficient, maintainable load testing that provides meaningful reports.
Php Inspections (EA Extended): The Cookbook
This document discusses Php Inspections (EA Extended), a tool for PHP static code analysis. It provides key features like detecting pitfalls, bugs, and performance issues. The document outlines safety prerequisites like unit testing. It provides tips for using the tool like enabling inspections, cleaning up code to match standards, and sharing configurations. It suggests starting with high severity issues and language level migrations. Continuous static code analysis is recommended.
Gatling Performance Workshop
This document provides an overview of Gatling, an open-source load testing tool developed using Scala. It discusses Gatling's focus on web applications, simplicity, high performance, good reports, and easy integration with CI tools. It then covers setting up Gatling, including prerequisites, writing a sample test, and key concepts like scenarios, simulations, and reports.
Embedded Testing 2015
We deal with the impact of applying DevOps practices (infrastructure as code, continuous integration, release and deployment on demand) in the development of embedded projects spanning the full spectrum of mechanics, electronics and software.
Incorporating devops concepts within the regular test flow enables collaboration between engineers of all three disciplines with very fast feedback cycles.
Software is in a position to provide tools and data to electronics/mechanics to verify design decisions while moving forward with the implementation.
Deliverables are provided at any point in time of the development presenting a constant stream of functioning prototypes from the beginning of development while providing an almost seamless transition from 3D printed proof-of-concept using evaluation boards to integrated device.
In the talk we present the basic DevOps principles and concepts and how they map to established procedures like EOL Tests, affect production considerations and ease hardware-software integration.
Олексій Павленко. CONTRACT PROTECTION ON THE FRONTEND SIDE: HOW TO ORGANIZE R...
The document discusses various approaches for performing contract protection on the frontend side such as integration testing, law-driven contract testing, consumer-driven contract testing, and runtime checking. It then focuses on runtime checking, explaining what it is and how it can add an extra step to quality assurance by allowing integration errors to be responded to in real time. Details are provided on Oleksii Pavlenko who is an engineering manager, PhD holder, and former professional basketball player with interests in surfing, snowboarding, and other boardsports.
Testing of React JS app
This document discusses testing React JS applications with tools like Mocha, Enzyme, and Webdriver.io. It covers why writing tests is important, provides examples of unit testing React components with Enzyme, and discusses how to do functional and integration testing with Webdriver.io. The document demonstrates testing architectures, common testing patterns like page objects, and concludes that frontend tests are important and not too costly to implement.
Robot Framework Dos And Don'ts
This presentation demonstrates general guidelines how to create good test cases using Robot Framework. Both good practices and anti-patterns are presented.
The presentation is hosted on GitHub where you can find the original in ODP format: https://github.com/robotframework/DosDontsSlides
Expedia 3x3 presentation
The document describes LinkedIn's 3x3 mobile release process. Key points:
- Release new versions of the LinkedIn app 3 times per day, with a maximum of 3 hours from code commit to member availability.
- This allowed for faster iteration and feedback compared to previous monthly releases.
- The commit pipeline includes code review, static analysis, unit tests, UI tests, and staged releases to alpha and beta testers.
- Ensuring test stability and reliability was a challenge given the fast release cadence. Techniques included stabilizing the testing environment and framework, and improving test quality.
Dev ops presentation
The document provides an introduction to DevOps. It explains that DevOps aims to integrate developers and operations teams to improve collaboration and productivity by automating infrastructure, workflows, and measuring application performance. This addresses issues where development teams faced delays deploying code and operations teams struggled with managing an increasing number of servers. DevOps adopts practices like automating infrastructure configuration and code deployment to enable continuous delivery and fast, reliable releases while allowing development and production environments to be identical.
More Related Content
What's hot
Automating Your Way to Greatness by Combining OutSystems CI/CD With the Power...
Having built-in CI/CD capabilities has always been a core tenet of the OutSystems platform. As customer factories have grown and CI/CD pipelines have become more complex, OutSystems has developed an integration with some of the leading CI/CD DevOps tools in the market, Jenkins, and Azure DevOps to tackle some of the challenges of managing enterprise-grade CI/CD pipelines.
Python Testing Fundamentals
This document provides an overview of the Python unittest module for writing and running automated tests. It discusses how the unittest.TestCase class is used to define test classes with methods named "test_" that contain assertions. The unittest module then handles running the tests and provides features like test organization, discovery of test methods, and integration with other tools.
Unit Testing your React / Redux app (@BucharestJS)
React and Redux took the world by storm. These JavaScript libraries allow you to write applications consisting of reusable components while avoiding bugs related to side-effects. But I suspect that developers do not unit test their React/Redux code. Or at least not as much as they could. During this talk, I will showcase the unit tests we have written for our eventriX product. These tests run fast and cover the most important aspects of our client-side code running in the browser. These practical real-world examples could inspire you to write more and better unit tests for your own React/Redux application.
Testing With OutSystems
This document provides an agenda for a lab on testing with OutSystems. The lab will give an overview of testing with OutSystems, introduce the BDD testing framework and Gherkin language, and include a hands-on portion. Attendees will learn about Behavior Driven Development, the OutSystems Forge Component for BDD, and how to get started using Gherkin through an interactive demo link.
Test driving QML
How to test-drive your Qt QML code. Overview on how you do simple testing, UI level testing, synchronous testing, data-driven testing.
These are the slides used on the Tampere MeeGo meetup on March 15, 2011 and text may not be super clear for those who didn't attend the meetup. You can still download the example and examine it.
User story workflow (eng)
This document outlines Softjourn Inc.'s user story workflow process. It discusses the differences between releases and versions, and the stages a user story goes through: start, progress, and end. Releases group together versions, which contain user stories. User stories go through analysis, development, and testing stages. Test cases are created and stored in the company's Redmine wiki to validate user stories.
[FullStack NYC 2019] Effective Unit Tests for JavaScript
The document discusses code coverage and mutation testing tools for JavaScript. It introduces karma-coverage as a code coverage plugin that can be used with Karma test runner. Traditional code coverage only measures executed code and does not guarantee tests will fail on logic changes. Mutation testing seeds code with faults to evaluate test strength by whether faults are killed by tests. The document demonstrates Stryker, a mutation testing tool for JavaScript that works with popular frameworks and provides test reports. It provides sample URLs and recommends using Stryker with Angular CLI 6.1+.
Test Driven Development Methodology and Philosophy
A technique for building software that guides software development by writing tests. This is the philosophy and state of mind that a developer should change and start following TDD
How to push a react js application in production and sleep better
“Everything fails all the time”. True for every software project, especially for a large and complex JS project. In this session we are gonna explore testing and monitoring techniques to deliver and maintain a ReactJS + Redux application, and at the same time being able to go back to sleep without the fear that everything is gonna explode during the night.
1.qtp basics
QTP supports functional testing of different environments like Windows, web, and .NET. It uses VBScript for scripting and allows normal, analog, and low-level recording. Tests in QTP can be run in normal or fast mode and utilize checkpoints for verification. Key aspects include the test object model, synchronization, and the expert view interface.
Dot all 2019 | Testing with Craft | Giel Tettelar
This document discusses testing Craft applications with Codeception. It covers the basics of unit and functional testing, including the anatomy of a test class and how to run tests. Common assertions and methods for Codeception and Craft are provided. The document recommends testing business logic rather than implementation and provides tips on Craft's own testing framework and starting testing. It also discusses using continuous integration/delivery to run tests automatically and reduce risks of breaking changes.
PHPUnit with Magento
This document introduces unit testing in PHP and Magento. It discusses what unit testing is, why it is important, and how it can help catch bugs and allow code to be refactored more easily. It then introduces PHPUnit as the de facto unit testing framework for PHP. Key PHPUnit techniques like assertions and mocking are covered. Finally, it discusses how the Magento PHPUnit integration extension allows unit testing of Magento code and modules using PHPUnit. Demo code is referenced to illustrate unit testing concepts and techniques.
How to go about testing in React?
Presentation for my talk at the JavaScript Matters meetup organized by Skills Matter on 11/03/2019 in London, UK.
Gatling - Bordeaux JUG
The document discusses the importance of performance and load testing web applications. It defines performance as how fast, robust, and resource-effective a system is. Load testing involves stressing an application with simulated user load to determine its capacity and stability under heavy usage. The document outlines best practices for load testing methodology, tooling, and interpreting results to optimize performance. It promotes using an asynchronous, non-blocking tool like Gatling for efficient, maintainable load testing that provides meaningful reports.
Php Inspections (EA Extended): The Cookbook
This document discusses Php Inspections (EA Extended), a tool for PHP static code analysis. It provides key features like detecting pitfalls, bugs, and performance issues. The document outlines safety prerequisites like unit testing. It provides tips for using the tool like enabling inspections, cleaning up code to match standards, and sharing configurations. It suggests starting with high severity issues and language level migrations. Continuous static code analysis is recommended.
Gatling Performance Workshop
This document provides an overview of Gatling, an open-source load testing tool developed using Scala. It discusses Gatling's focus on web applications, simplicity, high performance, good reports, and easy integration with CI tools. It then covers setting up Gatling, including prerequisites, writing a sample test, and key concepts like scenarios, simulations, and reports.
Embedded Testing 2015
We deal with the impact of applying DevOps practices (infrastructure as code, continuous integration, release and deployment on demand) in the development of embedded projects spanning the full spectrum of mechanics, electronics and software.
Incorporating devops concepts within the regular test flow enables collaboration between engineers of all three disciplines with very fast feedback cycles.
Software is in a position to provide tools and data to electronics/mechanics to verify design decisions while moving forward with the implementation.
Deliverables are provided at any point in time of the development presenting a constant stream of functioning prototypes from the beginning of development while providing an almost seamless transition from 3D printed proof-of-concept using evaluation boards to integrated device.
In the talk we present the basic DevOps principles and concepts and how they map to established procedures like EOL Tests, affect production considerations and ease hardware-software integration.
Олексій Павленко. CONTRACT PROTECTION ON THE FRONTEND SIDE: HOW TO ORGANIZE R...
The document discusses various approaches for performing contract protection on the frontend side such as integration testing, law-driven contract testing, consumer-driven contract testing, and runtime checking. It then focuses on runtime checking, explaining what it is and how it can add an extra step to quality assurance by allowing integration errors to be responded to in real time. Details are provided on Oleksii Pavlenko who is an engineering manager, PhD holder, and former professional basketball player with interests in surfing, snowboarding, and other boardsports.
Testing of React JS app
This document discusses testing React JS applications with tools like Mocha, Enzyme, and Webdriver.io. It covers why writing tests is important, provides examples of unit testing React components with Enzyme, and discusses how to do functional and integration testing with Webdriver.io. The document demonstrates testing architectures, common testing patterns like page objects, and concludes that frontend tests are important and not too costly to implement.
Robot Framework Dos And Don'ts
This presentation demonstrates general guidelines how to create good test cases using Robot Framework. Both good practices and anti-patterns are presented.
The presentation is hosted on GitHub where you can find the original in ODP format: https://github.com/robotframework/DosDontsSlides
What's hot (20)
Automating Your Way to Greatness by Combining OutSystems CI/CD With the Power...
Automating Your Way to Greatness by Combining OutSystems CI/CD With the Power...
Unit Testing your React / Redux app (@BucharestJS)
Unit Testing your React / Redux app (@BucharestJS)
[FullStack NYC 2019] Effective Unit Tests for JavaScript
[FullStack NYC 2019] Effective Unit Tests for JavaScript
Test Driven Development Methodology and Philosophy
Test Driven Development Methodology and Philosophy
How to push a react js application in production and sleep better
How to push a react js application in production and sleep better
Олексій Павленко. CONTRACT PROTECTION ON THE FRONTEND SIDE: HOW TO ORGANIZE R...
Олексій Павленко. CONTRACT PROTECTION ON THE FRONTEND SIDE: HOW TO ORGANIZE R...
Similar to 100 tests per second - 40 releases per week
Expedia 3x3 presentation
The document describes LinkedIn's 3x3 mobile release process. Key points:
- Release new versions of the LinkedIn app 3 times per day, with a maximum of 3 hours from code commit to member availability.
- This allowed for faster iteration and feedback compared to previous monthly releases.
- The commit pipeline includes code review, static analysis, unit tests, UI tests, and staged releases to alpha and beta testers.
- Ensuring test stability and reliability was a challenge given the fast release cadence. Techniques included stabilizing the testing environment and framework, and improving test quality.
Dev ops presentation
The document provides an introduction to DevOps. It explains that DevOps aims to integrate developers and operations teams to improve collaboration and productivity by automating infrastructure, workflows, and measuring application performance. This addresses issues where development teams faced delays deploying code and operations teams struggled with managing an increasing number of servers. DevOps adopts practices like automating infrastructure configuration and code deployment to enable continuous delivery and fast, reliable releases while allowing development and production environments to be identical.
Testing in a continuous delivery environment
Talk at Iqnite conference for software quality and testing about how we have do continuous delivery at here.com
Together with Siddharth Somasundaram
http://www.iqnite-conferences.com/suisse/programme/programme.aspx
IFG for SAP Integration, webinar on Automated Testing
This is the presentation from the IFG webinar about Automating the testing of SAP Interfaces.
We are showing why testing, is really important and we are standing in a place where it really makes a lot of sense to automate the testing in a lot shorter time frame.
From 10 Deploys Per Year to 4 Per Day at DBS Bank: How Pivotal Platform Can R...
SpringOne Platform 2019
Session Title: From 10 Deploys Per Year to 4 Per Day at DBS Bank: How Pivotal Platform Can Reduce Operational Toil
Speaker: Shaun Norris, Field CIO, APJ, Pivota
Youtube: https://youtu.be/iqYg9EfUvoI
Release & Iterate Faster: Stop Manual Testing
The document discusses LinkedIn's "3x3" approach to software development, which aims to release code three times per day within three hours of a code commit. It outlines the challenges with their previous release process and describes how they implemented continuous integration, automated testing, and distribution methods to achieve much faster release cycles. Key aspects included static analysis, unit testing, automated UI testing across emulators in parallel, and distributing builds to alpha, beta, and production channels on Google Play. The approach enabled LinkedIn to release code over 130 times per year and get feedback from users much more quickly.
Dev ops
The document provides an introduction to DevOps, which promotes collaboration between development and operations teams. It discusses models used before DevOps, including the waterfall model and agile methodology. While agile methodology improved on waterfall by allowing for continuous development and testing, a lack of collaboration between teams remained an issue. DevOps aims to address this by having development and operations engineers work together throughout the entire lifecycle from design to deployment. This is intended to result in faster delivery of features to customers while also improving stability. The document outlines the DevOps lifecycle from continuous development to continuous monitoring.
3x3 Speeding Up Mobile Releases
Presenters: Drew Hannay - Staff Software Engineer at LinkedIn
Presented on Mar 21 at 10:30am at Mobile Delivery Days 2016
Continuous integration is old hat in the web frontend and backend world, but it’s still rare for native mobile apps. For true continuous integration, we ship every commit directly to production – but this is clearly not realistic in the world of native apps, where binaries must be published in the App Store (with Apple’s week-long review process) and Google Play, then downloaded by members.
On the engineering side, we needed an aggressive goal to ensure we didn’t fall back into the pattern of manual verification of each release. We also wanted our product partners to be free to ship as often as they want (without annoying members of course!). We settled on a rule that we call “3x3”.
3x3: Speeding Up Mobile Releases
The document discusses LinkedIn's transition to a 3x3 release cycle for their flagship mobile app, releasing new versions every three hours. Previously they released monthly. The new process involves continuous integration pipelines for code review, static analysis, unit testing, and UI testing on alpha and beta builds. Tests are automated and run in parallel on emulators to speed the process. Partner teams now validate through automation. Risk is minimized through feature flags and A/B testing. Areas for future improvement include further automating the release process and adding performance testing.
Accelerate User Driven Innovation [Webinar]
https://info.dynatrace.com/apm_dtm_ops_17q4_wc_accelerate_user_driven_innovation_en_registration.html
Accelerate User Driven Innovation [Webinar]
DevOps adopters are more agile, more reliable and more successful but, only 2% of companies worldwide have adopted DevOps best practices.
We know it’s more difficult for enterprises companies with legacy systems and processes to get started but it isn’t impossible.
To help you accelerate your own DevOps journey & realise some of the benefits, we’re thrilled to be hosting international DevOps experts Andreas Grabner, Mark Tomlinson and James Pulley.
With combined experience across hundreds of DevOps deployments they have some remarkable use cases to share including Verizon, and even our own story of transforming from on premise six month waterfall deployment to a cloud native one hour continuous delivery model.
Don’t miss these amazing insights. Register today!
Develop, deploy, and operate services at reddit scale oscon 2018
The last few years have been a period of tremendous growth for Reddit. Process, tooling, and culture have all had to adapt to an organization that has tripled in size and ambition. Greg Taylor discusses Reddit's evolution and explains how one of the world’s busiest sites develops, deploys, and operates services at significant scale.
Presented at OSCON 2018 in Portland, Oregon
Deccan ruby-conf-talk
1. The document discusses CRUDActions, a Ruby on Rails module created by the speaker to optimize API development by reducing duplication across controllers and allowing APIs to be highly flexible and dynamic.
2. CRUDActions handles common CRUD actions as well as search, sorting, counting, includes/excludes, and joins to optimize API development and make applying global changes easier.
3. While CRUDActions speeds up API development and creates highly optimized APIs, any changes to the module could affect all APIs, and additional testing and documentation is needed to implement it fully.
How To Transform the Manual Testing Process to Incorporate Test Automation
Although most testing organizations have some automation, it's usually a subset of their overall testing efforts. Typically the processes have been previously defined, and the automation team must adapt accordingly. The major issue is that test automation work and deliverables do not always fit into a defined manual testing process.
Learn how to transform your manual testing procedures and how to incorporate test automation into your overall testing process.
Apache Cassandra at Target - Cassandra Summit 2014
Pioneering NoSQL in a Big Enterprise. The problems we needed to solve, the journey we took to get there, and the lessons we learned along the way.
Why Test SAP PI/PO after any upgrade
In this presentation, you will see some of the problems SAP PI/PO upgrades, Support Packs, and Patches. You will learn some of the problems about applying them and how to get it fixed.
The best way to ensure you are testing it is to use an automated tool to setup the test cases and run them.
There is a demo on using Figaf IRT to setup the tests in it.
You can try the tool self at https://figaf.com/IRT
QA Best Practices in Agile World_new
The document discusses QA best practices in an Agile development environment. It describes key aspects of Agile like iterative delivery, self-organizing teams, and rapid feedback. It addresses challenges of fitting QA into short iterations and questions around testing approaches. The document advocates for testing to be collaborative, automated, and continuous throughout development. It provides recommendations for QA roles in activities like planning, stand-ups, retrospectives and acceptance testing. Overall it promotes testing practices in Agile that focus on early feedback, automation, and involvement of QA throughout the development process.
Road to Continuous Delivery - Wix.com
The document discusses Aviran Mordo's presentation on Wix's journey towards continuous delivery. Some key points:
- Wix has transitioned from traditional waterfall development to continuous delivery, deploying changes around 60 times per day.
- This was enabled by adopting DevOps practices like test-driven development, feature toggles, A/B testing, automated deployments, and monitoring.
- Tools like App-Info, New Relic, and custom deployment tools were crucial for implementing continuous delivery at Wix's scale across multiple data centers and cloud providers.
- Transitioning required cultural changes, empowering developers, and embracing risk and failure to improve continuously. Wix now develops and replaces infrastructure
DevOps for TYPO3 Teams and Projects
The document discusses DevOps practices for TYPO3 projects. It defines DevOps as the confluence of development and operations. It highlights the importance of communication between different roles like developers, system administrators, and integrators. It also provides examples of tools and techniques that can be used at different stages of a TYPO3 project to facilitate DevOps practices, such as automated testing, deployment automation, and content synchronization.
Time logger
Time Logger is an employee management system that keeps all the report of all the employees working in the project has completed or running.
Gatling
These slides will give you brief discription about issues with the traditional performance testing tools and how the gatling resolve issues?
Similar to 100 tests per second - 40 releases per week (20)
IFG for SAP Integration, webinar on Automated Testing
IFG for SAP Integration, webinar on Automated Testing
From 10 Deploys Per Year to 4 Per Day at DBS Bank: How Pivotal Platform Can R...
From 10 Deploys Per Year to 4 Per Day at DBS Bank: How Pivotal Platform Can R...
Develop, deploy, and operate services at reddit scale oscon 2018
Develop, deploy, and operate services at reddit scale oscon 2018
How To Transform the Manual Testing Process to Incorporate Test Automation
How To Transform the Manual Testing Process to Incorporate Test Automation
Apache Cassandra at Target - Cassandra Summit 2014
Apache Cassandra at Target - Cassandra Summit 2014
More from Lars Thorup
SQL or NoSQL - how to choose
The past years, a number of new database systems have appeared, like MongoDB and Redis. Most of them have radically new ways to look at data persistance, where efficient replication is prioritized over advanced query support.
In this talk we will discuss some of the benefits and drawbacks of the new key/value stores and document databases. As an example, we will demonstrate Redis, an advanced key/value store. Redis is different from most other key/value stores on two dimensions: It runs entirely in RAM and it supports a number of advanced data structures with accompanying specialized algorithms.
Super fast end-to-end-tests
Automated end-to-end tests are often seen as a necessary evil. A common example is Selenium-based browser tests. This kind of testing has many drawbacks: 1) They take a long time to run. 2) They require complicated setup. 3) They are fragile. But it doesn't have to be like that!
In this talk I describe how we can write automated end-to-end tests that are 1) Superfast. 2) As easy to setup as unit tests. 3) As robust as unit tests.
This technique is leveraging existing unit testing techniques. Tests for lower layers (such as server code) is instrumented to record all requests and responses in a log file. Tests for higher layers (like client code) is extended with an mocking layer that automatically configures with the contents of that log file.
It is then possible to run a almost a hundred end-to-end tests every second.
Extreme Programming - to the next-level
This document discusses taking extreme programming principles to the next level by turning traditional practices "up to 11". It explores several ideas for achieving faster feedback including mob programming, continuous deployment, hypothesis-driven user stories, shared product ownership, monitoring-driven development, and continuous learning. The author asks the reader to consider which ideas may work to implement in their organization this month.
Advanced Javascript Unit Testing
This document summarizes best practices for JavaScript unit testing presented by Lars Thorup. It discusses how to test asynchronous code using callbacks and promises, fake timers to test delayed behavior, mock the DOM and AJAX requests, enable cross-browser testing using Karma, and detect memory leaks between tests. Lars Thorup is a software developer who focuses on JavaScript, TDD, and continuous integration.
Unit testing legacy code
Unit testing and test-driven development are practices that makes it easy and efficient to create well-structured and well-working code. However, many software projects didn't create unit tests from the beginning.
In this presentation I will show a test automation strategy that works well for legacy code, and how to implement such a strategy on a project. The strategy focuses on characterization tests and refactoring, and the slides contain a detailed example of how to carry through a major refactoring in many tiny steps
Advanced QUnit - Front-End JavaScript Unit Testing
Code: https://github.com/larsthorup/qunit-demo-advanced
Unit testing front-end JavaScript presents its own unique set of challenges. In this session we will look at number of different techniques to tackle these challenges and make our JavaScript unit tests fast and robust. We plan to cover the following subjects:
* Mocking and spy techniques to avoid dependencies on
- Functions, methods and constructor functions
- Time (new Date())
- Timers (setTimeout, setInterval)
- Ajax requests
- The DOM
- Events
* Structuring tests for reuse and readability
* Testing browser-specific behaviour
* Leak testing
Put "fast" back in "fast feedback"
One of the cornerstones in Agile development is fast feedback. For engineering, "fast" means "instantly" or "in 5 minutes", not "tomorrow" or "this week". Your engineering practices should ensure that you can answer yes to most of the following questions:
- Do we get all test results in less than 5 minutes after a commit?
- Is our code coverage more than 75% for both front-end and back-end?
- Can we start exploratory testing in less than 15 minutes after a commit?
- Do all our tests pass more than 90% of our commits?
This talk will give you practical advice on how to get to "yes, we get fast feedback".
Database Schema Evolution
Streamline your database changes by versioning your database instances and your database schema, running database instances locally and implementing database changes using migration scripts based on database refactoring patterns.
Advanced Jasmine - Front-End JavaScript Unit Testing
This document discusses advanced techniques for front-end JavaScript unit testing using Jasmine, including mocking methods, constructors, timers, and AJX requests to test code in isolation without dependencies and speed up tests. It also covers spying on events, simulating CSS transitions, using custom matchers, structuring test code, and browser-specific testing. The presenter is Lars Thorup, a software developer and coach who founded ZeaLake and teaches agile and automated testing.
Javascript unit testing with QUnit and Sinon
This document discusses JavaScript unit testing with QUnit and Sinon. It introduces Lars Thorup and his background in software development, testing, and coaching. It then provides an overview of unit testing, explaining why it is beneficial and how to implement it. Finally, it demonstrates various QUnit and Sinon techniques for writing tests, including assertions, spies, stubs, mocks, asynchronous code, the DOM, and advanced mocking.
Continuous Integration for front-end JavaScript
Simple demo on setting up continuous integration with GruntJS and PhantomJS of your front-end JavaScript code and Jasmine tests running on Jenkins
Automated Performance Testing
If you are like most test driven developers, you write automated tests for your software to get fast feedback about potential problems. Most of the tests you write will verify the functional behaviour of the software: When we call this function or press this button, the expected result is that value or that message.
But what about the non-functional behaviour, such as performance: When we perform this query the expected speed of getting results should be no more than that many milliseconds. It is important to be able to write automated performance tests as well, because they can give us early feedback about potential performance problems. But expected performance is not as clear-cut as expected results. Expected results are either correct or wrong. Expected performance is more like a threshold: If the performance is worse than this, we want the test to fail.
Test and Behaviour Driven Development (TDD/BDD)
In this introduction to Test Driven Development (TDD) or Behaviour Driven Development (BDD) we give a high level description of what it is and why it is useful for developers. Then we go into some details on stubs and mocks, test data, UI testing, SQL testing, JavaScript testing, web services testing and how to start doing TDD/BDD on an existing code base.
Agile Contracts
How do you sell an agile project? Most clients expect to buy software by time-and-material or by fixed-price-fixed scope contracts based on detailed requirements. These models cannot create a fertile environment for collaboration between client and vendor.
In this presentation, we report on our experiments with commercial contracts that supports an agile development process, based on concrete examples of win-win contract types. We will outline the different aspects of these contracts, as well as experiences creating and delivering software solutions under these contracts.
High Performance Software Engineering Teams
Based on my experiences building high performance engineering teams, this presentation focuses on the technical practices required. These practices centers around automation (build, test and deployment) and increased collaboration between Engineering and QA (TDD, exploratory testing, prioritization, feedback cycles).
Elephant Carpaccio
Here are some tips for breaking down work in an agile way:
- Focus on delivering value to users. Each story and task should provide some value.
- Iterate frequently. Stories and tasks should be small enough that you can complete and release them within a sprint or two.
- Get early feedback. Small slices allow testing work sooner and adjusting based on feedback.
- Prioritize flexibility. Small slices give you options to reorder or drop work as priorities change.
- Estimate costs accurately. Tasks should take 1-5 days; if longer, may need refactoring. Consider spikes for technical challenges.
- Refactor when repetitive. If work is very similar, look for ways to simplify through ref
Unit Testing in JavaScript with MVC and QUnit
Lars Thorup presents on unit testing JavaScript applications with the MVC pattern and QUnit testing framework. He discusses testing views, controllers, models, and services. The document recommends setting up tests for each component in isolation by injecting stubs for their dependencies. Asynchronous testing is also covered, including techniques like stopping/starting to synchronize async calls in tests. The MVC pattern with dependency injection is advocated to make the code more modular and testable.
Introduction to Automated Testing
Learn about the benefits of writing unit tests. You will spend less time fixing bugs and you will get a better design for your software. Some of the questions answered are:
Why should I, as a developer, write tests?
How can I improve the software design by writing tests?
How can I save time, by spending time writing tests?
When should I write unit tests and when should I write system tests?
More from Lars Thorup (18)
Advanced QUnit - Front-End JavaScript Unit Testing
Advanced QUnit - Front-End JavaScript Unit Testing
Advanced Jasmine - Front-End JavaScript Unit Testing
Advanced Jasmine - Front-End JavaScript Unit Testing
Recently uploaded
Unveiling the Advantages of Agile Software Development.pdf
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
What next after learning python programming basics
What next after learning python programming basics
Webinar On-Demand: Using Flutter for Embedded
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
How to write a program in any programming language
How to write a program in any programming language
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
Presented at NLJUG's J-Spring 2024.
一比一原版(USF毕业证)旧金山大学毕业证如何办理
USF硕士毕业证成绩单【微信95270640】一比一伪造旧金山大学文凭@假冒USF毕业证成绩单+Q微信95270640办理USF学位证书@仿造USF毕业文凭证书@购买旧金山大学毕业证成绩单USF真实使馆认证/真实留信认证回国人员证明
#一整套旧金山大学文凭证件办理#—包含旧金山大学旧金山大学本科毕业证成绩单学历认证|使馆认证|归国人员证明|教育部认证|留信网认证永远存档教育部学历学位认证查询办理国外文凭国外学历学位认证#我们提供全套办理服务。
一整套留学文凭证件服务：
一：旧金山大学旧金山大学本科毕业证成绩单毕业证 #成绩单等全套材料从防伪到印刷水印底纹到钢印烫金
二：真实使馆认证（留学人员回国证明）使馆存档
三：真实教育部认证教育部存档教育部留服网站永久可查
四：留信认证留学生信息网站永久可查
国外毕业证学位证成绩单办理方法：
1客户提供办理旧金山大学旧金山大学本科毕业证成绩单信息：姓名生日专业学位毕业时间等（如信息不确定可以咨询顾问：我们有专业老师帮你查询）；
2开始安排制作毕业证成绩单电子图；
3毕业证成绩单电子版做好以后发送给您确认；
4毕业证成绩单电子版您确认信息无误之后安排制作成品；
5成品做好拍照或者视频给您确认；
6快递给客户（国内顺丰国外DHLUPS等快读邮寄）。
教育部文凭学历认证认证的用途：
如果您计划在国内发展那么办理国内教育部认证是必不可少的。事业性用人单位如银行国企公务员在您应聘时都会需要您提供这个认证。其他私营 #外企企业无需提供！办理教育部认证所需资料众多且烦琐所有材料您都必须提供原件我们凭借丰富的经验帮您快速整合材料让您少走弯路。
实体公司专业为您服务如有需要请联系我: 微信95270640奈一次次令他失望山娃今年岁上五年级识得很多字从走出小屋开始山娃就知道父亲的家和工地共有一个很动听的名字——天河工地的底层空空荡荡很宽阔很凉爽在地上铺上报纸和水泥袋父亲和工人们中午全睡在地上地面坑坑洼洼山娃曾多次绊倒过也曾有长铁钉穿透凉鞋刺在脚板上但山娃不怕工地上也常有五六个从乡下来的小学生他们的父母亲也是高楼上的建筑工人小伙伴来自不同省份都操着带有浓重口音的普通话可不知为啥山娃不仅很快与他们熟识了
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Top 9 Trends in Cybersecurity for 2024.pptx
Security and risk management (SRM) leaders face disruptions on technological, organizational, and human fronts. Preparation and pragmatic execution are key for dealing with these disruptions and providing the right cybersecurity program.
E-commerce Development Services- Hornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Using Xen Hypervisor for Functional Safety
An update on making Xen hypervisor functionally safe and enhancing its usage in automotive and industrial use cases
zOS Mainframe JES2-JES3 JCL-JECL Differences
Document which explains the difference between Jes2 and Jes3
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
Malibou Pitch Deck For Its €3M Seed Round
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Presentation from Ghazal Aakel and Eric Jochum at the GSD Community Stage Meetup on June 6th, 2024
Mobile app Development Services | Drona Infotech
Drona Infotech is one of the Best Mobile App Development Company In Noida Maintenance and ongoing support. mobile app development Services can help you maintain and support your app after it has been launched. This includes fixing bugs, adding new features, and keeping your app up-to-date with the latest
Visit Us For :
UI5con 2024 - Bring Your Own Design System
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
Oracle 23c New Features For DBAs and Developers.pptx
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
一比一原版(UMN毕业证)明尼苏达大学毕业证如何办理
UMN硕士毕业证成绩单【微信95270640】购买（明尼苏达大学毕业证成绩单硕士学历）Q微信95270640代办UMN学历认证留信网伪造明尼苏达大学学位证书精仿明尼苏达大学本科/硕士文凭证书补办明尼苏达大学 diplomaoffer,Transcript购买明尼苏达大学毕业证成绩单购买UMN假毕业证学位证书购买伪造明尼苏达大学文凭证书学位证书,专业办理雅思、托福成绩单，学生ID卡，在读证明，海外各大学offer录取通知书，毕业证书，成绩单，文凭等材料:1:1完美还原毕业证、offer录取通知书、学生卡等各种在读或毕业材料的防伪工艺（包括 烫金、烫银、钢印、底纹、凹凸版、水印、防伪光标、热敏防伪、文字图案浮雕，激光镭射，紫外荧光，温感光标）学校原版上有的工艺我们一样不会少，不论是老版本还是最新版本，都能保证最高程度还原，力争完美以求让所有同学都能享受到完美的品质服务。
#毕业证成绩单 #毕业証 #成绩单 #學生卡 #OFFER录取通知书 #雅思#托福等……
国外大学明尼苏达大学明尼苏达大学毕业证offer制作方法（一对一专业服务）
1客户提供办理信息：姓名生日专业学位毕业时间等（如信息不确定可以咨询顾问：我们有专业老师帮你查询）；
2开始安排制作毕业证成绩单电子图；
3毕业证成绩单电子版做好以后发送给您确认；
4毕业证成绩单电子版您确认信息无误之后安排制作成品；
5成品做好拍照或者视频给您确认；
6快递给客户（国内顺丰国外DHLUPS等快读邮寄）
— — 制作工艺 【高仿真】— —
凭借多年的制作经验本公司制作明尼苏达大学明尼苏达大学毕业证offer《激光》《水印》《钢印》《烫金》《紫外线》凹凸版uv版等防伪技术一流高精仿度几乎跟学校100%相同！让您绝对满意。
— — -公司理念 【诚信为主】— — —
我們以質量求生存.以服务求发展有雄厚的实力专业的团队咨询顾问为您细心解答可详谈是真是假眼见为实让您真正放心平凡人生,尽我所能助您一臂之力让我們携手圆您梦想!
此贴长年有效【贴心专线/微-信: 95270640】敬请保留此联系方式以备用！如有不在线请给我们留言！我们将在第一时间给您回复!上散发着一抹抹的光晕而这每处自然形成的细节融合在一起浑然天成的美实在令人心生愉悦小道的周边无秩序的生长着几株艳丽的野花红的粉的紫的虽混乱无章却给这幅美景更增添一份性感夹杂着一份纯洁的妖娆毫无违和感实在给人带来一份悠然幸福的心情如果说现在的审美已经断然拒绝了无声的话那么在树林间飞掠而过的小鸟叽叽咋咋的叫声是否就是这最后的点睛之笔悠然走在林间的小路上宁静与清香一丝丝的盛夏气息吸入身体昔日生活里的繁忙多
Recently uploaded (20)
Unveiling the Advantages of Agile Software Development.pdf
Unveiling the Advantages of Agile Software Development.pdf
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
What next after learning python programming basics
What next after learning python programming basics
How to write a program in any programming language
How to write a program in any programming language
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Oracle 23c New Features For DBAs and Developers.pptx
Oracle 23c New Features For DBAs and Developers.pptx
100 tests per second - 40 releases per week
- 1. 100 tests per second - 40 releases per week Lars Thorup, Triggerz April, 2018
- 2. Let's deploy a new feature!
- 3. Lars Thorup | Triggerz ● Lars ● MSc comp. science ● Developer, coach ● CTO, co-founder of Triggerz ● @larsthorup ● Triggerz ● Employee training ● Recommendation engine ● SaaS ● Started in 2016 ● 3 corporate clients live ● 1800 users ● www.triggerz.com
- 5. Code stack ● Browser ● React ● Redux ● App-server ● Node.js ● Restify ● Knex ● Database ● PostgreSQL
- 6. 100 tests per second Note: these are our slow integration tests for the front-end; we also have fast unit tests :)
- 7. 20-40 releases per week
- 8. Our experience with continuous delivery ● Costs ● More up-front investment in tests and automation ● More discipline required ● Deployment pausing requires manual intervention ● Changes ● Continuous but smaller stress over not breaking production ● Benefits ● Developer feedback is faster ● We can reprioritize frequently ● Users get new functionality much faster ● Production issues are few, small and quickly fixed ● Deploying becomes trivial
- 10. Feature toggles ● Disable and deploy unfinished feature to production ● Fast integration ● Fast feedback https://admin.triggerz.com/#feature:ageUserLocation=true
- 11. Next ● Zero-downtime ● More than one app server ● Rolling upgrades ● Service coordination (locks, serializable transaction isolation) ● Custom CSS packs ● Custom values of our CSS variables ● Webpack-step per custom pack
- 12. Did we deploy the new feature?