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.
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.
The ultimate goal of a DevOps approach is to deliver high-quality features to your customers at the pace they need. High performing DevOps shops point to continuous testing and test automation as key contributors to their success.
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.
The world of testing is always evolving – software development life-cycles, delivery models and team culture. We see this evolution affecting the way teams are constructed, what skill-sets are required, and the ownership of quality within the organization.
Join our STP Community Webinar host, Smita Mishra, as she leads this panel discussion with Theresa Neate and Hilary Weaver-Robb. These seasoned Testing Professionals will discuss their experiences with testing, development, and a leadership perspective in a DevOps world. They will also discuss how testing has evolved, and the types of testing they are focusing on now.
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.
You will leave this session ready to provide clear leadership in test management and quality management and to help your organization achieve successful testing and quality.
In this webinar, Rex will explain the evaluation guidelines and how to apply them to your organization. You’ll come away ready to get started on bottom-line focused, data-driven improvements to your testing processes.
This webinar will give attendees an overview of the significant test strategies in use by testers in various industries and business domains around the world. We’ll examine: analytical strategies (where testers analyze requirements or risks to identify the test conditions to cover); model-based strategies (where testers develop a model of the environment in which the system exists, the inputs and conditions to which the system is subjected, and how the system should behave); methodical strategies (where testers use a predetermined set of test conditions, such as a quality standard or set of heuristics); process-compliant strategies (where testers follow a set of processes defined by others, such as Agile testing); reactive strategies (where testers react to the actual system under test rather than trying to pre-plan the testing); and, other strategies in common use.