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?
At least once in our lifetime, while working in IT, we have read an article or a book where “time management” or “energy management” were mentioned, or at least used a planner to organize, prioritize and plan the tasks. Time management and Energy management are not new concepts, but they still influence our daily lives.
Within the testing and software development world, there seems to be a confusion about what Quality Assurance, Quality Control, Checking and Testing refer to. I will show you the differences through my eyes and experience.
You just launched an application on the market, all champagnes start popping, everybody is happy. The DevOps come to see you the next day. Nothing is pink anymore. The application stopped several times during the night due to overload. To make things even more complicated, they cannot identify the reason why the application crashed.
It seems a new test framework is gaining traction on the internet (especially in the Java area) reviving the concept of BDD. Cucumber is a software tool for running automated acceptance tests in a business-readable domain-specific language. BDD or Behavior-Driven Design, however, has been around for a while, the first articles and projects (JBehave and RSpec appearing in 2007. As mentioned on the site of the project, Cucumber is a rewriting of the previous two frameworks.