Interview Questions, Answers and Tutorials

Blog

Bottom Up Integration 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. In this approach, testing is conducted from the submodule to the main module, if the main module is not developed a temporary program called DRIVERS is used to simulate the main module. Advantages: * Advantageous if major flaws occur toward the bottom of the program. * Test conditions are easier to create. * Observation of test results is easier. Disadvantages: * Driver Modules…

Branch testing

Branch Testing/ Decision Coverage:   Test coverage criteria require enough test cases such that each condition in a decision takes on all possible outcomes at least once, and each point of entry to a program or subroutine is invoked at least once. That is, every branch (decision) taken each way, true and false. It helps in validating all the branches in the code making sure that no branch leads to abnormal behavior of the application. Formula: Branch Testing=(Number of decisions outcomes tested / Total Number of decision Outcomes) x 100 % A branch is the outcome of a decision, so branch…

Accessibility Testing

What is Accessibility Testing? Accessibility testing is the technique of making sure that your product is accessibility compliant. There could be many reasons why your product needs to be accessibility compliant as stated above.  Accessibility testing is a type of systems testing designed to determine whether individuals with disabilities will be able to use the system in question, which could be software, hardware, or some other type of system. Disabilities encompass a wide range of physical problems, including learning disabilities as well as difficulties with sight, hearing, and movement.   Why accessibility Testing?Typical accessibility problems can be classified into the…

Acceptance testing

Acceptance testing, a testing technique performed to determine whether or not the software system has met the required 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…

Adhoc Testing

    Adhoc testing is an informal testing type 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 the application. The main aim of this testing…

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 PlanStart 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 a 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…

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 set up the database: Create a database with the name “tutorial”. Create a table tutorials_tbl. Insert records into tutorials_tbl : mysql> use TUTORIALS; Database changed mysql> 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…

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 the performance of one web page say a page is shown by the URL:https://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 the test…

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 other elements: Sampler, Logic Controller, Configuration Element, Listener, and Timer. Each Sampler can be preceded by one or more Pre-processor elements, followed by a 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…

JMeter Tutorial – Build Test Plan

What is a Test Plan? A Test Plan defines and provides a layout of how and what to test. For example the web application as well as the client-server application. It can be viewed as a container for running tests. A complete test plan will consist of one or more elements such as thread groups, logic controllers, sample-generating controllers, listeners, timers, assertions, and configuration elements. A test plan must have at least one thread group. We shall discuss these elements in detail in the next chapter Test Plan Elements.  Follow the below steps to write a test plan:  Start the JMeter…