Today, time to market is crucial and errors and bugs are not easily tolerated. Therefore, it is important to deliver high-quality products. As quality assurance is often not the prime focus, because of various constraints such as time, cost, resources, QA is only partially covered. The result is reflected in a negative user experience. Manual testing has reliability issuess, as it is tedious and slow. As an example, by the time a bug is discovered, important details to reproduce it may have already been forgotten. Moreover, manual test results should be well documented by the tester in order to serve as reference to others. For these reasons, testing is a matter of discipline where automation can really help.
At some point, one may be interested in finding out how well-developed the automated test cases which validate the Web Services functionality actually are. In other words, it would be good to know how much the test cases hit the code. One way to test the Web Services functionality is by using SOAP UI. This article describes how we can use the Squish Coco application to determine how much the SOAP UI test cases impact the C# code.
We already know that millions of people from around the world use mobile phones and tablets, and the number of users is on the rise. This also determines the exponential growth of the global mobile applications market.Companies which develop mobile applications must ensure that they deliver high-quality products and that they stand out from the crowd in order to receive good feedback from customers. This has become a challenge, considering the diversity of mobile devices and operating systems. To ensure large and efficient coverage, these applications must undergo automated testing. This is the reason why generic solutions must be found, namely solutions that cover the testing of the applications to the greatest possible extent.
All new features determine us to add a couple of new cases to one or multiple data providers. What happens when you have two, three or more features that need the adding of various details to data providers? Eventually the data providers from the tests will get bigger and harder to follow. Let’s say we have an online store application that can be used for purchasing items with one type of account (regularAccount) and this store is available for 3 domains. This online store offers only English localization.
In a general, as a widely accepted definition, quality of a product is the main characteristic that differentiates that aforementioned product in relation to other, similar products available on the market. Quality implies meeting the customer’s expectations, at a cost that the customer affords (or: agrees) to pay, so that we, as a provider of goods or services, will be able to do this the next day and the day after that. A bug-free product is not necessarily a good-quality product. Quality is as good as its perception by the end-users, as good as meeting the end-users’ expectations. Of course, a bug-free product is more likely to be perceived as a good one, but that’s just part of the whole picture. This is an important part, no one could argue about, but just one part of the picture. “Quality Assurance” is the set of activities aiming to build quality into our final product. It consist of preventive and corrective actions that ensure us and our customers that the product we deliver meets their expectations. Customers’ expectations derive from the intended use of our product and from various legal or industry standards.
Do you want an application that automatically starts up your favorite or most indispensable applications? Write an AutoIt script! It will ease your routines and launch everything you need for work while you enjoy your morning coffee. While there are many great automation tools like Selenium, Sikuli, AutoHotkey available, AutoIt is easy to learn, it is freeware and it is fast – perfect for task automation based on GUI and for carrying out all kinds of tests related to performance!
I’m sure everyone who’s worked in a software company has, at least once, heard this question or maybe even thought about it. Analyzing a bit further, it becomes obvious that the question makes no sense as the two types of tests don’t perform the same function. We need acceptance tests, and in modern times we’d like them to be automated. The actual question you might have heard is “Who will implement the acceptance tests?” and the answer to this will vary depending on your company / team direction. In my opinion, which happens to coincide with the company’s and the team’s opinion (yey!), everyone in the team should do it.
Every four years during the Olympic Games we admire the athletes who are going beyond their limits, who establish new records and bring glory to their team and country. We consider them experts in what they do and some of us know the struggle, hard work and the sacrifices they make to reach the top of the podium. Similarly to athletes, individuals, who want to be the best in their profession, need to go through a long journey from beginner to expert.
The Testing Map aims at covering, in visual form, the most important information a software tester should know. There is one area which tackles processes in particular. I will talk about this area in the lines that follow.
As applications and systems grow larger and more complex, test automation is moving beyond a luxury and becoming a necessity for them. As technology changes, testing must also change and adapt. So start small, by using different approaches on a small scale to see what works best before attempting to spread further. Successful test automation needs both ingenuity and perseverance. What are the main factors that contribute to success in test automation? What common factors most often lead to the failure of an automation effort?