Skip to main content


Showing posts from 2016

Approaches, Tools and Techniques for Security Testing *Very Useful*


Security testing is a process that is performed with the intention of revealing flaws in security mechanisms and finding the vulnerabilities or weaknesses of software applications. Recent security breaches of systems at retailers like Target and Home Depot, as well as Apple Pay competitor Current C, underscore the importance of ensuring that your security testing efforts are up to date.

The prime objective of security testing is to find out how vulnerable a system may be and to determine whether its data and resources are protected from potential intruders. Online transactions have increased rapidly of late making security testing as one of the most critical areas of testing for such web applications. Security testing is more effective in identifying potential vulnerabilities when performed regularly.

Normally, security testing has the following attributes:
AuthenticationAuthorizationConfidentialityAvailabilityIntegrityNon-repudiationResilienceWHY SECUR…

Difference between A/B testing and Multivariate testing

It’s been a while, so in the meantime I’ve found this quite useful as we are look to start introducing this within my streams of work!

Many people seem to get confused about the terms A/B testing, split testing and multivariate testing. Essentially, A/B testing and split testing are the same concepts but multivariate testing is different. So for all practical concepts, consider A/B Testing = Split Testing. The difference between A/B testing (or split testing) and Multivariate Testing:

A/B Testing

In A/B testing you split traffic amongst two or more completely different versions of a webpage (landing page, home page, etc.) The variations of your original page can differ in any manner. You can either just change the headline; or you can even change entire design, layout, offer and what not in the variations. What you change in A/B test is only limited by your creativity. For example, if you are A/B testing on your landing page you may want to create one version with 15% discount, the other…

What is a good Agile Tester ?

Its a good question!

Over the last couple of weeks I have read various articles highlighting what a good Agile tester is… all very good, but all very different!

"Testers are responsible for quality" No, no, no...
So the question is, what do YOU think a good Agile Tester looks like?
Here are my thoughts:
I strongly believe that a good Agile Tester is whatever it needs to be for a given project. Everybody within an Agile team has the same goal and requires continuous collaboration to succeed.
At the start of a sprint, an outsider looking in, should they be able to pick out who is the Developer, BA or Tester? I don’t think so. Everybody needs to be involved in defining things such as processes, user stories and acceptance criteria etc.
We all need to deliver value, we all need to continually look for improvements and we all need the ability to respond to change.
It’s only at this point that I see people doing specifics to their specific role, and for testers believe our main pu…


I came across this post recently here: I guess its a little like i have been feeling recently! Have a read...

Software testing can be stressful.

Causes can vary from deadlines, lack of communication, or internal pressure. It is also the relentless nature of the job. As much as we love our job, here are some of the struggles that only a tester will understand.

1. We are Undervalued

“Our developers can check their own code.”

Some companies use this reason to justify why they don’t need testers. This is especially common when the company doesn’t have a large budget.

You’ll always need testers. Cutting software testing expenses is not the way to go. Having a dedicated testing team will save you a lot more time and resources in the long run. If you release a buggy product, you’ll lose a huge amount of users. You’ll lose your developers’ time to fix the product, which increases your costs.

Your developers can write a bug-free p…

Exploratory Testing Poster Attempt!!!

Over the last couple of months I have had a number of team session relating to Exploratory Testing.

We wanted to create a poster that contained information about the following: Session basedKey elementsStructure to exploring softwareWhere does exploratory fitWhat to think about when exploring softwareSmall section on the benefits of paired testingTools to assist exploratory testing sessionsBug clusteringReporting/Auditing
So, I have done just that!
The main aims of this poster is to spark conversation within project teams about how/what you do when exploratory testing, it’s high-level ideas! There is no reason why you cannot create your own. I am NOT saying this is how you will do exploratory testing its more of an ideas framework equipped with some context for the wider stakeholders…
Here is my first attempt:

Exploratory Testing Framework Information
Our Principle: Exploratory testing is an approach to software testing that is concisely described as simultaneous learning, Test design an…