In this post, I will be looking at Bugs with an insight that helps testers to learn some new lessons on why the same might have occured. It’s quite common that the testers are blammed for all the missed out bugs in the system as if they are super natural powers to over see all the issues that are there in the system.
Bugs are there every where. Not just software applications, look at any system for that matter & there are issues wrt End User needs and the same might need to evovle over a period of time with the changing needs / requirements from time to time.
What is a Bug ?
It’s tough to arrive at a generic defintion for the bug & people might have heated discussions on what is a bug & what is not. Mostly it’s based on the context in which people are working. We do come across many bugs in our daily life while working with the tools that are needed for the day to day operations.
So in my context, Bug is something that’s unable (doesn’t allow me) to satisfy my needs with the system. What do to do ?
Capture the story around the Bug and not just steps to reproduce. Talk to the reporter and discuss on the scenarios used with the system that lead to the bug.Let’s explore the possible options even though Tester validated the system early
New Test Scenarios for the Testers
-
We mayn’t even think of that scenario while validating the system. Add the similar test scenarios to the Test Suites
-
The scenario may not be logical (though it seemed to be for testers) for the user though functionally correct. Add to the similar scenarios to Test Suites
-
Might have been a compatability issue with a new environment that doesn’t exist in Test Labs
Reduce mistakes and improve test teams capability
-
Might have been missed by a Tester. Check with the tester who performed the Test earlier and find out on why issue missed and the same marked as a pass even though it fails. Might happen through overlook also. Do more analysis here and try to reduce the same.
-
Might be over looked through regression tests. Might have failed and passed in the internal builds and finally breaked in the production system. Analyse the reasons here and improve upon on regression testing.
-
Make it a point to log the bug as soon as they discover the same. People might loose the same from their memory as time goes
Software Projects need effective & skilled programmers to deliver on time without compromising on the assured quality. We often need generic skills apart from the technology to deliver effective solutions on time. I have come across of the article
Seven Habits of Effective Programmers has been originally published at
Technicat. Philip Chu share his experiences with Software Releases and the comes up with a list of seven habits that makes normal programmers effective.
Habits of Effective Programmers
- Understand your requirements
- Keep it real
- Understand your code
- Optimal Programming
- Manage Thyself
- Continuous education
- Respect your peers and managers
Abstract
As a software engineer, you might want any number of things out of your job – a steady paycheck, the opportunity to work on interesting projects, a springboard to the next better job, or maybe you just like hanging out with other programmers. But by “effective”, I mean the ability to complete projects in a timely manner with the expected quality. After working on dozens of software releases, I believe the following practices will bring you there, and while they may involve sticking your neck out, I’d like to think they will also advance your professional reputation, career longevity, and personal satisfaction.
Check out For Seven Habits of Effective Programmers for complete reading
In this post, i will share my views & findings with Open Source Test Management Tools. Usage of tools in the Test Management is becoming the basic need & It will be tough to manage the activities associated there with out any support from the tools.
The commercial tools in this segment are costly and may not fit into upcoming organizations budget. So i have been looking at Open Source Test Management tools. In the last week, I have evaluated some open source test management tools.
The following are my requirements for Test Management Tool
-
Capture the Requirements
-
Design Test Cases
-
Map Test Cases with Requirements
-
Link Bug reports with Test Case ID after the test execution
-
Test Execution Reports
-
Version Management for the Test Cases
-
Search Feature
The following tools are evaluated after the initial screening.
The above tools work with Apache, MySQL & PHP. Both the tools looks promising and the Test Link has some additional benefits in-terms of better reports and linking with popular issue trackers.
