This makes it difficult to test the GUI of an application under testing. In fact, it may not be able to render large HTML files at all. Although, by default that embedded resources can be downloaded, rendering these in the Listener/ View Results Tree may not yield a 100% browser-like rendering. JavaScripts, applets, and many more.) and it does not render the page for viewing. It tests on the protocol layer, not the client layer (i.e. JMeter does not have a built-in browser, unlike many functional-test tools. Preparing for Functional Testing by Using JMETER For weekly releases regression tests can be performed when functional testing is over for the changes. For the release taking months to complete, regression tests must be incorporated in the daily test cycle.
Regression testing is usually performed after verification of changes or new functionality. Regression test should be the part of release cycle and must be considered in test estimation.
When this test is done tester should verify if the existing functionality is working as expected and new changes have not introduced any defect in functionality that was working before this change. The intention of this test is to verify the changes made in the existing functionality and newly added functionality.
Testers perform functional testing when new build is available for verification. Verifying that the bugs are fixed and the newly added features have not created in problem in previous working version of software. This test can be performed on a new build when there is significant change in original functionality or even a single bug fix. Test cases are re-executed in order to check whether previous functionality of application is working fine and new changes have not introduced any new bugs. Regression means retesting the unchanged parts of the application.