Reducing a test set without losing coverage of major test cases is one of the main goals of any tester working on test design. In this article, we will discuss how to reduce the number of tests without losing major ones using the analysis of interconnections and the inner logic of a product. This article will be mainly useful for testers who often test different windows with a number of interconnected options and parameters.
So let’s see to which products and how we can apply the analysis of interconnections…
The most of testers at least once performed testing for compatibility of the developed application with the antiviruses. It’s widely known that antivirus software influences significantly the system functioning and also the work of the particular programs, and nowadays, the antivirus is almost must-have part of the computer system. Moreover, there are a lot of diverse malware protection products, and sometimes they can be unpredictable.
So, to adequately check the product for the compatibility with the antivirus software, you should apply some creative approaches. It is natural that you’ll need some knowledge for that – this is what we aim in this article.
In the first part of this article, we’ll consider the main types of antivirus programs, their features and specialties, and also the current statistics of antivirus product popularity. This is the theoretical minimum that a tester should know to start planning and performing antivirus compatibility testing. In the second part, we’ll discuss the role of such testing and its place in the software product life cycle, and also consider the problem situations that can appear during compatibility testing. This information is especially useful when planning and performing tests.
This article is for those who write or are going to write functional tests for any programs. The goal of this article is to give the flavor of the main techniques of test design and also to answer the question: What method is better to choose for testing your project?
When you first meet the concept of the exploratory testing you can think that its name fully exposes the sense of this sort of activity. But if you get a little bit deeper – this confidence weakens and disappears. Especially clear it can be seen when balancing between the concepts of the exploratory and wild testing, which in one hand are synonyms in QA industry, and in another (from the good sense point of view) – contrary one to another. It’s because what can have in common the exploration – serious, responsible and well-organized process – and something wild and chaotic, that is wild testing?
In this article, we will tell you our own way of Impact Analysis introduction and work with it. Why did we decide to introduce Impact Analysis in software testing in our teams? What practical benefit from this innovation have we got and are getting today? You will get answers to these and many other questions concerning this topic while reading this material.
This article is intended to provide full and detailed description of deployment of automated testing system consisting of Team Foundation Server + Microsoft Test Manager + System Center Virtual Machine Manager.
This article may be useful for Automated Testing Specialists and System Administrators.
In the process of creation of a successful software product, there is an inevitable problem of finding a balance between the quality and the release date of the software product. The testing allows obtaining a product that satisfies all requirements. But the covering of each product risk with various test cases and compiling them take too long. The correctly prepared testing process should provide a required quality level without exceeding project time and budget . If the time for testing was estimated wrongly, it can lead you either to the late product delivery, or to the decrease of its quality and competitiveness . The software testing estimation is a rather complicated and volumetric process but its significance for the creation of the successful project shouldn’t be underestimated.
This article contains recommendations on how to do software testing estimation, which, we hope, can help you to obtain more realistic and functional QA time estimates for a new project.
This article can be useful for those testers who configure their test environment themselves without the help of the system administrator. The aim of the article is to present a step-by-step description of the installation and configuration of the domain controller, Exchange Server, and MS Outlook with two accounts for the testing purposes.
This article comes from the personal experience. I tested an application that worked with a “living” Exchange system. For testing, I needed a real Exchange server through which it would be possible to send and receive mail for checking different test cases. My task was to find the most optimal configuration of the test environment to configure everything quickly on the one hand and to simulate a relatively real situation on the other hand.
In the simplest case, it is enough to have one machine – real or virtual. Then, there can be variations: to make it more trustworthy, we can use 3 real machines – server and two clients in a separate sub-network. The installation and configuration of the software will not differ much.
In this article we will talk about the file systems and files, but the most attention will be focused on the key points of testing of software that works with NTFS and FAT file systems.
At the end we will give our check list for testing of software, working with the FAT and NTFS file systems - we hope that it will help you in development of testing plan for your software.