How of import is regression testing?

In a unmarried sentence, Regression testing is the retesting of a previously tested computer programme next modification to ensure that faults have got non been introduced or uncovered equally a resultant of the changes made. Regression testing helps to ensure that changes made to the software code practise non suspension other previously working parts of the software. It is of import to practise regression testing frequently, because the code equally a whole may easily "regress" to a lower score of character subsequently making a change. Regression testing is necessary, fifty-fifty though a alter appears to hold upwards working correctly in addition to is believed non to touching on the residuum of the software.

But definitions apart, always wondered how of import is regression testing? To hold upwards honest, I had been doing regression testing to a greater extent than equally a routine physical care for till recently. And ane sense (of course of study bitter) changed everything. While testing a product, ane time I received a post service from my projection Pb scream for me to seek out a build. He also sent a listing of changes made inward the build. Some of the changes were few major põrnikas fixes in addition to around were few novel features/enhancements. And I was asked to submit my written report inward iii days! So keeping inward hear the recent changes I had to brand my strategy to seek out the build. Also I had to kicking the bucket along inward hear the dependency of the affected modules amongst other related modules. And accordingly, I designed my seek out programme (I am non talking almost whatever seek out programme document here. Rather I was going to seek out the create yesteryear exploratory method, equally I had solely iii days to test). So I tested it in addition to submitted my written report inward due time, amongst around genuinely interesting in addition to of course of study major bugs.

Jeez! Instead of getting give-and-take of encouragement for my smart move (which I thought, I did), I got around other post service (this fourth dimension from my manager) stating that somehow I had missed a real of import bug! And how could it happen? Considering the detailed in addition to rigorous testing that had been done on the build! So instead of blaming others, I sat downwards to hold off for the loophole(s) inward my ain seek out plan/test strategy. And to my surprise, in that place were none!

So I asked my managing director to supply me amongst to a greater extent than details regarding the põrnikas which obviously I had missed. And in that place it was. The põrnikas was genuinely inward a far remote module which was inward no possible means related to whatever of the modules where I looked for possible problems. The argue was unproblematic however horrible! I was non told that in that place were around changes inward that module too! When the concerned developer was confronted yesteryear the manager, his respond was “I solely made around minor changes inward the code. So I didn’t mean value it was of import to inform almost this”. Strange! But hither I am non blaming the developer. To him the changes made mightiness seem minor in addition to unimportant. But equally a tester I should have got looked for unintentional errors inward this module too, equally this was an of import expanse of the application.

So I mean value these were my mistakes:
1. First, I should non have got believed the developer that he had made changes inward those listed areas only. Because the areas he listed were those which he idea equally important. At most I could have got taken the listing equally a reference solely spell planning my testing strategies.

2. While planning my strategy, I should have got included the other major in addition to of import areas, fifty-fifty if no apparent changes were made inward them. And here, I didn’t practise it because of fourth dimension constraint. But that also makes no excuse for me. In illustration of express time, I should have got tried to purchase to a greater extent than fourth dimension from my manager. If I was non able to purchase to a greater extent than fourth dimension from my manager, I should have got informed him inward advance almost my inability to encompass those other risky areas.

3. You mightiness order that I should have got done to a greater extent than rigorous regression testing. Which, I mean value I did to my satisfaction. But I missed that of import põrnikas due to my tunnel vision of the affected areas (as told yesteryear the developer lead). I didn’t anticipate the changes inward other possible areas. And inward the physical care for I missed the bug.

4. That fourth dimension nosotros didn’t have got whatever alter command method inward house inward our project. If in that place were one, hence all the changes made inward the code should have got been approved yesteryear the alter command board. In that illustration I could have got known each in addition to every module that could have got been perhaps affected yesteryear the changes.

After this experience, I realized the importance of regression testing inward whatever testing process, hold upwards it scripted or exploratory. Some of yous also mightiness have got faced around like situations. If so, practise part your sense amongst others yesteryear leaving a comment. Also if yous tin ship away mean value of whatever other possible reasons why I missed that of import bug, hence delight practise part amongst me. Waiting for your valuable comments…


More interesting articles here :Tutorial Software
Sumber : http://www.softwaretestingtricks.com/
Post a Comment (0)
Previous Post Next Post