It is nice to meet new terms and keywords relating testing. This morning I got a question how I am planning to do 'regression as part of Code Retrofitting testing'. Have never heard of retrofitting testing before, so did some googling. The best explanation I found was on blog http://blog.intrepidtesting.com/retrofit-vs-retest-vs-regression-testing/ article " Retrofit vs Retest vs Regression Testing " : Retrofit testing is carried to to test that a change in functionality is correctly implemented for existing entities. Retrofit testing is more commonly carried out when you have an incremental project, or change requests. If the time available to test is tight, retesting and retrofit testing usually takes a higher priority over regression testing Colleague's comment while trying to help me: " if I googled it correctly then they expect you to perform regression for legacy system where your changes were introduced. In this way I would ...
Comments
but what is the context?
but one thing thing should be always there which is, the responsibilities of a part time tester should be different then a full time tester.
Arrange a win-win state, determine what are the tings you can do as part time and what things you can't.
__
regards
I don't know whether you are checking your blogs... I was going through the old blogs..those are nice, speacially the blog were you discussed 'whether the tester is valuated? '. I have to contribute or rather ask you a question in this regard.
Developers are proud to show there application which they have developed. What are you proud of ? Are you proud to show off the application you have tested? Don't you think developers take all the credit for bugless application ?
This question have been haunting me. As a more experienced tester, I hope you help me out.
Thanks,
Jerison
(reading my blogs.. just still not time for testing because of the family. will be back soon)