Blog

Creating software testing documentation may seem to be boring, but this doesn’t mean that you can simply skip this part of your project. Sometimes the documentation is the only way to save and share information about the product. Test Cases vs Checklists There are several types of the documentation: checklists and test cases. Cases are extremely detailed and heavy and take a lot of time. Besides, bugs can adapt to tests, and cases increase the possibility of this problem. Checklists give you more flexibility, but their functionality may at some point decrease due to the human factor. Going into details To avoid the mistakes, you can try to make checklists more detailed. Such a strategy will virtually turn them into one giant test case, and it has certain advantages: Both positive and negative cases are covered; Your chances of detecting problems are higher; It’s easier to understand how the software works; Such list covers a lot of user scenarios. Obviously, ...

Just imagine: one day, you, an experienced QA tester who knows everything about testing software, completely switch to managing projects. That’s a good step forward, but being a project manager is not an easy challenge. No worries, we will give you some tips on how to survive. Keep your priorities in order You are not a tester anymore, so pay attention to planning tasks for your team. Don’t forget to communicate with your clients and control the deadlines. Check the status of your project Make sure that all the milestones are delivered. It’s better to do this regularly, between the deadlines. Providing your team with a feedback is a must. Don’t dig into details too much Being aware of everything is great, but when you’re a project manager, you have no need to know ALL the details. Don’t overload yourself - you just have to know where to get the essential detail when necessary. Be responsible for your team You’re not walking alone. You’re a project manager now, a...

Talking about testing probably seems to be a pretty unnatural activity. Why should you waste your precious time on talking, if you can spend it on testing instead? Well, this may work in case you are the last QA tester in the world. But since testing is usually done on the team, it’s important to know how to talk about it in the right way. Here are several things to avoid: Talking as if testing is an easy task. Please, don’t think that testing can be formalized. If you learn nothing while testing the software, you are doing something wrong. Sure, you can still predict certain steps and use some patterns, but this doesn’t mean that testing can always be done in the same way. Counting the cases. No one cares about the number of test cases. Quantity matters, but not in this situation. Instead of counting them, discuss bugs, risks, and other important things. Inability to describe the strategy. A testing strategy is something that must be designed and discussed. It’s a whole se...

We have already talked a lot about quality assurance companies and quality control so that you know that QA and QC are extremely important things. But what does the quality mean? Can we measure it? What hides behind this word? This is a pretty philosophical question. We have no Aristotle or Nietzsche on our team, but we will still give you an answer. We are not philosophers, but cool testers, so we definitely know better. Here are 6 features which your customers would like to find in your high-quality product: Functionality This is the most important feature. Your customers simply want to use your product and get a result, and you have to ensure this. You must predict all the potential scenarios, and make sure that your product is functioning without a problem under any of them. Portability Your product won’t become very popular in case it’s compatible only with a single iOS gadget. Find out what devices your target audience uses, and make sure your product is friendly to them...

Every time you release a new product, you have to make sure that it works properly, and there are no bugs hiding under its stylish design. Quality Assurance and Quality Control are essential parts of this process, and they seem to be pretty similar. But they are not the same. QA: To prevent failures In other words, QA is the maintenance of your product’s level of quality. Its main mission is to improve both development and testing processes, which will allow preventing the occurrence of defects during the development lifecycle. Besides, QA implementation has a beneficial impact on planning and your team’s productivity. QC: To detect failures The mission of QC is to find all the defects AFTER the product was developed and BEFORE it will be released. It allows ensuring that the product meets all the requirements. What is the difference? We guess you have already understood the main distinction: QA is about preventing failures, while QC is all about finding them. QA involves pr...

Let’s imagine – you have just created an amazing mobile app. You have already taken care of mobile testing services and fixed the bugs, so now everything works fine. But it’s not the time to relax, as promotion is the next step you have to take. Here are some tips which will help you to do this. Use Social Media Be easy to discover - such a strategy will increase the number of your app downloads. Do you have Facebook? Instagram? Twitter? If yes, great. If not - better create accounts there. Using social media will allow you to keep in touch with your target audience and inform them about all updates. You can also go for paid advertisement. Create a Promo Video A lot of people don’t watch a movie without watching a trailer - this thing also works with apps. Create a short promo video which will attract the attention of your audience and explain why your mobile application is cool. Involve a Celebrity There are many people who download apps just because of someo...

The mobile market is growing, and nothing can stop its evolution. The diversity of available gadgets is impressive, and manufacturers still surprise us from time to time, creating absolutely new devices. That’s why app developers use emulators sometimes. The thing is that there are too many gadgets to take into consideration, while emulators allow to reduce costs and simplify the process of app testing. But here are several significant reasons to forget about using emulators. So, what is impossible without real devices? Prediction of real occurrences. Some things simply can’t be tested with emulators. For instance, battery consumption. Considering ALL user interactions. Scrolling, zooming, and other interactions can differ according to the devices’ touchscreens. So that you won’t be able to test them efficiently with emulators, which won’t give you a true-to-life environment. Making your users really happy. Mobile app performance testing is a must in case you want to make ...

Apple gadgets are not as essential as air or water, but come on, we can’t deny that these devices have taken over the world. Just look at those lines in Apple stores when a new iPhone is released… So that, iOS app development is a great thing to try. Unfortunately, bugs can spoil even the most interesting app, so make sure that your QA testers check the following things: Beta Testing. It’s a must, as your app won’t get popular if it’s not user-friendly. Cross-device compatibility. Your app must be compatible with different iOS devices. You have to consider sizes of the gadgets, their screen resolutions, etc. Installation - Uninstallation. Before your users start to enjoy your app, they have to install it. If the installation process causes problems, they will just uninstall it, and that’s it. By the way, they should also have no difficulties with removing the app. Battery performance and multitasking effects. If the gadget performs different processes at the s...

Even the most promising software development project is worth nothing in case you decide to skip the testing phase. It’s a crucial stage, and you must never forget about it. Moreover, you should already start thinking about testing while creating the project plan. The main question you have to answer at this point is if you are going to test your software in-house or go for independent testing. In-house option is a great choice if you are developing something absolutely secretive - all the QA activities will be done by your team. But the thing is that you can face project delays, financial unsustainability, and other problems. In this case, Testing-as-a-Service (or TaaS) can be your savior. This is an outsourcing model which implies trusting the software testing to a third-party vendor. Here are some more arguments in favor of TaaS: Flexibility. You can go for either complex software testing services or a single type of testing. Experience. To control the quality of your pro...