Combinatorial testing is a difficult problem. Having to test a small number of inputs can result in a combinatorial explosion of possible permutations. In Cucumber we see this problem in Scenario Outlines where we can have a large number of rows for the Examples table. We want to reduce the combinations to a more manageable… Read More »
Being a manual software testing resource, like many others I have lived the past few years under the constant fear of my job being taken over by the hype of “Automation”. I have worked in domains ranging from telecom, hospitality and retail and have mostly followed the principles of old school manual testing for… Read More »
Performance testing is a particularly common question in our experience with our clients and prospects. We have encountered situations where understanding what constituted good performance was not clear at the beginning of a test effort. Benchmarking web services usually involved simulating lots of users and sending lots of messages to simulate a heavy production situation…. Read More »
If you’re a software tester who’s been in the field for a few years, you may have found yourself in one of the following situations: You’re working as hard as you can to find bugs in a huge system and you can’t get to everything within the deadline. You’ve already stumbled across some good bugs,… Read More »
Main Types of Software Testing Software test cases are software codes that are executed based on the input provided by the clients. Once the required output is got, the module is said to be compliant with client requirements. Software developers follow three main types of testing – the black box testing, grey box and white… Read More »
Choosing a Testing Methodology Testing methodologies are approaches to testing, from unit testing through system testing and beyond. There is no formally recognized body of testing methodologies, and very rarely will you ever find a unified set of definitions. But here are some common methodologies: Unit testing The act of testing software at the… Read More »
Article by: Amir Ghahrai
It is a common practice that when a defect is fixed, two forms of testing are done on the fixed code. The first is confirmation testing to verify that the fix has actually fixed the defect and the second is a regression test to ensure that the fix itself, hasn’t broken any existing functionality. It is important to note that the same principle applies when a new
Article by: Oliver Tuschling
The main reason of reviewing test cases: increase test cases quality and therefore product quality.
As we know testers are involved (should be involved) on the Requirements Specification review process to provide the SQA knowledge to the requirements written. As testers are involved on the process they become experts on the area and on the application functionality and many times their knowledge helps avoid introducing future defects into
What is Data and Database Integrity Testing?
Data integrity and database integrity test techniques verify that data is being stored by the system in a manner where the data is not compromised by updating, restoration, or retrieval processing. This type of testing is intended to uncover design flaws that may result in data corruption, unauthorized data access, lack of data integrity across multiple tables, and lack of adequate transaction performance (Dustin
What is a White Box Testing Strategy?
White box testing strategy deals with the internal logic and structure of the code. White box testing is also called as glass, structural, open box or clear box testing. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths, statements and internal logic of the code etc.
In order to implement white box testing, the tester has