TestLodge is a test management tool which is used to store information such as how testing is to be done, plan the testing activities and report the status of quality assurance activities. It has reasonable price plans and can be used owning to its simple interface and its non-complexity. The system focuses on creation and maintenance of test plans, map the requirements, execute the test cases and generating reports based on the results. It offers the following features to the users: TestLodge allows the creation and maintenance of test plans.The test plans can either be built from beginning or from the template that TestLodge provides. It allows mapping requirements against the test cases. It allows entering a title, description, test steps and expected result for each test case. After creating the test cases TestLodge provides a clear interface that guides the tester through each test one by one. TestLodge provides a simple interface for testers to manage the test process and thereby making their work easy. It helps to avoid the trouble of using multiple applications also. Please feel free to get in touch with us if you need any further assistance. Software Testing Leave a reply Your email address will not be published. Required fields are marker *

Speed of page load is determined by how fast the page loads when the URL for the page is called.This involves loading of all the components for the webpage. These elements will affect the page load time for a webpage. This includes images, CSS, JavaScript files etc. Load time is also affected by factors like the type of the server used for hosting, the bandwidth allocated to browse the site, the geographic location of the user etc. To improve the user experience and to sustain users to the website it is recommended to have page load time to be optimized. Commonly used Tools to check webpage load time are : http://www.webtoolhub.com https://tools.pingdom.comer http://sitespeed.me/en/tracer These can be used to measure page load time in terms of : Location of user. Connection speed. Amount of data/time required to load CSS files, Javascript files, images. Software Testing Performance Testing Leave a reply Your email address will not be published. Required fields are marker *

The context-driven software testing methodology suggests for continuous and creative evaluation of testing opportunities. It is a testing way that conforms to the context of the project, more than applying a best practice. For context-driven, a good tester should ask as many questions as possible to reveal not only parts of the context but should know about the act of information. Context-driven methodology is similar to the agile process. It is implemented when the end-users have different preference and needs. Eg: Notepad is an ideal application for writing simple text. But if other users want the tools to add graphics and different font size and colors, then this application is not for them. So context-driven testing is based on the fact that ‘no solution is the best solution’. But in this case, the advantage lies with the end user, since the final product that is delivered is a user-friendly product, which is the main aim of Context-driven testing. This methodology works better in stable applications where conditions seldom change and also where test scenarios are not known. Why do we need Context-driven testing? Most of the times, programmers are not given a proper well document which explains them exactly how to do the work they are supposed to do, as well as testers also will not be provided with complete documents. So that they would not know the complete proper requirement. But, they may have a spec or a basic document like BRD or some reference documents that tells them what they need to do. But it is assumed they will figure out the best way to accomplish the task. So Context-driven testing is introduced in a situation like this. Techniques used for Context-Driven Testing Exploratory testing Grey Box testing Seven Principles of Context-driven testing:- The practice of workflow depends on its context. There are good practices, but no best practices in context. People working together are the most important part of the concern project context. Projects of time overriding in ways that are often not predictable. The product is a solution in a concept that if the problem is not solved, the product doesn't work. Good software testing is a challenging process. Only through judgment and skill, we are able to do the right things at the right times to effectively test our products. If you need any further assistance, please feel free to get in touch with us. Software Testing Leave a reply Your email address will not be published. Required fields are marker *

Network emulation is used for testing the performance of real applications over a virtual network. It is the act of introducing a device to a test network that alters packet flow in such a way as to mimic the behavior of a network. Netem is a network emulator tool provides functionality for testing protocols. It will emulate the network properties of wide-area networks. Netem is already enabled in the kernel and a current version of iproute2. The netem kernel component is enabled under: Networking Networking Options QoS and/or fair queuing Network emulator Iproute2 is a collection of utilities for controlling TCP/IP networking and traffic control in Linux. Netem is controlled by the command line tool 'tc' and it is part of the iproute2 package of tools. Commands for network emulation: Note: Here, I have used ethe1 for the interface in the examples below; you should use the name of your specific Ethernet card To add constant delay to every packet going out through a specific interface: $tc qdisc add dev ethe1 root netem delay 80ms A ping test to this host should show an increase of 80ms in the delay to replies. To add random variance$tc qdisc change dev ethe1 root netem delay 80ms 10ms The following command will add +/- 10 ms of jitter to the 80ms of delay:$tc qdisc add dev ethe1 root netem delay 80ms 10ms To turn off/delete the qdisc from a specific interface (in this case, ethe1):$tc qdisc del dev ethe1 root Typically, the delay in a network is not uniform. It is more common to use a normal distribution to describe the variation in delay. Netem can accept a non-uniform distribution:$tc qdisc change dev ethe1 root netem delay 100ms 20ms distribution normal Please get in touch with us if any queries Software Testing Leave a reply Your email address will not be published. Required fields are marker *

In Selenium Webdriver, a browser session can be closed using two webdriver commands: close() and quit(). The situations in which they are used are briefly explained below: close() close() is a webdriver command which closes the browser window which is currently in focus. During the automation process, if there are more than one browser window opened, then the close() command will close only the current browser window which is having focus at that time. The remaining browser windows will not be closed. The following code can be used to close the current browser window: driver.close() //where, ‘driver’ is the Webdriver object. quit() quit() is a webdriver command which calls the driver.dispose method, which in turn closes all the browser windows and terminates the WebDriver session. If we do not use quit() at the end of program, the WebDriver session will not be closed properly and the files will not be cleared off memory. This may result in memory leak errors. The following code can be used to close all the browser windows: driver.quit() //where, ‘driver’ is the Webdriver object.If the Automation process opens only a single browser window, the close() and quit() commands work in the same way. Both will differ in their functionality when there are more than one browser window opened during Automation. Hope you find this tips useful. Please feel free to get in touch with us for any queries. Software Testing Selenium Leave a reply Your email address will not be published. Required fields are marker *