You are here


Tinkering with Arduinos and Python

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

Do you think Arduinos seem pretty nifty? Ever wondered what they are capable of if you throw some Python into the mix? This workshop is a fun hands-on tinkering session where you will learn how to combine python code with Arduinos! Control motors and power switches from your GUI buttons, or get your automated sensor readings on a dashboard. Or create an API. Code templates to expand and modify, as well as all necessary hardware will be provided (but at least 1 in 3 should bring a laptop).

Key takeaways:

  • Getting up and running with the whole chain from sensors&switches to GUI and API
  • Several examples of practical applications which you are likely to come across
  • Code templates to easily get started with several types of solutions



  • Attendee will have to bring a laptop

We’re in This Together - Mentoring a New Tester as a New Tester

Picture this situation: You’re the lone tester in your team. You find out that the company has just hired another tester. After a little digging you discover this is someone with little or no testing experience. You want to help the new hire, but maybe you aren’t all that experienced yourself. A bigger hurdle is that you’re also new to mentoring.

Not so long ago, I was a junior tester in a company that hired someone with no previous experience of the tech industry or testing. My mentee from there is now a successful lone tester. I will share what did and did not work in our mentor/mentee relationship. We will explore together the various stages of learning for a person with no testing experience from day one right up to the day they were using ZAP and JMeter to successfully identify issues in the application. I’ll also talk about how I felt when my mentee became better than me at using some of these tools and how the roles became reversed somewhat.

We’ll look at how to build mentor/mentee rapport and create an environment that enables people to feel safe if they fail.

Participants will get to hear the good, the bad and the ugly that can happen in a mentoring process from both the perspective of the mentor and the mentee.

In this session, I’ll share my own experiences with mentoring, with tips you can use to be an effective mentor, regardless of your experience level or situation.

Key takeaways:

  • Resources both mentor and mentee can use for the mentor/mentee relationship
  • Guidance to help both the lone mentor and the mentor who is a member of a larger team
  • Structuring and scheduling retrospectives to enhance learning
  • Understanding that you don’t need to know everything to be a good mentor

Pros of Proactive Ios App Profiling as a QA Pro

Imagine an application that suits you perfectly, but makes your phone literally a hot potato. Or, another case - in the middle of the day you find out that battery is critically low, though it was fully charged just a few hours before. Trying to find out the reason - you spot the app that was folded, however continued to actively exchange data with the server. I bet that as a user you will be irritated with either of the options.

I believe that QA engineer must care about all app characteristics that are crucial for the users and could do much more than just tapping the device screen and exploring how the UI responds.

So, let’s take an iOS app, xCode with Instruments and see which information could be retrieved. Energy log, Time Profiler, Activity Monitor… all these items might sound messy for the first time, but let me show you how beneficial their use could be for the testing and for the quality of the product. Also I'll show how we created & adjusted tools that help us in some of the specific checks.

After that let’s also discuss how we could cooperate with the developers in such investigations. That’s important as only together we could find out the root causes, but not the symptoms only.

Key takeaways:

  • We will learn what could irritate user and how an app lives on the user device 
  • We will explore how to collaborate with the developer and help them 
  • We will understand some of the developers’ pains 

Effective End 2 End Testing with CodeceptJS

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

There are lots of testing frameworks in JavaScript. Let’s learn the one which makes testing a joy. A tool that makes tests easy to follow and easy to work. CodeceptJS allows you to concentrate on test scenario and not on implementation details. It provides page objects, page fragments out of box.

Key takeaways:

  • How to setup browser tests with CodeceptJS
  • How to debug CodeceptJS tests
  • How to write tests using PageObjects Data management in CodeceptJS
  • How CodeceptJS can be used for mobile testing




Flaky Tests - Getting out of the Re-Run Cycle

If you have written and executed automated tests you have seen them doing their job very well, but most probably you have also seen some of the tests both failing and passing on the same code with no apparent reason. The kind of tests that give both failing and passing results on the same code and configuration are called flaky(nondeterministic) tests. Having flaky tests in your testsuite will make your tests unreliable and eventually they will lose their value. When you can’t trust your tests, why do you execute them at all?

During the presentation I will share real life examples of the steps that can be taken to reduce test flakiness and the amount of time spent on handling flaky tests.

Key takeaways:

The attendees will walk away with the following practical tips:

  • how to identify flaky tests how to reduce test flakiness
  • how to live with flaky tests (there will always be flaky tests, but it is possible to make them easier to handle)

Power of Orthogonal Pairing in Devops Quality

One of the changes between testing in a DevOps environment compared to testing in a more classical agile, or even waterfall is the ability to test and learn about the product in all phases. We don't so much follow the development and test sequentially but instead learn and analyze simultaneously from many angles. This provides a whole range of new opportunities to increase value provided, but also presents a lot of new mind sets and perspectives to assimilate. We realize that we provide, or limit, quality and value for all kind of users and crew. Do we know how to test deployment pipelines, monitoring tools and server fallback routines? One of the ways to get up running fast is to sit together, and collaborate.

Some but not all have been pairing like this for a long time within the team. We pair with other testers to share knowledge, we pair with developers on testing and coding to learn about the code and share testing mindsets.

Now we also get the opportunity to pair with so many others! Management, operations, marketing or IT-infrastructure teams and any other departments you have. Sharing knowledge is a goal, but pairing and tight collaboration also helps to build bridges. Closer and more personal relations and a shared language reduce friction and increase the momentum for change and improvement. They say that to know someone you should walk a mile in their shoes, so let’s do that. And also let them try on yours. Spend an hour and do what they do, and you will both see new ideas. For instance: Pairing with management and product owners made it easier for them to express their needs and see possibilities, but also taught me the importance of translating and express ideas, wishes and problems into dollars and cents. Pairing with customer support resulted in the design of a tool for express change requests, reducing their queue-times for unexpected problems and allowing the development team an new insight into day to day problems. Also, when invited into a bug bash they reported a new record of found bugs, clearly showing that our channels for internal communications where too much of an hassle for them to report through before.

Key takeaways:

  • Tips on how to get effective pairing sessions with other professions.
  • How to become a better tester by learning other jobs.
  • Why bouncing ideas in orthogonal directions generates value.
  • Pairing and learning is fun! Let's do more of it.

House of Cards - Software Testing Lessons from Frank Underwood

House of Cards is my favourite TV Show. It depicts the US politician Frank Underwood, and his struggle to gain power and influence in American politics. Now while it might not be immediately seen as a natural place to learn about software testing, it struck me that a lot of the ideas and comments made in the TV series can be directly transferred to our world of software testing.

Having gone through a bit more systematically I've found a whole series of great quotes from several of the characters in the show that I've set in a testing context and will present in a humorous way.

The short track should be lighthearted and entertaining, despite addressing some real testing principals that everyone should remember. Having seen the show is not a requirement, but might make it even more entertaining. And I'll keep it spoiler-free for those who haven't seen it.

Key takeaways:

Entertainment repetition of good practices in software testing, a different view on house of cards, and perhaps software testing.

The Four-Hour Tester

The challenge of teaching new testers useful skills is something that many testers face – either you’re a manager, a test competence lead, or an experienced tester who coaches other testers. What would you need to learn and practice to become a tester in the first place? How would you pick the things to learn and skills to practice to help a new team member learn the ropes of testing and start adding value? If Tim Ferriss can come up with the 4-hour chef, why can’t we come up with the 4-hour tester?

Armed with the hypothesis that it’s possible to identify the core skills and knowledge for testers and that it’s possible to become familiar with those in 4 hours, Joep and Helena set out to explore and discover what that core consists of. This talk addresses the process of discovery itself, how they found the hypothesis to be or not to be true, and what they learned along the way. They will also present the results of the experiment as a set of heuristics in a framework that can help novice testers to learn testing.

Key takeaways:

  • Sometimes learning means trying something with minimal instruction
  • What the five basis testing skills are that we identified
  • Inspiration to try the exercises at and/or to develop something similar

The Fraud Squad - Learning to Manage Impostor Syndrome as a Tester

"I've just got where I am though luck!" "I'm going to be found out at any moment!" "I don't deserve the success I've achieved!" "I'm a giant fraud!" These are all pretty common thoughts someone suffering from Impostor Syndrome might have. I hear Impostor Syndrome mentioned frequently as something common in our industry, but hadn't even heard of it until a couple of years ago. It's something a lot of successful and really intelligent people suffer from. Its effects can be debilitating, and it shouldn't be dismissed as non-existent or unimportant. We need to acknowledge it, talk about it, and make it ok for people to admit they are affected by it. I'll talk about how my own feelings of Impostor Syndrome have affected me throughout career, even when I didn't know what it was, what I've done to manage these negative feelings, and how it's enabled me to start making a positive contribution to the testing community.

Key takeaways:

  • An understanding of what Impostor Syndrome is, why people suffer from it and what it feels like
  • If you suffer from Impostor syndrome, you aren't alone
  • If you suffer from Impostor syndrome, it isn't a sign of weakness
  • If you suffer from Impostor syndrome, you can manage it, and do amazing things
Subscribe to Beta&Gamma