schedule Mar 22nd 03:45 - 04:30 PM place Jupiter people 28 Interested

Test Encapsulation has its basis in a research paper I wrote about a decade back for Testing Experience magazine and later presented in a some conferences. At the heart of test encapsulation is introspection - making 'test' the most powerful component of the test automation engine, providing all meta data to it so that it can make run time decisions for itself. It's a complete rethinking of the way test automation engines are architected internally.

The ideas were at a very nascent stage at that time. And well, they were just ideas and I was told how impossible they were. So, I ended up experimenting with the concept for almost a decade, creating 20+ automation engines, big and small, touching the philosophies to various levels. They had varying amount of success w.r.t. where I wanted them to be.

At last, I have got it right to a fair extent. This presentation would be more than theoretical exploration of possibilities. I would demonstrate a test engine that achieves many of the ideas that I discuss. The engine would be free and open-sourced so that attendees can freely experiment further.

 
1 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Demonstration

The session would have 3 primary phases to it:

  1. The story of an automated test - The first part of the talk happens (literally) from the perspective of a automated tests, raising important questions and establishing the need for test encapsulation.
  2. A brief interlude to introduce Arjuna - a free, open source Python based advanced test automation engine.
  3. How Arjuna enables writing of intelligent tests.

Learning Outcome

  1. Run time introspecting automated tests
  2. Subscription Model for Automated Regression Testing
  3. Meta-programming for automated tests
  4. A framework which implements Test Encapsulation

Target Audience

Developers, Testers, Managers who have been involved with test automation for 2+ years.

Prerequisites for Attendees

2+ years of hands-on exposure to test automation of any kind.

schedule Submitted 4 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Leena S N
    By Leena S N  ~  2 months ago
    reply Reply

    Rahul,

    This looks very interesting. Can you provide a few more details about the levels of intelligence these automation engines have? A few examples of the engines that you've built and how those make decisions by themselves might help.

    Also, wondering how is it concepts compared to Property-based testing?

    Thanks,

    Leena

     

  • Jeremy Kriegel
    By Jeremy Kriegel  ~  4 months ago
    reply Reply

    Thank you for your submission. While I think this talk sounds fascinating, I also think there is a mismatch with the audience for this talk and the audience of this track. The Design Innovation Track focuses primarily on Product Owners and UX, with benefit to coaches, stakeholders, and anyone else who helps guide the product. Perhaps this would be better suited to a different track?

    • Rahul Verma
      By Rahul Verma  ~  2 months ago
      reply Reply

      Thanks Jeremy.

      I am a software testing researcher. There is no direct track for testing in the conference. So, I guess this talk is going to be a misfit anywhere I put it :-)