Interview Questions and Answers

Interview Questions And Answers

Manual, automation, qtp,qc, bugzilla, agilemethodology, functional ...More
Manual, automation, qtp,qc, bugzilla, agilemethodology, functionaltesting, non functionaltesting, black box,structural, peer to peertesting, white boxtesting, static testing,dynamic testing,Assertion Testing. (NBS), Automated Testing ,Background testing, Bug,Beta Testing, Benchmarks,Benchmarking, Big-bangtesting , Boundary ValueAnalysis , Cause EffectGraph Less

Interview Questions and Answers

to get instant updates about 'Interview Questions And Answers' on your MyPage. Meet other similar minded people. Its Free!

X 

All Updates


No Detailed Information available.

No feeds found

All
Posting your question. Please wait!...


About

Manual, automation, qtp, qc, bugzilla, agile methodology, functional testing, non functional testing, black box, structural, peer to peer testing, white box testing, static testing, dynamic testing, Assertion Testing. (NBS) , Automated Testing , Background testing, Bug, Beta Testing, Benchmarks, Benchmarking, Big-bang testing , Boundary Value Analysis , Cause Effect Graph

RSS

10:12 AM - 29 Oct 14

jMeter Tutorial - FTP Test Plan

In this chapter we will see how to test a FTP site using JMeter. Let us create a Test Plan to test the FTP site. Rename Test Plan Start the JMeter window by clicking on /home/deepak/apache-jmeter-2.9/bin/jmeter.sh. Click on the Test Plan node. Rename this Test Plan node as TestFTPSite. Add Thread Group Add one Thread Group, which is placeholder for all other elements like Samplers, Controllers, Listeners. Right click on TestFTPSite(our Test Plan) > Add > Threads(Users) > Thread Group. Thread Group will get added under the Test Plan (TestFTPSite) node. Next let us modify the default properties of the Thread Group to suit our testing. Following properties are changed: Name: FTPusers Number of Threads (Users): 4 Ramp-Up Period: leave the the default value of 0 seconds. Loop Count:1Add Sampler- FTP Request Now that we have defined our users, it is time to define the tasks that they will be performing. We will add FTP Request elements. We will add two FTP request elements, one which will retrieve a file and one which will put a file on the ftp site. Begin by selecting the FTPusers element. Click your right mouse button to get the Add menu, and then select Add > Sampler > FTP Request. Then, select the FTP Request element in the tree and edit the following properties as in the image below:The following details are entered in the this element: Name: FTP Request Get Server Name or IP: 184.168.74.29 Remote File: /home/deepak/sample_ftp.txt Local File:sample_ftp.txt Select get(RETR) Username:deepak Password:system123 Now add another FTP request as above and edit the properties as in the image below: The following details are entered in the this element: Name: FTP Request Put Server Name or IP: 184.168.74.29 Remote File: /home/deepak/examplefile.txt Local File: /home/deepak/work/examplefile.txt Select put(STOR) Username:deepak Password:system123 Add Listener The final element you need to add to your Test Plan is a Listener. This element is responsible for storing all of the results of your FTP requests in a file and presenting a visual model of the data. Select the FTPusers element and add a View Results Tree listener (Add > Listener > View Results Tree). Run the Test Plan Now save the above test plan as ftpsite_test.jmx. Execute this test plan using Run > Start option. View Output The following output can be seen in the listener. You can see that four requests are made for each FTP request. We see that the test is successful. The retrieved file for GET request is stored in the bin folder. In our case it would be /home/deepak/apache-jmeter-2.9/bin/. For PUT request the file is uploaded at the path /home/deepak/.Answer Here...
12:14 AM - 15 Sep 14

jMeter Tutorial - Database Test Plan

In this chapter we will see how to create a simple test plan to test the database server. For our test purpose we have used the MYSQL database server. You can use any other database for testing. For installation and table creation in MYSQL.Once MYSQL is installed, follow the steps below to setup the database:Create a database with name "tutorial".Create a table tutorials_tbl.Insert records into tutorials_tbl :mysql> use TUTORIALS;Database changedmysql> INSERT INTO tutorials_tbl ->(tutorial_title, tutorial_author, submission_date) ->VALUES ->("Learn PHP", "John Poul", NOW());Query OK, 1 row affected (0.01 sec)mysql> INSERT INTO tutorials_tbl ->(tutorial_title, tutorial_author, submission_date) ->VALUES ->("Learn MySQL", "Abdul S", NOW());Query OK, 1 row affected (0.01 sec)mysql> INSERT INTO tutorials_tbl ->(tutorial_title, tutorial_author, submission_date) ->VALUES ->("JAVA Tutorial", "Sanjay", '2007-05-06');Query OK, 1 row affected (0.01 sec)mysql>Copy the appropriate JDBC driver to /home/deepak/apache-jmeter-2.9/lib.Create JMeter Test PlanFirst let's start the JMeter from /home/deepak/apache-jmeter-2.9/bin/jmeter.sh.ADD USERSNow create a Thread group, right click on Test Plan > Add> Threads(Users)> Thread Group. Thread Group will get added under the Test Plan node. Rename this Thread Group as JDBC Users.We will not change the default properties of the Thread Group.ADDING JDBC REQUESTSNow that we have defined our users, it is time to define the tasks that they will be performing. In this section, you will specify the JDBC requests to perform. Right click on the JDBC Users element, selectAdd > Config Element > JDBC Connection Configuration.Set up the following fields (we are using MySQL database called tutorial):Variable name bound to pool. This needs to uniquely identify the configuration. It is used by the JDBC Sampler to identify the configuration to be used. We have named it as testDatabase URL: jdbc:mysql://localhost:3306/tutorialJDBC Driver class: com.mysql.jdbc.DriverUsername: rootPassword: password for rootThe other fields on the screen can be left as the defaults as shown below:Now add a JDBC Request which refers to the JDBC Configuration pool defined above. Select JDBC Users element, click your right mouse button to get the Add menu, and then select Add > Sampler > JDBC Request. Then, select this new element to view its Control Panel. Edit the properties as below:Variable name bound to pool. This needs to uniquely identify the configuration. It is used by the JDBC Sampler to identify the configuration to be used. We have named it as testName: LearnEnter the Pool Name: test (same as in the configuration element)Query Type: Select statementEnter the SQL Query String field.CREATE LISTENERNow add the Listener element. This element is responsible for storing all of the results of your JDBC requests in a file and presenting a visual model of the data.Select the JDBC Users element and add a View Results Tree listener (Add > Listener > View Results Tree).SAVE AND EXECUTE TEST PLANNow save the above test plan as db_test.jmx. Execute this test plan using Run > Start option.VERIFY OUTPUTIn the last image you can see that 2 records are selected.Answer Here...
03:52 PM - 22 Aug 14

jMeter Tutorial - Web Test Plan

Let's build a simple test plan which tests a web page. We will write a test plan in Apache JMeter so that we can test performance of one web page say page shown by the URL:http://www.testinganswers.com/. Start JMeter Open the JMeter window by clicking on /home/deepak/apache-jmeter-2.9/bin/jmeter.sh. The JMeter window will appear as below: This is a JMeter window having nothing added yet. Details of the above window are: Test Plan node is where the real test plan is kept.Workbench node is where the temporary stuff is kept. Rename Test Plan Change the name of test plan node to Sample Test in the Name text box. You have to change focus to workbench node and back to Test Plan node to see the name getting reflected.Add Thread Group Now we will add our first element in the window. We will add one Thread Group, which is placeholder for all other elements like Samplers, Controllers, Listeners. We need one so we can configure number of users to simulate. In JMeter all the node elements are added by using the context menu. You have to right click the element where you want to add a child element node. Then choose the appropriate option to add. Right click on Sample Test(our Test Plan )> Add> Threads(Users)> Thread Group. Thread Group will get added under the Test Plan (Sample Test) node.We will name Thread Group as Users. For us this element means Users visiting the TutorialsPoint Home Page. Add Sampler Now we have to add one Sampler in our Thread Group (Users). As done earlier for adding Thread group, this time we will open the context menu of the Thread Group (Users) node by right clicking and we will add HTTP Request Sampler by choosing Add > Sampler> HTTP request option.This will add one empty HTTP Request Sampler under the Thread Group (Users) node. Let us configure this node element:Name: We will change the name to reflect the action what we want to achieve. We will name it as Visit TutorialsPoint Home PageServer Name or IP: Here we have to type the web server name. In our case it is www.testinganswers.com. (http:// part is not written this is only the name of the server or its IP)Protocol: We will keep this blank, which means we want HTTP as the protocol.Path: We will type path as / (slash). This means we want the root page of the server. Add Listener We will add a listener. Let us add View Results Tree Listener under the Thread Group (User) node. This will ensure that the results of the Sampler will be available to view in this Listener node element. Open the context menu and Right click on Thread Group(Users) choose Add > Listener > View Results Tree option to add the listener.Run the Test Plan Now with all the setup, let's execute the test plan. With the configuration of the Thread Group (Users) we have kept it all default values. This means JMeter will execute the sampler only once. It will be like a single user and only one time. This is similar to like a user visiting a web page through browser, only here we are doing that through JMeter sampler. We will execute the test plan using Run > Start option. Apache JMeter asks us to save the test plan in a disk file before actually starting the test. This is important if we want to run the test plan again and again. If we say not to save by clicking No option it will run without saving. View Output We have kept the setting of the thread group as single thread (that means one user only) and loop for 1 time (that means run only one time), hence we will get result of one single transaction in the View Result Tree Listener. Details of the above result are: Green color against the name Visit TutorialsPoint Home Page indicates success.JMeter has stored all the headers and the response sent by the web server and ready to show us the result in many ways.The first tab is Sampler Results. It shows JMeter data as well as data returned by the web server. The second tab is Request, where all the data which was sent to the web server as part of the request is shown.  The last tab is Response data. In this tab the listener shows the data received from server as it is in text format.This is just a simple test plan which executes only one request. But JMeter's real strength is in sending the same request like many users are sending it. To test the web servers with multiple users we will have to change the Thread Group (Users) settings. Answer Here...
03:50 PM - 22 Aug 14

jMeter Tutorial - Test Plan Elements

A JMeter Test Plan comprises of test elements which are discussed below. A Test Plan would comprise at least one Thread Group. Within each Thread Group we may place a combination of one or more of other elements: Sampler, Logic Controller, Configuration Element, Listener, and Timer. Each Sampler can be preceded by one or more Pre-processor element, followed by Post-processor element, and/or Assertion element. Let's see each of these elements in detail: ThreadGroup Thread Group elements are the beginning points of your test plan. As the name suggests, the thread group elements control the number of threads JMeter will use during the test. We can also control the following via the Thread Group: By setting the number of Threads.By setting the Ramp Up TimeBy setting the number of test iterations. The Thread Group Control Panel looks like this:Details of each component on the above panel are: Action to be taken after a Sampler error: In case any error occurs during test execution you may let the test either: Continue to the next element in the testStop Thread to stop the current Thread.Stop Test completely, in case you want to inspect the error before continue running. Number of Threads: Simulates the number of user(s) or connection(s) to your server application.Ramp-Up Period: Defines how long it will take JMeter to get all threads running.Loop Count: Defines the number of times to execute the test. Scheduler checkbox Once selected, the Scheduler Configuration section will appear at the bottom of the control panel.Scheduler Configuration You can configure the start and end time of running the test. Controllers JMeter has two types of Controllers: Samplers and Logic Controllers. Samplers Samplers allow JMeter to send specific types of requests to a server. They simulate a user's request for a page from the target server. For example, you can add a HTTP Request sampler if you need to perform a POST, GET, DELETE on a HTTP service Some useful samplers are: HTTP RequestFTP RequestJDBC RequestJava RequestSOAP/XML RequestRPC Requests An HTTP Request Sampler Control Panel looks like the following figure:Answer Here...

View more rss »

Links

View more links »

No messages found
Suggested Pages
Tell your friends >
about this page
 Create a new Page
for companies, colleges, celebrities or anything you like.Get updates on MyPage.
Create a new Page
 Find your friends
  Find friends on MyPage from