Regression and Retesting

Regression testing is a testing which is perform to ensure that changes ( feature enhancements or defect fixes) to the software have not contrary affected it

Retesting is a Testing which is perform (something) again or differently to verify.

lets took an example:





An application is developed with six features. Released for testing. Testing team per form testing found two(red colour) are having defects. Application returns back to developers. Developers perform fixation and also release a new built with feature enhancement( new feature is in brown) test team performs the testing over built. Testing over resolved issue( dark red ) is retesting. While testing over other impacted arias is called regression testing.( feature tested again due to new feature enhancement (gold) and due to test impact of fixation ( Gray)).

What is difference between Priority and Severity?

ISTQB Definition(priority: The level of (business) importance assigned to an item.)

Priority of a bug  is impact on application business. majorly bugs are having impact on business always . Impact can be differ of a bug at application. Hence priority  can be define in many types as per industry aspects. 
Mostly priority is categorized as High, medium and Low.
For example :  Material calculator is not function in inventory system. This issue is of High priority.



ISTQB Definition(severity: The degree of impact that a defect has on the development or operation of a component or system.)


Severity is measured by the impact of bug at application functions.  it normally indicates, how functioning is impacting application working. Severity is also organization specific. but as standards.
Five types are define.


Blocker: This leads to state when no further testing is possible.
Critical:  User is having data lose, crashes,exception in execution but application can tested.
Major: A function is not working.
Minor: A function is not working in few aspects.
Trivial: Insignificant  impact of issue at application.

What is difference between Smoke testing and Sanity Testing?

Smoke testing and Sanity testing is same as per all standards.
 But in industry specific term, it is is quite different. testing takes place in both manner first basic functional testing, basic functional testing with all positive aspects. smoke is execute all functional test scenario required priority base positive test cases. but in sanity tester put all positive test case with basic testing as well as few negative test cases if required. hence we just put little more efforts in sanity testing according industry aspects.

How ever Sanity is like regression testing but it does not cover all parts of application which may leads to existence of few defects. On the other hand Sanity is quickest way to find all critical bugs which can be cause of failure of any application.

Back Ground:

Smoke testing has been introduce in pipe industries for testing pipe leakage, Sanity is used in weather calculation. both are actually used to produce quick result.

Question and Answers

1. How should a Tester plan his/her tasks??

To make plan tester just first check it own limit to complete the task, it measures it's time limit and  make schedule as possible . it have also plan for delay and other unfortunate conditions. he is also depends on it's  budget and knowledge of domain.  he take 10-15 % time for  backup  so that he can handle it's unfortunate conditions. either his plan is mostly depends over the plan of given by his lead, but he also follow some strategic planning based on positive and negative aspects of project.
2. What can a tester do at the time bug fixing?

A tester is having a big role in success of project/ product in mean while he  is not free either built is gone for fixing. he measures the  previous  bugs and also effects after fixing. he analyze the tested built so he have the knowledge of built Architecture to find out the effects of fixing of bug over the other modules of Project, than he is also in state of new test case and plans for upcoming built.