Dabbagh Bits

When you have a set of test cases to execute, and especially across various platforms, it’s very time-efficient to do a base case run before you start officially marking test cases as pass/fail. In testing lingo, this is classified as smoke tests or sanity tests. It helps with

Sometimes as QA Engineers we focus too much on individual components of the product or service we’re responsible for. To truly understand your product, to properly identify what’s working and what’s not, to know the state of quality, you need to use your product like an end

One of the biggest challenges I face in my current role is handling my main responsibilities and balancing the extra work required to stay out of technical debt or to de-clutter. We’re a small team of 3 QA Engineers plus a co-op now, and before that for over a

In my current role, we’ve created something we call internally as Minimum Regression Test Runs. It’s basically a minimum set of test cases that must be executed for every release, no matter how big or small the release is. More on this in a future post but while

In part 1 [http://dabbaghbits.com/2017/01/12/selenium-webdriver-part-1-architecture-to-handle-different-browsers/] of the Selenium WebDriver introduction to running tests with different browsers, we proposed an architecture to enable us to achieve our goal. In this part, we’ll talk about how to use Ant [http://ant.apache.org/] to run tests

Selenium WebDriver has pretty much been the de-facto standard for web automation. While there is a lot of documentation out there, I haven’t found an article explaining an architecture for running scripts with different browsers. This is part 1 of a 2 part series to explain the steps we

You have no idea how many times I’ve seen updates get pushed to production that break major functionality and cause havoc. This is a problem everywhere, small or large companies. Doesn’t matter if you’re agile, waterfall, or whatever else. There is no excuse to not test properly

To a developer, tester, product manager, and even between testers themselves, testing and quality assurance can mean different things. I want to highlight what being a tester means to me, and hopefully initiate that conversation for you. To start, testing is a passion. If you don’t have the passion

Before starting my current job, I didn’t have a lot of responsibility on my shoulders. I worked in a big company and only had my tasks to complete and then go home. Fast forward to my first app release, delivering an app to thousands of users, and it had

I’m not one for cliches, but “raise your standards” is a statement that’s truly powerful and is actually useful. Something if you were to apply to your every day life, whether it be a job, side work, living arrangements, or anything at all, it will make a tremendous

As testers, many times we need the help, support, and skills of our colleagues around us to achieve our goals. Realizing what you need to complete a task or to test software is a vital skill to have. It can save you, and others, a great deal of time and

Just like how there are code reviews to get a second look at code, we can apply the same thing for test cases. Test case reviewsare an effective way to ensure test cases are written properly and have good coverage. When writing test code, that by default should always be

Sometimes I find myself struggling to organize a test suite in a way that seems efficient or just feels right. Today, I was looking over a test suite written by a colleague and something clicked: * Organize tests in a way that traces user flows * Organize tests in a way such

Bug verification can seem like the easiest thing in the world, but it’s not as simple as you might think. It takes extra effort to go from an ok tester, to an outstanding one. Let’s start with the steps an ok tester might take: 1. Go through bug