aditimamid

 Profile Answers by aditimamid Questions by aditimamid

• Oct 21st, 2009

 

1st of all do sanitary testing, if you feel application is stable then go for Retesting and check all the functionality again.

mailtwogopal

 Profile Answers by mailtwogopal 

• Nov 1st, 2009

 

As stated earlier, Sanity testing helps you in identifying the stability as well as the flow of the AUT which helps in further realising the testing of particular module which undergone code change or testing the full AUT.

As far as I have experienced, I would also say even sanity test pass is found and if time permits as per schedule I advise you to re-test the module integrated with module which undergone changes. there is nothing wrong in it. One cannot say "Do" or "Don't do" as it depends entirely on the application.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Nov 10th, 2009

 

The depth of any test effort depends on the amount of time and resources management is willing to spend on it. This decision is largely based on the application under test, ranging from applications that have significantly high ramifications if defects occur (ie., code for an ATM where money is dispersed) to applications that have no tangible impact at all (ie.,
code that structures how something will behave on an application that has little
value to the company).

Of course, if the application under test can have potentially significant
impact on revenue or on customer perception, then management will be more
willing to devote more testing resources to it. In these conditions, it would be
worthwhile to conduct more than just a sanity test.

Nevertheless, in any situation, one begins with sanity testing, paying
particular attention to functionality that is influenced by the modified code.
Beyond that, it is best to identify any dependencies that other modules may have
on this module and sanity test them as well. If time permits, you would then
sanity check other major functionalities even though they may not be directly
dependent on the modified module.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Nov 28th, 2009

 

HI

  In this case i can do the functional testing on pirticular change, and then if required the i will do the Regression testing on an entire application if required.

But it's all depends on plan, strength of issues. For ex: only GUI related or text changes done then there is no need of regression/retesting.

CNU