RE: What is testing methodology?Is retesting is ...
Test Methodology is Overall Application Programming.(i.e) To Check the Application Program works without bugs. To check whether the Application Programs work properly or not use by our testcases.
Retesting is done to check a part of the application when the bug's have been fixed.
When the code has been modified the whole application is tested to check if the application is working fine is called Regression Testing.
Regresion Testing done after enhancement in Software and Re-testing is after Bug Fixing
RE: What is testing methodology?Is retesting is ...
Hi Shailaja
When the code has been modified the whole application is tested to check if the application is working fine is called Regression Testing.
This is what u replied about Regression but as per me whole application is not tested for regression only that part of the application where the code change might affected will be tested only not the whole application
RE: What is testing methodology?Is retesting is ...
In my point of view Restesting is that testing to check the application after regular interval of time that it works properly or not i.e its expected result match the actual result.
Regression testing is that testing when a software tester found the bug he than send back to the developer to fix that particular bug after that tester sees that this fix bug should not effect on any other module fuctionality.
RE: What is testing methodology?Is retesting is ...
Retesting- when a defect is detected and fixed then the software should be retested to confirm that the original defect has been removed successfully.
Regression- is the repeated testing of an already testing programe after modification to discover any defects introduced or uncovered as a result of the change(s).
RE: What is testing methodology?Is retesting is ...
Regrassion Testing; It is testing in which one will perform allready testing functionality. Regression testiong is done in 2 ways 1. Whenever test engineers raises some doubts then developer rectifys that. and build is released from the developers department now test engineers will perform the defective functionality and also related functionalities once again.
2. Whenever new changes are incororapted by the developer and the new build is realesed form the developers department.. then test engineer will perfom the test once again.
RE: What is testing methodology?Is retesting is ...
Testing methodology means testing an application fully and check whether it is working fine with specified requirements or not. Regression Testing: When a bug is found in an application then that bug is reported to developers.They apply modifications (Regress) on it and send back to tester. Tester again check the application & see if it is working correctly now or not i.e. when any modification is made to an application testing is done to check whether it is working fine or not called regression testing. Re-Testing:Testing done by applying different values to a module to see its desired functionality.
RE: What is testing methodology?Is retesting is ...
Testing Methodology: To check the application is working properly or not. Regression : Whenever is bug found send to the developer for fixing after fixing of bug they send new build for testing.Tester check the that bug is found or not and check the all functionality is working or not. and also check the other functionality is not affected by the this fixing.
RE: What is testing methodology?Is retesting is ...
Retesting: Retesting the module/application to check whether the reported bug is soved or not. RegressionTesing: it executed after new version (any modifications) released to ensure there has been no negative impact on the capabilities which the application provided by the earlier release. ---verify the defects which have been identified as corrected ---verify the newly delivered functionality
RE: What is testing methodology?Is retesting is ...
Retesting: The re-execution of the test on modified build with multiple test data is retesting.
Regression Testing:Retesting of a previously tested program following the modification to ensure that whether any faults have been introduced or not. It is performed only when the software or its environment is changed.