Software Testing
more_horiz
close

on 19th December 2016 / by smitha.vn
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 *
close

on 24th November 2016 / by Sarin S R
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 *
more_horiz
close

on 23rd November 2016 / by samantha.gomez
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 *
more_horiz
close

on 23rd November 2016 / by Vyshnavi.J
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 *
close

on 21st October 2016 / by Urmila.cm
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 *
close

on 06th April 2016 / by Sarin S R
Zyxware as an organisation is trying to introduce cost effective measures that can save time, resources and bring value to client, as part of that we have introduced automation of checkout process in Drupal Ubercart. On the analysis made in many ecommerce website we have come to the conclusion that checkout process is the main functional flow that is critical to client and it was to be automated to keep a check on the stability of checkout process flow. Stability of checkout process is of main concern because that is what will be directly relating to online sales/marketing of online products. We have automated the below checkout scenarios in Drupal Ubercart using Selenium: Checkout process for web user Checkout process for Authenticated user Paypal Checkout process for web user Paypal Checkout process for Authenticated user All the four scenarios include: Selecting a product Adding the selected product to cart Procedding to checkout process Enetring the shipping details Making Payment Complete the transaction These scripts can be used as a check on checkout process repeatedly to keep track of the stability of checkout. The scripts developed can be easily modified according to requirement or any alteration needed. Also the script can be imported to java, ruby, python etc which in turn can be run on webdriver to bring unlimited flexibility to the automation process. If you need any further assistance, please feel free to get in touch with us. Software Testing Drupal Ubercart Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 31st March 2016 / by tiju.thomas
Cross browser testing is the type of testing in which testers ensure that the application is compatible to latest versions of the commonly used browsers (commonly used browsers list can be obtained from browser statistics). Google Chrome, Mozilla Firefox, and Internet Explorer are some of them. This article includes a checklist that can be referred while performing the cross browser testing. Checklist: The alignment of the items in a webpage is correct. The color, font size of the elements in a webpage are as expected. Ensure the layout of the page. The spacing between the items in a webpage. The styles/ effects given are reflecting in all browsers. Make sure that the videos are working. Make sure that the image uploading , file uploading etc are working. Make sure that the links are working. Make sure that Always update your browsers prior to testing and working of the check boxes. Make sure that the look and feel of the fields given for uploading any images or files. Make sure that the file downloads are working. Make sure that the buttons working. Make sure that all the images are getting loaded. Make sure that the links are properly navigated. Make sure that the application performance. The above points to be ensured while performing cross browser testing. Always update your browsers prior to testing. Also, you may refer other articles related to testing over here. Software Testing Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 20th August 2015 / by tiju.thomas
Whenever you play back the recorded test cases in Selenium, the http secured websites will displayed an authentication popup window and it prompt you to enter the http user name and the password and it will not allow to perform any further operations until you provide username and password. Lets checkout the solution. The solution for the situation is that, when you record a website using selenium IDE, In the recording window, you should change the Base URL as in the following format, http://<httpusername><password>@<sitename> Eg: http://testuser:user0123@testsite.com For more information, contact us now. Do you need any support from us, get a quote. I hope the above description was helpful for you. Thank you. Software Testing Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 19th August 2015 / by rajula.s
Firebug, an extension of Mozilla browser is a very helpful tool to find the spacing between elements, padding, border and margin, font, font size and color of the text and many other things in a webpage. This article talks about the basic things we can perform using firebug in a tester's point of view. Open Firebug To open the firebug go to Tools > Web developer > Firebug or simply press F12 in the keyboard. To check an element click the inspect button (image of a lens or small arrow) and click on the element in the webpage. On clicking the element you can see that it is getting highlighted. You can see the details of that element like style, layout etc in the right most session. Firebug to find the measurements If you want to know the measurements given for an element, you can either click on the layout tab in the right most portion of the firebug panel or check the details displayed under the style tab. The layout gives the margin, border and padding given and the under the styles tab you can get the details like border, height, width etc. You can also edit the given height, width and try out and ensure the look and feel of the page. For checking the font, font size and color Suppose you want to know the font, font size and color of a text, inspect the text and click on the tab titled computed. Here you can get details like font family, font size, font weight, color etc. Here, also you can edit the size and check the readability of the text. For checking image On inspecting an image, you can see that the image is represented as src= "imagename.extension". We can view that image by right clicking on the name and select the option 'open in new tab'. Now you can also save the image by right clicking the image opened in the new tab. Like this, different things that we can do in a browser which are very interesting and may be helpful for testing, checkout other testing tips, and always be in touch with us. If you want any testing help, connect with us. Software Testing Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 19th August 2015 / by anoop.v
ETL or Data warehouse testing is quite different with regular testing. There are lot of challenges are facing while performing ETL or Data warehouse testing. Do you need a testing expert or want help in your business, just click here to hear from us. The main challenges of ETL or Data warehouse testing includes : Data loss during ETL testing. Duplicate data and Incompatibility. Lack of inclusive test bed. Testers have no benefits to execute ETL jobs by their own. Data volume and complexity is huge. Inefficient in procedures and business process. Inconvenience securing and building test data. Absence of business course information. Data plays a very important role in business to make business decisions. ETL testing plays a notable role in reliability, consistent and validation process. For more information, click here Software Testing Leave a reply Your email address will not be published. Required fields are marker * anjani (not verified) access_time 23 May 2019 - 10:22 Target is EDWSMDM Destination is Fact Loe_Bd_customers1 staging = get all leads associated with campaigns that have upplier-di=12004 In thi scenario,how can i identify what is the source and the target and how to writ the SQL query for this,iam new to etl testing,and very confused. please advise,help Add new comment