Skip to main content

Posts

Showing posts from 2018

How to set up a proxy on Charles (so you can test other devices on your local dev machine)

Have you ever wondered, how do I test my fixes/changes on my local machine on IE 11? Or in general, how do I test my fixes/changes on my local machine, when I don't actually have that browser on my laptop? If so, the Charles Proxy tool might be your answer. A few years ago I learned this and I thought this could be useful for you if any of the below apply to you: You are developing on a Mac and want to test Internet Explorer 11 or Microsoft Edge on your local machine You want to test your fixes on a (physical) mobile device, with fixes done on your local machine You don't have access to a mobile device/internet browser simulator like Browserstack or Perfecto For this I'm going to explain how to set this up using your development laptop and a "test device" 1. Download Charles https://www.charlesproxy.com/download/  and install this on your laptop where you do your development 2. Make sure both the laptop and the test device are on the same internet net

My experience at Agile Testing Days 2018

I had seen blog posts and activity on Twitter in the years leading up to my first ever Agile Testing Days (ATD(- it seemed like people really enjoyed this conference, so it's safe to say I was glad to get  this email from Uwe saying: "Congratulations, you are part of the Agile Testing Days 10th anniversary as a speaker with:  Bringing in change when you don’t have a “leadership” job title ! " For me, this is a BIG conference, a lot of people; a lot of attendees and A LOT of tracks - won't deny I found this intimidating as there were a lot of interesting talks/workshops at the same time. Looking back at this conference, one thing that really stands out to me is choice: Which will I see? Which am I prepared to miss out on?

My experience at Belgrade Test Conference 2018

Just under two weeks ago, I flew to Belgrade for the first time, to present my talk: " What I wish I knew in my first year of testing" at the Starter track.  According to the conference site the Starter track: "will focus more on the role of testing in general and software development basics, as well as some technical showcases of what testing actually looks like.  It is well suited for people who want to start their careers in software testing or deepen their understanding of testing." The conference had 3 parallel tracks - 1 Starter and 2 tester tracks, based on my understanding, people could only get access to either the 2 tester tracks or the 1 Starter track. It was my second time presenting this talk (after presenting it at Eurostar 2016) but this time the talk was very different, same core idea but the actual material itself was about 30-40% different and organised/structured very differently. I arrived in Belgrade on the evening of November

An analogy to explain the limitations of test cases

I love analogies. They help me explain things in a way that (hopefully) others can understand and relate to. When I was thinking how can I try and explain the limitations of test cases (because knowing test cases aren't all they are cracked up to be, and explaining that to someone - are two different things) the first thing that came to mind is job interviews. We've all been on job interviews - it's an understandable concept and we can all relate. So here we go: First, let's agree that both testing and job interviews are information seeking activities. In testing, we are trying to find out information about the Software Under Test. In job interviews, the company is trying to seek information on the candidate (actually it goes both ways- the candidate is also trying to seek information on the company as well) Second, let's agree that in both examples you want to make an informed decision. In testing, you want to know if the software is ready to go live or