The objective is to support teams to develop products that matter. Value-Driven Development encourages teams to adapt and engage with end-users. The key is to develop products that are actually being used. A working product is useless when it is not being used, a quality product is pointless when it is not being used. Value-driven teams are user and usage orientated teams.
Just when we, as testers, got a handle on what Agile means for us, the landscape changed yet again to a DevOps culture. Words like continuous integration (CI), continuous deployment (CD), and pipelines are now ones we’re hearing on a daily basis. As a tester, I’ll admit, I had no clue of what these words meant, and how was I to change the way I tested to fit within this DevOps culture.
Testing involves two types, one will be functional and the other is the non-functional testing. These types of testing are different – continue reading to learn about both of them.
At the turn of the 19th century, the industrial revolution replaced many manual jobs and that resulted in a better quality of life. At the same time, it also led to the loss of a large number of jobs in the short term. Since then there has been a recurrent fear that technological change will spawn mass unemployment. However, the Artificial Intelligence and Machine Learning revolution, that the world has come to terms with, will be significantly different from the Industrial Revolution.
Are you worried about your organization’s ability to cope up with the complexity of delivering at high velocity with excellent quality in multi-speed IT landscape and hybrid environments? Read some thoughts here about some Quality Engineering paradigms in DevOps world that we, Digital Assurance Services- Tech Mahindra, have implemented successfully with our customers.
In this talk, we will confront misconceptions about what accessibility is and isn’t while taking an interactive look at how to test for usable, accessible and inclusive applications.
Are you tired of spending endless hours maintaining your automated test cases? Do you dread looking at test automation reports because of the tedious tweaks you know you’ll need to make from the latest updates from dev? Has your team lost its faith in test automation?
As automation knocks on the door once again, for many there is a continued fear, when will I be automated away? While manual testing will continue for the foreseeable future, it never hurts to get introduced to the concepts of what might come next as a manual tester! The world of software development and software testing continues to change, and as it does, testing and development come to meet in the contested territory of DevOps.
Since AI driven test generation was first introduced in 2017, much has been learned. Millions of test steps were generated and executed, finding thousands of bugs. We will dig into how the technology works, where it works and doesn’t.
Here is your opportunity to ask any questions to Michael Bolton. Michael is a consulting software tester and testing teacher who helps people solve testing problems that they didn’t realize they could solve.
Focusing on more valuable automation, shifting traditional “right” tasks left, and tailoring refinement to account for more efficient activities are some of the topics we’ll discuss.
