The approach to test via comparison of multiple API responses between production and test code versions is very effective and produces the required results, release over release. Improvements and changes, however, are needed to address changing needs. This is true for most if not all tech solutions; the economics principle ‘Law of Diminishing Marginal Utility’ also applies to software. A tech solution that excited stakeholders when first introduced could become stale very soon. A revamp or a new solution is needed to match evolving expectations.
DevOps is the preferred methodology for software development companies looking to code, build, test, and deploy software as a continuous process. It is popular because it creates a fast-paced, results-oriented, collaborative environment that encourages cross-skilling and self-improvement.
In life and in test automation, a lot of things change as you mature—the challenges you face, the types of failures you experience, and the best ways to solve them. Let’s skip the “life lessons” and focus on the test automation angle here
One of my mentors, whom I admire, once told me, "Quality is not only QA's responsibility; everyone- from development engineers to technical architects, to product managers need to share the responsibilities. In a QA role, if you want to be successful, you have to know the right amount of information from everyone and always ask questions." I took my mentor's advice very seriously.
Most software developers are in either the agile or the waterfall camp. Agile is required to be competitive, but many enterprise processes still rely on waterfall practices for stability. They can coexist.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
In this interview, Jennifer Scandariato, the director of test engineering and leader of the Women in Technology initiative at iCIMS, explains the changing role of the manual tester, how they can adapt to a much faster environment, and why security is more important than ever before.
In this interview, Brandon Carlson, a consultant at Lean TECHniques, explains how all the newer aspects of software have come together. He explains how things have changed since agile has grown in prominence and what DevOps does for testing and development.
In this interview, TechWell speaks with Michael Sowers, CIO and senior consultant at TechWell. At STARWEST 2015, he gave a presentation titled "Plan, Architect, and Implement Test Automation within the Lifecycle."
More than two decades ago, Richard P. Gabriel proposed the idea that “Worse Is Better” to explain why some things that are designed to be pure and perfect are eclipsed by solutions that are compromised and imperfect. This is not simply an observation that things should be better but are...
Your organization is embracing agile. When it comes to adopting the process, your team seems to be doing all the right things. Yet deep down, something still doesn’t seem quite right. As their leader, it could be that you haven’t figured it out either. Perhaps your team is lacking some...
Transforming software development across geographic locations in a large company is difficult. But Nationwide Insurance found a way to successfully implement more than forty agile teams in multiple locations around the United States using their internal Application Development Center.
Top web companies employ continuous delivery of software to build and deploy systems faster and gain a marked competitive advantage. You can do it, too! Andy Singleton shares the patterns for testing in real time that result in more frequent and more reliable releases. He explains why...