• Liked Puneet Khanduri
    keyboard_arrow_down

    Diffy : Catching bugs without writing tests

    Puneet Khanduri
    Puneet Khanduri
    schedule 3 months ago
    Sold Out!
    45 mins
    Demonstration
    Beginner

    Diffy is a tool used at Twitter to automatically catch regressions in our backend services before they are deployed to production.

    Diffy is open source and has been adopted into modern continuos deploy workflows by the larger community.

    This talk will cover the fundamental concepts behind Diffy and how its automation helps achieve peace of mind for service owners, devops, and QA folks.

  • Liked Pooja Shah
    keyboard_arrow_down

    Release Status Analyser to bring more agility @ work

    Pooja Shah
    Pooja Shah
    schedule 4 months ago
    Sold Out!
    20 mins
    Demonstration
    Advanced

    Problem Statement

    Do you have a lot of automated Tests and so the lot many tests reports to analyse before taking call for release?

    Plot: Any huge impacting micro-service based product/project for which enormous tests have been already automated and your continuous deployment process requires all of those tests in "PASSED" state. Due to high traffic most of the day, releases are deployed at non peak hours. Imagine decided deployment time in production is 5 AM. (The feature and regression testing is done already but there are always some small last minute changes, so it’s better to have a double check on the frozen code to release)

    At 1 am: Final automated sanity checks start executing  

    At 3 am: Get the results, release engineer/ devOps gets notified of the state of the release, she/he looks at CI board and see several green and red builds. He/She now 1 by 1 opens all red builds, clicks on individual reports, console, screenshots....  more red builds- more time to analyse it...

    At 4.30 am: After gathering report on which test failed for what reason & who should be looking at them, she/he calls up respective owners to look out and state the reasons & take a call on the release

    At 5 am: The service owner says "let’s revert my feature to previous version and take the release live"

    Release Engineer again starts searching for files/mails where the last stable version is stored, spending more time again. It’s 6 AM now, she/ he deploys last stable service versions, runs the failed tests -> integration tests ...

    it already 9 AM, wooosh!, time runs really fast. Can't release now, peak traffic time.............

    Do you share the same pain?

    Before giving a +1 for the release, it becomes essential for the QA folks to provide proper feedback as quickly as possible. At the same time assessing n number of reports becomes an additional tedious task. So definitely there should be 1 dashboard which nicely displays the status with transparency and anyone should be able to tell whether release is good to go and if not, then why not. RSA which I have created on top of open-sourced technologies is a small effort towards achieving the same. Will take you through a live demo and discuss on how you can use it to meet your needs.

  • Liked David Laribee
    keyboard_arrow_down

    Testing Strategy: New Model, Better Outcome

    David Laribee
    David Laribee
    schedule 3 months ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Pyramids? Quadrants? Cupcakes?! There are a wide array of models that describe approaches to test automation strategy and their possible positive (or negative) outcomes.

    In this talk, we’ll survey the landscape of testing models: models that range from technical to product to cultural mindsets, including best practices and anti-patterns. I’ll add detail and nuance to each of these models in the form of professional experience, real world example, and case study. 

    With a new lens, focusing on testing strategy as an act of curation, I'll share a new approach to evolving a testing strategy appropriate for your product development team's specific context.

  • Liked Narayan Raman
    keyboard_arrow_down

    UI Automation Success: Keeping Pace with Product Evolution

    Narayan Raman
    Narayan Raman
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Team A's application is evolving fast. Team B is switching UI frameworks (jQuery to Angular). Team C is migrating an applet application to web. Team D is extending a web app to mobile. Can automation help in the following scenarios? Ideally it should.

    When applications evolve, test automation code starts failing. If tests are not fixed quickly, automation code becomes stale and the whole suite becomes unusable.

    Changes to applications follow specific patterns. Knowing these patterns helps create automation frameworks which can handle them easily. In this talk, through live examples, we will see various ways in which web applications evolve, how they break automation code, and how we can structure the automation code such that there is minimal change required to accommodate changes.

  • Liked Julian Harty
    keyboard_arrow_down

    Does software testing need to be this way? Tools, approaches and techniques to test more effectively

    Julian Harty
    Julian Harty
    schedule 3 months ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Software development teams recognise testing is relevant and important. Testers want to add value and do purposeful and meaningful work, however software automation is encroaching and in some cases obviating much of the hand-crafted tests - including some of the 'automated tests' created by teams. As Nicholas Carr says in his book The Glass Cage: "Who needs humans anyway?"

    And yet, humans - people - have much to contribute to crafting excellent software, including testing the software. This presentation investigates:

    • leading automation techniques to understand more of what they can offer us in terms of testing our software.
    • how structured testing techniques can help all testers including "exploratory testers"
    • where analytics can help
    • tools, approaches and techniques to help test more effectively
  • David Laribee
    David Laribee
    schedule 3 months ago
    Sold Out!
    480 mins
    Workshop
    Intermediate

    In the early 2000s, eXtreme Programming (XP) introduced agility to software engineers. Contemporary cultural and technical innovations - container technology, distributed version control systems, the proliferation of free and open source software, and the DevOps movement - have significantly expanded our possibilities.

    In this one day, hands-on workshop, we’ll build a modern continuous deployment pipeline based on Git, Jenkins, and Docker. Starting with continuous integration, we’ll practice Git workflows enabling parallel development with pull requests and explicit dependency management through the use of forked repositories. We’ll then extend the ecosystem to support ad-hoc testing environments, multi-versioned deployments, and build promotion. We’ll survey tools and techniques for production deployments touching on Docker Swarm, Google Kubernetes, ChatOps, and emerging tools used in serverless architectures such as Amazon Lambda.

    While technologies change, values and principles continue to guide our choices. We’ll end with reflection and a guided discussion on how core XP values - simplicity, feedback, communication, courage - can serve as a compass for environmental and workflow decisions that impact our customers and teammates.

Sorry, no proposals found under this section.