The demand for testing Flash/Flex applications has become much more significant during the last few years, indicative of widening use of this technology. Along with this demand came the need for automating tests upon these applications. However, this need raises a few questions and problems, some of which will be discussed in the following article.
This paper describes the problems of using image comparisons in automatic tests and reviews two image processing algorithms, which can be integrated into the existing automatic test tools.
Many people tend to get confused between exploratory testing and Ad-hoc testing. Ad-hoc testing is a way to perform testing randomly, without following a structured test plan and scripts. Usually, the main reason why organizations perform Ad-hoc testing is because time and budget constraints prevent them from complying with the requirements of the scripted testing process, so shortcuts need to be implemented. Completely unplanned random actions on an application are not exploratory testing but simply bad testing (Exploratory Testing by Peter Marshall).
Mobile apps and mobile internet usage is growing exponentially. As more and more companies roll out mobile business-critical applications, such as mobile banking, commerce or health apps, their risk exposure is also on the rise. Alongside the increasing demand from end users for fast service and an excellent user experience, organizations are also busy ensuring compliance with security and privacy laws and regulations. Accordingly, companies require mature mobile testing solutions that allow them to deploy and support their mobile application development in a timely and cost-effective manner, while reducing their risk exposure.
Test automation promises many attractive benefits such as running multiple tests overnight at a click of a button, eliminating mindless work, increasing test coverage, and reducing the cost of testing. So the question is, how do we get started?
KDT is the next generation test automation approach that separates the task of automated test case implementation from the automation infrastructure. Test Language is not a test automation approach. Test Language is a comprehensive test approach that hands over the responsibility of automation plan, design and execution to the functional testers by using a KDT-based solution.
The need for usability testing ranges from a bonus feature all the way to a government mandate, and in many cases is able to make the difference between a successful product and a failed one. As such, it is far from always that the most thorough methods are desired, so sometimes usability has to be handled by the testers, without any actual user input. In this case, we have to try to analyze a subjective measure objectively. To do so, we ask, “What is usability?”
Today, when a telephone system is installed in a new neighborhood, it will always work perfectly. The phone will ring, the line will connect immediately, and people can communicate with each other even if all the neighbors are speaking at the same time. This is because over time and due to algorithms which have been developed, it is known how much hardware is needed to support a specific area. Web technology is very different. There can be a different number of servers, different amounts of resources per server, different and new technologies, many different parameters can be configured to improve performance and naturally code can always be improved. As the number of mission critical application websites increases, there is an increasing need to test these applications in order to ensure and guarantee that the business and marketing needs are met. Because the web does not have the same loyalty as traditional trading, poor performance will let users easily move over to the competition.
As a general idea, availability is a measure of how often the application is available for use. More specifically, availability is a percentage calculation based on how often the application is actually available to handle service requests when compared to the total, planned, available runtime. The formal calculation of availability includes repair time because an application that is being repaired is not available for use.
Mobile users have high performance expectations, whether using a mobile application or accessing a website from a mobile browser. The mobile app marketplaces are filled with competitive offerings; if you want a spot on a customer's smartphone, you have to earn it.
At the same time, you cannot afford to spend months and millions of dollars testing mobile apps before you deploy them. There are too many competitors and the market is growing far too quickly for you to sit on the sidelines; if you’ve yet to join the mobile app playing field, you’re missing out on spreading your services to millions upon millions of potential customers.
In this article, we will look at some of the common issues, challenges, and strategies to tackle performance testing on mobile applications.
As many as 44% of website owners do not test their website to check for such concerns as increased traffic volume or load. In today’s competitive and highly responsive market, it’s unwise for retailers to ignore the necessity of performance testing, especially when their website is sometimes their only means of attaining sales and create a good reputation. Hence, every website manager should adopt a mechanism to monitor their website and its performance 24/7.
Performance testing is widely misunderstood, particularly by executives and managers; these misunderstandings can cause a variety of difficulties, including project failure. Experienced performance testers are a necessity to any testing venture: they will speak your language and guide you through the process of meeting your goals, even if you’re as yet unable to articulate what those goals are. They not only know how to relate to executives in terms of business risks, short- and long-term costs, and implications of schedule adjustment, but they also know how to explain their testing. It is the job of the performance tester to define the conditions under which the goal applies; i.e. to determine the goal's context. Therefore, this goal must address such things as client connection speed, number of people accessing the site, and the types of activities those people are performing.
With many years of experience with our various clients and customers, QualiTest Group has developed a unique approach and exclusive tools (accelerators) for performing web service testing which is unmatched in the industry. Relying on manual regression testing is inefficient and not a good use of Quality Assurance resources. That’s why QualiTest Group has developed its unique web services testing solution based on automatically generated test scripts and test data.
In this white paper, we will explore the process of testing a Content Delivery Network, including all of the individual facets which must be considered and their importance to the network as a whole.
There is little doubt at this point in anyone’s mind that Selenium is seeing wide spread adoption, evident in the fact that even historically reluctant organizations are welcoming this open source tool into their kit. So what is Selenium anyway? Selenium is an open source tool for automating web browsers. That is really all you get and, as many organizations are discovering the hard way, this product tackles the problem of test automation in a radically different way than most other market leading tools of the past and present.
The process and level of effort for building automated tests for terminal-based applications is similar to that of automating tests for applications running on other platforms, including MS Windows and the web.
As more legacy applications are converted to the web or other modern user interfaces, validation of that conversion must be done as part of the testing process. Testing often accounts for a large portion of the project budget and it is often a costly and time consuming process to build tests with traditional testing tools for the modernized version of an application. In addition, testing cannot begin until after conversion which can significantly delay the delivery of the application.