When issues Regression testing some claim a bit of complexity for integration into the development process of a team, with small Features and diverse projects are discussed. For this case, and bearing in mind the definition of regression testing, we can design a simple integration that allows us to approach this useful practice.
Before seeing this we see a definition of regression testing:
They are called regression testing any type of software testing that attempt to uncover errors (bugs), lack of functionality, or functional deviations from the expected behavior of the software, caused by making a change in the program.
In the case of small tasks without immediate relation to other tasks you can select the last developed Feature or Bug repaired, and check again that they maintain the expected behavior.
Now if we are integrating a new Feature or repairing a bug on a Release larger, such as the integration of a new payment method for a shopping cart, you can select the last three developed Features or Bugs repaired, maintaining a direct relationship, and check again that they maintain the expected behavior.
This is a simple strategy that lends itself to many improvements, and can easily increase the level of quality throughout the development process