In the agile world, it's important to remember that planning and documentation is still important and serves a purpose. While agile promotes “working software over comprehensive documentation,” it doesn’t say ignore documentation as much as we’d all often like to think. When developing a working DevOps pipeline, it is important to understand what your quality gates are, what thresholds you expect, and where you expect these to be. A well documented test plan should inform the pipeline, and provide information and details as to what constitutes a working code. Too often this DevOps work is done out of sync with Testers, which then either means quality definitions don't line up, or additional re-work has to be put in to align software confidence goals.

 
3 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Introduction
  • SMART Objectives
  • Modeling the Pipeline
  • Quality Thresholds
  • Wrap Up

Learning Outcome

After sitting through this talk, students will understand the importance of documenting specific quality gates and defined thresholds for use in their DevOps work. They will have a good idea of specifically what to call out, how to generate this information, and the importance of working closely with the DevOps team to ensure that high quality software is continuously being deployed, instead of just rapid software.

Target Audience

Test/QA Managers, Testers, DevOps Engineers

schedule Submitted 2 weeks ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Max Saperstone
    keyboard_arrow_down

    Exploring Automation Strategies and Frameworks What Should Your Team Be Using?

    Max Saperstone
    Max Saperstone
    schedule 2 weeks ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Agile practices have done a magnificent job of speeding up the software development process. Unfortunately, simply applying agile practices to testing isn't enough to keep testers at the same pace. Test automation is necessary to support agile delivery. Max Saperstone explores popular test automation frameworks and shares the benefits of applying these frameworks, their implementation strategies, and best usage practices. Focusing on the pros and cons of each framework, Max discusses data-driven, keyword-driven, and action-driven approaches. Find out which framework and automation strategy are most beneficial for specific situations. Although this presentation is tool agnostic, Max demonstrates automation with examples from current tooling options. If you are new to test automation or trying to optimize your current automation strategy, this session is for you.

     

  • Liked Max Saperstone
    keyboard_arrow_down

    Testing with a Rooted Mobile Device

    Max Saperstone
    Max Saperstone
    schedule 2 weeks ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Traditional applications are tested through the GUI and through all exposed APIs. However, typical mobile app testing is only done through the front-end GUI. In addition, performance and security details are not readily available from the mobile device. Max Saperstone demonstrates some benefits of testing a native mobile application on a rooted device—one with privileged access control. Although Max does not describe how to root a device, he shares how to access back-end processes and test at this detailed level. He discusses the technical controls made available through a rooted device—together with its auditing, logging, and monitoring—and describes the gathering of additional metrics. Max demonstrates tools for penetration testing, sniffing, and network hacking; shares how to access application data directly; and shows how data security is implemented for the application. Learn how to use the admin rights associated with a rooted device to examine device performance and to simulate interrupts and system faults.