Entries Tagged 'Testing best practices' ↓
May 26th, 2016 — Career in Software Testing, Testing best practices, Testing Tips and resources
We all heard the story of the little frogs in the well who thought the world is the well until they came out and realized how big, beautiful and different it is!
Do you think you have lived this story at some point in your professional life? Well, everyone has. Welcome to the world of reality – beautiful testing :).
Today, I want to share 4 mistakes I made when I started my software testing career. You’re Probably Making These. Check out. Continue reading →
April 4th, 2016 — Career in Software Testing, How to be a good tester, Testing best practices, Testing Skill Improvement, Testing Tips and resources
Challenges are normal. It is when you look at them as opportunities, a gold mine and as obstacles, a land mine. I have had my share of ‘opportunities’ over the years in the IT industry.
Some came with the role I was playing, some general. This is my attempt to record them and to reach out to the community to see if any of those resonate with you and maybe, in a small capacity help you and let you know that you are not alone.
Here’s my top 10 list:
Continue reading →
March 14th, 2016 — Agile Testing, Testing best practices
Technical debt is a metaphorical idea which argues that just as one may run into debt problems in finance, software organizations encounter something similar in the buildup of unfinished work during past projects and version releases/sprints.
What is Technical debt?
It represents the effort needed to fix the issues/defects that remain in the code when an application is released. In simple words – it’s the difference (in terms of bugs) between what is expected and what is delivered.
When a development team is busy working on a project and fixing bugs unfortunately, many new bugs appear. Out of Continue reading →
March 7th, 2016 — Bug Defect tracking, Testing best practices, Testing Tips and resources
Do you believe that software errors occur only once and that on being fixed they never resurface? I feel that about 30% of the errors reoccur.
In this article, I want to cover how important it is to document some of the frequently encountered errors.
Below, you will find some common areas where issues are seen and a template to document them. Continue reading →
February 29th, 2016 — Agile Testing, Testing best practices, Testing Methodologies
In the first part of the article series, we understood the nuances of Continuous Delivery (CD) where we have production ready software at any point via continuous feedback loops. Continuous integration (CI) is the real meat behind the CD process and is the reason that makes Continuous Delivery possible.
To understand CI, let’s take the terms at face value and deduce a basic definition. The first word means “ongoing” or “frequent” and the second “merged” or “made part of”. So CI is a process where something is being “merged”-“frequently”.
Logically the next question is: What is the something being merged and where is it merged?
Continue reading →
February 25th, 2016 — Agile Testing, Testing best practices, Testing Methodologies
In this two-part article series, we will focus on Continuous Delivery (CD) and Continuous Integration (CI), starting with an at length discussion on Continuous delivery today.
Software development has seen a steep outlook and approach difference to keep up with the current market trends and consumer needs. While the traditional waterfall approach was more sequential and planned, it has setbacks in terms of satisfying customer expectations of the final product. Continue reading →