In this manner, we can see if the pages responded correctly to invalid data. We will add assertions to the samples following these scenarios to verify the ‘correctness’ of a requested page. Log in User-User logging in to an Accountįollowing these scenarios, we will simulate various entries and form submission as a request to a page is made, while checking the correct page response to these user entries. Create Account-New Visitor creating an Account The modified Test Plan will include these scenarios: We will create a Test Plan in order to demonstrate how we can confi gure the Test Plan to include functional testing capabilities. For this chapter, we will limit ourselves to selected functional aspects of the page that we seek to verify or assert. ![]() In fact, the application you want to test may even reside locally, with your own machine acting as the “localhost” server for your web application. Unlike for a load-testing Test Plan, it is unnecessary to select a specifi c workload time to perform a functional test. With some knowledge of HTML tags, you can test and verify any elements as you would expect them in the browser. ![]() However, to compensate for these shortcomings, JMeter allows the tester to create assertions based on the tags and text of the page as the HTML fi le is received by the client. This makes it diffi cult to test the GUI of an application under testing. In fact, it may not be able to render large HTML fi les 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, etc.) and it does not render the page for viewing. It tests on the protocol layer, not the client layer (i.e. In this regard, I need to highlight that JMeter does not have a built-in browser, unlike many functional-test tools. The Test Plan we will create and run at the end of this chapter will incorporate elements that support functional testing, exclusively. Later, we will create a new Test Plan similar to the Test Plan in Chapter 5, only smaller. We will begin the chapter with a quick overview to prepare you with a few expectations about JMeter. This chapter assumes that you have successfully gone through Chapter 5, and created a Test Plan for a specifi c target web server. This chapter will give a walk through on how to create a Test Plan as we incorporate and/or confi gure JMeter elements to support functional testing. In other words, aside from creating a Load Test Plan, JMeter also allows you to create a Functional Test Plan. This flexibility is certainly resource-effi cient for the testing project. Besides integrating functional-testing elements along with load-testing elements in the Test Plan, you can also create a Test Plan that runs these exclusively. ![]() Many other load-testing tools provide little or none of this feature, restricting themselves to performance-testing purposes. JMeter is found to be very useful and convenient in support of functional testing. Although JMeter is known more as a performance testing tool, functional testing elements can be integrated within the Test Plan, which was originally designed to support load testing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |