Wim will be presenting the following session
filter_list help_outline
  • Varuna Srivastava

    Varuna Srivastava / Wim Selles - Build a responsive typescript wdio framework

    90 Mins

    Participate in this workshop to learn how to put together the concepts of a wdio and typescript in a mocha framework that is scalable, robust, easy to read. We will be sharing our real-time experience of how we migrated our testing approach, design and framework when our application was migrating from javascript to a typescript architecture.

    You will leave with your very own example automation framework that demonstrates advanced principles of wdio using typescript automation design. We will integrate with allure reporting.



    Key takeaways:

    1. A robust and scalable framework with the advanced principle for ui testing.
    2. A selection of design patterns for the designing framework.
    3. Concepts in designing your ui automation such as modeling data within your application and componentizing page objects.
    4. A framework which is responsive for web applications.
1. What got you started/interested in Testing?

I started in testing in 2007 when I was an account manager selling office equipment and wanted to do something different. I liked computers had an interview with Sogeti, and IT company in the Netherlands, to look into testing. I liked the idea to be kind of a gatekeeper for quality and started my journey in September 2007 at a small company in the Netherlands.

2. What has been your best moment/highlight working with Selenium?

It was not with coding, it was my second conference I visited in 2017 in Berlin. There were some great talks about Selenium and test automation, the one that really made me think was the talk of Richard Bradshaw which was called "Your Tests Aren't Flaky, You Are!" It was the exact same thing I was struggling with with some team members

3. What do you think is the biggest challenge faced by Software Testers today?

I think there are several things:

  • There are so many tools to help you do the automation, it's like a jungle. People tend to pick tools based on "it's hot", or "everybody is using it, I should also use it" instead of doing a proper research of which tool would help to guarantee the quality of the SUT
  • We tend to verify everything through the UI and to be honest, less is more
  • We tend to discard business value and business risks when we create our tests and start coding right away. This will often result in tests that don't have any value and slow down the build and release process
  • and many more
4. What is your advice to testers, who are new to automation?

I think that they should look at the points at "What do you think is the biggest challenge faced by Software Testers today?"