Plato wrote that “necessity is the mother of invention.” This still holds true today as developers, engineers and testers need their ever-growing test cases to be automated. They need to be testing every day, multiple times a day with a variety of tests: smoke, regression, functional, user acceptance, etc. Because of the sheer volume of test cases and device permutations, a DIY lab just can’t handle the load and, as a consequence, more organizations
This week, we’re celebrating being named open-source quality assurance and testing services vendor of the year at the QA Vector Awards 2018 for our work with Rabobank. There is no shortage of honors for the IT industry, but as the only awards dedicated to software quality assurance, testing and delivery at banks, the QA Vector Awards highlight some the most important QA challenges for financial services organizations, and helps show how they can be overcome. Our win recognizes the innovation and excellence of Perfecto’s continuous testing suite and its crucial role in helping Rabobank meet the quality assurance needs which came with an ambitious digital transformation project.
If you’ve been following the meteoric rise of Snapchat since 2012 - or their subsequent drop-off after their app overhaul - you’ve seen a young, disruptive company experience some growing pains. A leaked 6000-word, internal memo from its CEO, Evan Spiegel, offers some frank and straightforward insights into difficulties which were caused by the company’s app redesign. According to TechCrunch, a humble Spiegel admitted to impatient strategic moves. Perhaps taking a page out of
Exciting things are happening here at Perfecto! Today we announced the upcoming release of our second book, Continuous Testing for DevOps Professionals. Debuting next week at Jenkins World | DevOps World, and spearheaded by Perfecto’s own Eran Kinsbruner, we collaborated with the best and brightest in the industry to provide in-depth guidance on implementing and sustaining continuous testing (CT) across the DevOps pipeline, how to address testing challenges, and offered insight into preparing for the future of testing. All profits from the sale of the book will be donated to Code.org, a nonprofit dedicated to expanding access to computer science in schools and increasing participation by women and underrepresented minorities.
The CT recipe: people, process, technology No matter where you work, you're probably already using some type of agile method. However, recent research has shown that maturing from agile to DevOps is easier said than done. It turns out that one of the biggest stumbling blocks for implementing DevOps is the lack of Continuous Testing (CT). Without CT, Continuous Integration and Continuous Delivery simply can't work. Given that a large majority of organizations are struggling with their CT strategies, we thought it would be a good idea to step back, take a deep breath, and demystify the process of creating successful CT by offering a few high-level best practices to follow.
When planning for a continuous testing strategy, leadership should have a comprehensive plan for all teams and individuals. The more you tailor each of these aspects to fit your organization, the more likely you are to succeed in your continuous testing efforts. 1. Number of projects and their type (mobile, web, responsive web, progressive web, etc.) Do you have parallel development teams? A team for native, web/mobile? A team to maintain test code? WIth the never ending number of device and browser permutations, there’s a lot of code to maintain just to keep your current features and user experience functioning properly across all platforms.
Perfecto’s DigitalZoom™ Adds Support for Software Version Control with tools to speed up DevOps processes
How do you keep track of all the moving parts of Continuous Testing? Source Code, Test Scripts, logs, visuals, and other artifacts are created and collected during the all-encompassing processes of Continuous Testing throughout the DevOps pipeline. The amount of test data and number of artifacts are constantly growing and at the same time require traceability. We at Perfecto, see digital enterprises asking a key, fundamental question: How do we optimize testing activities in order to identify and fix issues as early as possible in the SDLC?