If you’ve been testing for any length of time, you know that the number of possible test cases is enormous if you try to test all possible combinations of inputs, configuration values, types of data, and so forth. It’s like the mythical monster, the many-headed Hydra, which would sprout two or more new heads for each head that was cut off. Two simple approaches to dealing with combinatorial explosions such as this are equivalence partitioning and boundary value analysis, but those techniques don’t check for interactions between factors. A reasonable, manageable way to test combinations is called pairwise testing, but to do it you’ll need a tool.
In this One Key Idea session, Rex will demonstrate the use of a free tool, ACTS, built by the US NIST and available for download worldwide. We can’t promise to turn you into Hercules, but you will definitely walk away able to slay the combinatorial Hydra.
Agile testing has developed exponentially over the last two decades, with the role of QA continuously transforming. In this episode, Jonathon Wright with Kate Falanga, Associate Director of QA at Code & Theory, to discuss the evolution of the QA role in Agile.
The data environments are gradually growing to become bigger and bigger. According to the recent surveys, the compound annual data growth through the year 2020 will tend to be near about 50 percent per year. With the increasing amount of data, the data sources are also raising. And along with that, the need for businesses to unlock those data and use them for taking critical decisions is even raising.
Software testing is not an easy job. Many complexities may arise during the process. The lack of the essential tool and appropriate manpower can also pose a problem in the software testing process. Especially the software vendors’ advertising tools and financial terms usually invest less in software testing resources.
DevOps testing strategy can be simplified emphasizing more on team effort. It always prioritizes about the best working shift that can be conclusive about the timing and frequency of testing practice by a developer in an automated fashion. Though such radical transformation might not be easy for some testers, things can be made to look smarter through proper strategy.
There are many random perceptions about Artificial Intelligence. Not just perceptions; many people fear as well about losing their job due to artificial intelligence. To be specific, the testing professionals often remain in doubts about whether artificial intelligence will take over the traditional forms of testing jobs. However, the perceptions of such are mere doubts. Watch this Episode.
The method of software production is evolving gradually. How software products are being produced today are not the same as they were being produced some years back. This is an interesting technology era where we are sandwiched between conventional testing and advanced continuous testing.
We are now shifting from the traditional structure of a huge team having centralized QA to an entirely new structure. This new structure involves small, self-contained, and autonomous teams that ship software frequently makes use of Continuous Integration tools for automating and administer their developed environment for minimizing bottlenecks.
Software testing or QA is very crucial in all types of businesses. Mistakes can be sometimes very expensive to cope up with and can yield a huge loss. Hence, effective testing is necessary to check product quality before delivering or marketing. That being said, implementing the right and appropriate testing method is essential.
Choosing the right automation testing tool could be a tough job. At times, choosing the wrong tool could lead to results which are unexpected and unforeseen, besides there being significant technical difficulties in making the tool work in your environment. Situations like these will, at best, set back your test automation efforts and may also sabotage them for some time
The art of software testing is extremely sophisticated and often misunderstood by those who do not engage in software testing. For such ‘non-testers’, these common misconceptions about software testing are often related to how software testing differs from other forms of testing.
Big Data and Analytics testing involve unstructured input data, data formats and types, processing and storage mechanisms as well as software and products that are completely new. This requires new abilities and skills, the building of new toolsets and instrumentations which are beyond the scope of traditional testing.
Mr Niranjan Limbachiya CEO, KiwiQA talked about KiwiQA journey, learning, personal challenges, company values, changes to the organisation, leaders admires, surprising things to know about him, future growth and finally about healthy work-life balance.
You can connect with him on Linkedin.
Manual software testing has been the cornerstone of software testing ever since software testing was set up. All test engineers and software QA staff, developers and programmers test their code manually, at least to some degree. Though it is a critical element of software testing, it is certainly not the be-all and end-all.
Why would it be advisable for you to test your web applications? In what capacity would it be a good idea for you to test your web applications? How to work out a reasonable start-up programming testing system? These are not single answer questions. A few organizations don’t fret over testing by any means, despite the fact that the essential target of any bit of programming is to give smooth running.