Over the recent years, agile teams have started practicing the shift left test approach to speed up their product deliveries and remove testing bottlenecks. Often teams tend to shift functional testing to the left of delivery cycle addressing the cross functional requirements(CFR) tests at the end.

The functional requirements of the product defines the behaviour of the system whereas the Cross-Functional Requirements(CFRs) define the operational attributes of the system like performance, availability, reliability, usability, accessibility, audit, logging, recoverability, user volume, security, localisation, etc.

Consider a case where an online retail application has launched its big sale days with exceptionally great deals, triggering the enthusiasm of millions of users to access the application at the same time. The moment the big sale started, the website received a peak load from its users. Unable to withstand the load, the application was inaccessible until a suitable fix was done by the engineering team. Would this make the customers happy with online shopping experience? How many people would stay in the application until it’s up again? Would they shop in the application if this repeats?  If CFRs had been tested effectively with proper focus, we could avoid facing this situation of losing hundreds of customers.

This session talks about the importance and need to shift CFR tests to the left of delivery cycle for high confident and quality releases. It gives step by step explanation of shift left process and practices that helps build CFRs into the product right from project kickoff till delivery along with an example case study.

 
 

Outline/Structure of the Talk

  • Introduction to Shift Left (3 mins)
  • Quick introduction to CFRs (3 mins)
  • Importance of shifting CFR tests to the left with example (12 mins)
  • Step by step explanation of applying shift left in various stages of development right from discovery till delivery with an example case study (15mins)
                                                    - Identify your CFRs 
                                                    - Define your DoD
                                                    - Track your CFRs
  • Benefits of this approach (5 mins)
  • Conclusion (2 mins)
  • Q&A (5 mins)

Learning Outcome

  • Understanding the importance of shifting CFRs to the left of delivery cycle.
  • Mindset to better approach CFRs 
  • Tips and tricks that help to shift left CFRs 

 

Target Audience

Any one in the agile team who is responsible for delivering a quality product

Prerequisites for Attendees

  • Knowledge on Agile practices
  • Basic knowledge on CFR (aka) NFR(non functional requirements) testing
  • Basic understanding of Shift left approach would be a plus

 

schedule Submitted 8 months ago

  • Benjamin Bischoff
    keyboard_arrow_down

    Benjamin Bischoff - Of plugins and decorators - trivago's e2e test framework in the spotlight

    45 Mins
    Talk
    Intermediate

    Most often, test frameworks are developed from scratch and gradually extended with the required functionality. This approach is perfectly normal, but carries the risk of creeping technical debt as well as poor maintainability, transparency and extensibility. These risks can be minimized by using clean software architecture.

    In this talk, I will present two key parts of our internal Selenium-based end-to-end testing framework, which has been successfully used to test multiple web projects using desktop and mobile browsers during the past five years:

    1. the plugin infrastructure using Java's Service Provider Interface
    2. the custom WebElement decorator that enables more resilient Selenium WebElements

    I will explain the rationale for using these architectural tools and how these approaches mean that we can still evolve this framework quickly and easily to meet new needs.

  • Andrei Solntsev
    Andrei Solntsev
    Software developer
    Codeborne
    schedule 8 months ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate

    How to fight with unstable tests

    The talk is about flaky, or unstable tests – why it’s the biggest trouble in test automation and how to overcome it. I will show my collection of real-life examples of flaky tests from my experience. These are really tricky investigations that lasted many days, weeks and even years!
    The talk will be interesting to both testers and developers – anyone who loves to solve unsolvable puzzles.

help