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!


All Updates

No Detailed Information available.

No feeds found

Posting your question. Please wait!...


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


03:24 PM - 27 Feb 15

Manual Testing Questions and Answers

1. What is Acceptance Testing? Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria. 2. What is Accessibility Testing? Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.). 3. What is Ad Hoc Testing? A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing. 4. What is Agile Testing? Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development. 5. What is Application Binary Interface (ABI)? A specification defining requirements for portability of applications in binary forms across different system platforms and environments. 6. What is Application Programming Interface (API)? A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services. 7. What is Automated Software Quality (ASQ)? The use of software tools, such as automated testing tools, to improve software quality. 8. What is automated Testing? Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions. 9. What is Backus-Naur Form? A met language used to formally describe the syntax of a language. 10. What is Basic Block? A sequence of one or more consecutive, executable statements containing no branches. 11. What is Basis Path Testing? A white box test case design technique that uses the algorithmic flow of the program to design tests. 12. What is Basis Set? The set of tests derived using basis path testing. 13. What is Baseline? The point at which some deliverable produced during the software engineering process is put under formal change control. 14. What you will do during the first day of job? What would you like to do five years from now? 15. What is Beta Testing? Testing of a rerelease of a software product conducted by customers. 16. What is Binary Portability Testing? Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification. 17. What is Black Box Testing? Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component. 18. What is Bottom up Testing? An approach to integration testing where the lowest level components are tested first then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested. 19. What is Boundary Testing? Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests). 20. What is Bug? A fault in a program, which causes the program to perform in an unintended or unanticipated manner. 20. What is Defect? If software misses some feature or function from what is there in requirement it is called as defect. 21. What is Boundary Value Analysis? BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001. 22. What is Branch Testing? Testing in which all branches in the program source code are tested at least once. 23. What is Breadth Testing? A test suite that exercises the full functionality of a product but does not test features in detail. 24. What is CAST? Computer Aided Software Testing. 25. What is Capture/Replay Tool? A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools. 26. What is CMM? The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes. 27. What is Cause Effect Graph? A graphical representation of inputs and the associated outputs effects which can be used to design test cases. 28. What is Code Complete? Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented. 29. What is Code Coverage? An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention. 30. What is Code Inspection? A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards. 31. What is Code Walkthrough? A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions. 32. What is Coding? The generation of source code. 33. What is Compatibility Testing? Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware. 34. What is Component? A minimal software item for which a separate specification is available. 35. What is Component Testing? Testing of individual software components (Unit Testing). 36. What is Concurrency Testing? Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores. 37. What is Conformance Testing? The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard. 38. What is Context Driven Testing? The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now. 39. What is Conversion Testing? Testing of programs or procedures used to convert data from existing systems for use in replacement systems. 40. What is Cyclomatic Complexity? A measure of the logical complexity of an algorithm, used in white-box testing.41. What is Data Dictionary? A database that contains definitions of all data items defined during analysis. 42. What is Data Flow Diagram? A modeling notation that represents a functional decomposition of a system. 43. What is Data Driven Testing? Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing. 44. What is Debugging? The process of finding and removing the causes of software failures. 45. What is Defect? Nonconformance to requirements or functional / program specification 46. What is Dependency Testing? Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality. 47. What is Depth Testing? A test that exercises a feature of a product in full detail. 48. What is Dynamic Testing? Testing software through executing it. See also Static Testing. 49. What is Emulator? A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system. 50. What is Endurance Testing? Checks for memory leaks or other problems that may occur with prolonged execution51. What is End-to-End testing? Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate. 52. What is Equivalence Class? A portion of a component's input or output domains for which the component's behavior is assumed to be the same from the component's specification. 53. What is Equivalence Partitioning? A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes. 54. What is Exhaustive Testing? Testing which covers all combinations of input values and preconditions for an element of the software under test. 55. What is Functional Decomposition? A technique used during planning, analysis and design; creates a functional hierarchy for the software. 54. What is Functional Specification? A document that describes in detail the characteristics of the product with regard to its intended features. 55. What is Functional Testing? Testing the features and operational behavior of a product to ensure they correspond to its specifications. Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions. or Black Box Testing. 56. What is Glass Box Testing? A synonym for White Box Testing. 57. What is Gorilla Testing? Testing one particular module, functionality heavily. 58. What is Gray Box Testing? A combination of Black Box and White Box testing methodologies? testing a piece of software against its specification but using some knowledge of its internal workings. 59. What is High Order Tests? Black-box tests conducted once the software has been integrated. 60. What is Independent Test Group (ITG)? A group of people whose primary responsibility is software testing. 61. What is Inspection? A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection). 62. What is Integration Testing? Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems. 63. What is Installation Testing? Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions. 64. What is Load Testing? See Performance Testing. 65. What is Localization Testing? This term refers to making software specifically designed for a specific locality. 66. What is Loop Testing? A white box testing technique that exercises program loops. 67. What is Metric? A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code. 68. What is Monkey Testing? Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out. 69. What is Negative Testing? Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing. 70. What is Path Testing? Testing in which all paths in the program source code are tested at least once. 71. What is Performance Testing? Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing". 72. What is Positive Testing? Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing. 73. What is Quality Assurance? All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer. 74. What is Quality Audit? A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives. 75. What is Quality Circle? A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality. 76. What is Quality Control? The operational techniques and the activities used to fulfill and verify requirements of quality. 77. What is Quality Management? That aspect of the overall management function that determines and implements the quality policy. 78. What is Quality Policy? The overall intentions and direction of an organization as regards quality as formally expressed by top management. 79. What is Quality System? The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management. 80. What is Race Condition? A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access. 81. What is Ramp Testing? Continuously raising an input signal until the system breaks down. 82. What is Recovery Testing? Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions83. What is Regression Testing? Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made. 84. What is Release Candidate? A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released). 85. What is Sanity Testing?Brief test of major functional elements of a piece of software to determine if it’s basically operational. See also Smoke Testing. 86. What is Scalability Testing? Performance testing focused on ensuring the application under test gracefully handles increases in work load. 87. What is Security Testing? Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level. 88. What is Smoke Testing? A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire. 89. What is Soak Testing? Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed. 90. What is Software Requirements Specification? A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software.91. What is Software Testing? A set of activities conducted with the intent of finding errors in software. 92. What is Static Analysis? Analysis of a program carried out without executing the program. 93. What is Static Analyzer? A tool that carries out static analysis. 94. What is Static Testing? Analysis of a program carried out without executing the program. 95. What is Storage Testing? Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage. 96. What is Stress Testing? Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load. 97. What is Structural Testing? Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing. 98. What is System Testing? Testing that attempts to discover defects that are properties of the entire system rather than of its individual components. 99. What is Testability? The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met. 100. What is Testing? The process of exercising software to verify that it satisfies specified requirements and to detect errors. The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829). The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. What is Test Automation? It is the same as Automated Testing. 101. What is Test Bed? An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used. 102. What is Test Case? Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Test Driven Development? Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code. 103. What is Test Driver? A program or test tool used to execute tests. Also known as a Test Harness. 104. What is Test Environment? The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers. 105. What is Test First Design? Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test. 106. What is Test Harness? A program or test tool used to execute tests. Also known as a Test Driver. 107. What is Test Plan? A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. 108. What is Test Procedure? A document providing detailed instructions for the execution of one or more test cases. 109. What is Test Script? Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool. 110. What is Test Specification? A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests. 111. What is Test Suite? A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test. 112. What is Test Tools? Computer programs used in the testing of a system, a component of the system, or its documentation. 113. What is Thread Testing? A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels. 114. What is Top Down Testing? An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested. 115. What is Total Quality Management? A company commitment to develop a process that achieves high quality product and customer satisfaction. 116. What is Traceability Matrix? A document showing the relationship between Test Requirements and Test Cases. 117. What is Usability Testing? Testing the ease with which users can learn and use a product. 118. What is Use Case? The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities. 119. What is Unit Testing? Testing of individual software components. 120. how do the companies expect the defect reporting to be communicated by the tester to the development team. Can the excel sheet template be used for defect reporting. If so what are the common fields that are to be included ? who assigns the priority and severity of the defect To report bugs in excel: Sno. Module Screen/ Section Issue detail SeverityPrioriety Issuestatusthis is how to report bugs in excel sheet and also set filters on the Columns attributes.But most of the companies use the share point process of reporting bugs In this when the project came for testing a module wise detail of project is inserted to the defect managment system they are using. It contains following field1. Date2. Issue brief3. Issue discription(used for developer to regenrate the issue)4. Issue satus( active, resolved, onhold, suspend and not able to regenrate)5. Assign to (Names of members allocated to project)6. Prioriety(High, medium and low)7. Severity (Major, medium and low)  121. How do you plan test automation? 1. Prepare the automation Test plan2. Identify the scenario3. Record the scenario4. Enhance the scripts by inserting check points and Conditional Loops5. Incorporated Error Hnadler6. Debug the script7. Fix the issue8. Rerun the script and report the result122. Does automation replace manual testing? There can be some functionality which cannot be tested in an automated tool so we may have to do it manually. therefore manual testing can never be repleaced. (We can write the scripts for negative testing also but it is hectic task).When we talk about real environment we do negative testing manually. 123. How will you choose a tool for test automation? choosing of a tool deends on many things ...1. Application to be tested2. Test environment3. Scope and limitation of the tool.4. Feature of the tool.5. Cost of the tool.6. Whether the tool is compatible with your application which means tool should be able to interact with your appliaction7. Ease of use 124. How you will evaluate the tool for test automation? We need to concentrate on the features of the tools and how this could be benficial for our project. The additional new features and the enhancements of the features will also help. 125. How you will describe testing activities? Testing activities start from the elaboration phase. The various testing activities are preparing the test plan, Preparing test cases, Execute the test case, Log teh bug, validate the bug & take appropriate action for the bug, Automate the test cases. 126. What testing activities you may want to automate? Automate all the high priority test cases which needs to be exceuted as a part of regression testing for each build cycle. 127. Describe common problems of test automation. The commom problems are:1. Maintenance of the old script when there is a feature change or enhancement2. The change in technology of the application will affect the old scripts 128. What types of scripting techniques for test automation do you know? 5 types of scripting techniques:LinearStructuredSharedData DrivenKey Driven 129. What is memory leaks and buffer overflows ? Memory leaks means incomplete reallocation - are bugs that happen very often. Buffer overflow means data sent as input to the server that overflows the boundaries of the input area, thus causing the server to misbehave. Buffer overflows can be used. 130. What are the major differences between stress testing,load testing,Volume testing? Stress testing means increasing the load ,and cheking the performance at each level. Load testing means at a time giving more load by the expectation and cheking the performance at that leval. Volume testing means first we have to apply initial.Answer Here...
03:08 PM - 27 Feb 15

Acceptance testing

Acceptance testing, a testing technique performed to determine whether or not the software system has met the requirement specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it is has met the required criteria for delivery to end users. After the system test has corrected all or most defects, the system will be delivered to the user or customer for acceptance testing.Acceptance testing is basically done by the user or customer although other stakeholders may be involved as well. The goal of acceptance testing is to establish confidence in the system.Acceptance testing is most often focused on a validation type testing.Acceptance testing may occur at more than just a single level, for example:A Commercial Off the shelf (COTS) software product may be acceptance tested when it is installed or integrated.Acceptance testing of the usability of the component may be done during component testing.Acceptance testing of a new functional enhancement may come before system testing. Types of Acceptance Testing: User Acceptance test: The User Acceptance test focuses mainly on the functionality thereby validating the fitness-for-use of the system by the business user. The user acceptance test is performed by the users and application managers. Operational Acceptance test: The Operational Acceptance test also known as Production acceptance test validates whether the system meets the requirements for operation. In most of the organization the operational acceptance test is performed by the system administration before the system is released. The operational acceptance test may include testing of backup/restore, disaster recovery, maintenance tasks and periodic check of security vulnerabilities.Contract Acceptance testing: It is performed against the contract’s acceptance criteria for producing custom developed software. Acceptance should be formally defined when the contract is agreed.Compliance acceptance testing: It is also known as regulation acceptance testing is performed against the regulations which must be adhered to, such as governmental, legal or safety regulations. Acceptance Criteria:  Acceptance criteria are defined on the basis of the following attributes Functional Correctness and CompletenessData IntegrityData ConversionUsabilityPerformanceTimelinessConfidentiality and AvailabilityInstallability and UpgradabilityScalabilityDocumentation Acceptance Test Plan:The acceptance test activities are carried out in phases. Firstly, the basic tests are executed, and if the test results are satisfactory then the execution of more complex scenarios are carried out. The Acceptance test plan has the following attributes: IntroductionAcceptance Test Categoryoperation EnvironmentTest case IDTest TitleTest ObjectiveTest ProcedureTest ScheduleResources Acceptance Test Report: The Acceptance test Report has the following attributes: Report IdentifierSummary of ResultsVariationsRecommendationsSummary of To-DO ListApproval DecisionAnswer Here...
02:43 PM - 27 Feb 15

Adhoc Testing

Adhoc testing is an informal testing type with an aim to break the system. This testing is usually an unplanned activity . It does not follow any test design techniques to create test cases. In fact is does not create test cases altogether! This testing is primarily performed if the knowledge of testers in the system under test is very high. Testers randomly test the application without any test cases or any business requirement document.Adhoc Testing does not follow any structured way of testing and it is randomly done on any part of application. Main aim of this testing is to find defects by random checking. Adhoc testing can be achieved with the testing technique called Error Guessing. Error guessing can be done by the people having enough experience on the system to "guess" the most likely source of errors. This testing requires no documentation/ planning /process to be followed. Since this testing aims at finding defects through random approach, without any documentation, defects will not be mapped to test cases. Hence, sometimes, it is very difficult to reproduce the defects as there are no test-steps or requirements mapped to it.  When execute Adhoc Testing?Adhoc testing can be performed when there is limited time to do elaborative testing. Usually adhoc testing is performed after the formal test execution. And if time permits, adhoc testing can be done on the system).Adhoc testing will be effective only if the tester is knowledgeable of the System Under Test. Types of adhoc testing There are different types of Adhoc testing and they are listed as below:Buddy Testing: Two buddies, one from development team and one from test team mutually work on identifying defects in the same module. Buddy testing helps the testers develop better test cases while development team can also make design changes early. This kind of testing happens usually after completing the unit testing. Pair Testing: Two testers are assigned the same modules and they share ideas and work on the same systems to find defects. One tester executes the tests while another tester records the notes on their findings.Monkey Testing: Testing is performed randomly without any test cases in order to break the system.   Best practices of Adhoc testingFollowing best practices can ensure effective Adhoc Testing. Good business knowledgeTesters should have good knowledge of the business and clear understanding of the requirements- Detailed knowledge of the end to end business process will help find defects easily. Experienced testers find more defects as they are better at error guessing. Test Key ModulesKey business modules should be identified and targeted for adhoc testing.. Business critical modules should be tested first to gain confidence on the quality of the system. Record DefectsAll defects need to be recorded or written in a notepad . Defects must be assigned to developers for fixing. For each valid defect ,corresponding test cases must be written & must be added to planned test cases. These defect findings should be made as lesson learned and these should be reflected in our next system while we are planning for test cases.Conclusion: The advantage of Adhoc testing is to check for the completeness of testing and find more defects then planned testing. The defect catching test cases are added as additional test cases to the planned test cases. Adhoc Testing saves lot of time as it doesn't require elaborate test planning , documentation and test case design.Answer Here...
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/ 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: 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: 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...

View more rss »


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