In this series of blog posts, the goal is to help someone get started testing with Charles Proxy. The series will cover: What is a Proxy server? What is Charles Proxy and what can it do? How to set things up ready for testing? Test ideas using Charles including editing requests and responses, using breakpoints, throttling bandwidth, trigger various error codes and viewing network traffic. Make sure to start with Testing with Charles Proxy Part 1, before going through this post. continue reading

I find one of the hardest things about testing with a new tool, is actually getting started; familiarising myself with the new tool. In this series of blog posts, the goal is to help someone get started testing with Charles Proxy. The series will cover: What is a Proxy server? What is Charles Proxy and what can it do? How to set things up ready for testing? Test ideas using Charles including editing requests and responses, using breakpoints, throttling bandwidth, trigger various error codes and viewing network traffic. continue reading

It can be difficult to deal with intermittent bugs when they arise. In this blog post, I’ll share my thoughts on whether one should raise an intermittent bug, including if the bug can’t be reproduced. While there may not seem to be any value in raising an intermittent bug, I think it is worth documenting what you found. Did you make a mistake? Sometimes while testing, I make a mistake - I think I found an issue but then realised I actually double-clicked something or filled in a field with invalid data - which caused an error to appear on the screen. continue reading

I went to Toastmasters regularly for almost 8 years and one of my biggest key takeaways was the value of feedback. After every speech, someone would give a short 2-3 verbal evaluation of the speech. At the end of the evening, a general evaluator would give more feedback to everyone who had not given speeches (such as the evaluators). It’s safe to say that after almost 8 years at Toastmasters, I got pretty used to receiving feedback. continue reading

I’ve spent a few years of my career testing eCommerce sites and wanted to share a few test ideas, aside from the obvious ones such as add to cart, remove from cart, go to payments page etc. In the post below, I hope to also help trigger new test ideas for anyone who is working on eCommerce sites or apps. When you are logged in, add to cart on one device, then check on another device (that you are also logged in to) Here you are making sure that your activity isn’t just saved locally on your machine. continue reading

I’m having a presale on Gumroad (limited number available), before I hike up the price when the first version is published: If you want to see a sample of the eBook so far, check out my LinkedIn post where I shared Chapter 2: Gaining Skills Before (and After) Your First Role. You can also see the current breakdown of chapters and sections in each chapter. If you miss out on the presale, but want to be notified when the eBook is published, enter your email here. continue reading

In January 2022, I’ll be publishing an eBook on Leanpub called Starting Your Software Testing Career. If you want to be notified when the eBook is published, enter your email here. The eBook is currently being reviewed by experts in the field and by a few people in my target audience. The first published version will be about 60-70% of what the final book will be and will include chapters on Gaining Skills, Getting Your First Job, Finding a Mentor, Getting Started on a Software Testing Project, and much more. continue reading

Hi there, my name is Christina. I am an Agile Coach and my work is focused on collaborating with individuals, teams and organisations to embed and enable Agile practices. My expertise include team building, team coaching, meeting facilitation and developing practices such as Scrum and Kanban with a touch of Lean thinking. I enjoy generating and collaborating on new ideas, exploring solutions to challenges and I am actively involved in various communities as a speaker, workshop facilitator and other volunteering opportunities. continue reading

In past projects, written requirements have often been used as oracles to determine whether or not the behaviour they are seeing in the SUT (Software Under Test) is correct or not. According to Cem Kaner, an oracle or test oracle is a mechanism for determining whether a test passed or failed. The thing is, not every project has clear written requirements - some projects lack written requirements altogether, while others are not clearly written and are very open to interpretation. continue reading

It’s not hard to find articles or pieces of research claiming that the sooner you find a bug, the cheaper it is to fix. But I’ve found there isn’t actually a whole lot of information out there on exactly how to prevent bugs in the early stages of a software development project. i.e. before code is written, while requirements/user stories are being written or just after the requirements/user stories have been written continue reading