Agile teams need project management and project leaders. However, they don’t need title-based management or leadership. Instead, agile teams need everyone to be a leader. Learn what agile leaders do so you can practice your agile leadership.
Continue reading
Starting unit testing can be tough. Many questions, misconceptions, and points of confusion torment the beginner. One of the most common of such doubts revolves around amount. How much is enough? Should I aim for 100% coverage? In today’s post, we’ll help you answer these questions, but not by telling you how much is enough. Instead, we’re sort of doing the opposite. We’ll give you tools to identify how few tests is too few.
Continue reading
Blockchain technology is one of the most discussed topics in technical domains today. Many say that blockchain will disrupt a growing number of industries, and we’re already seeing more and more industries adopt this new technology. By definition, blockchain applications are distributed applications, where part of the code live with the data as smart contracts. That means developers need to test these applications differently. In this article we’ll examine how blockchain applications differ from traditional applications and some best practices for testing them.
Continue reading
Technology moves fast, and it is easy to get change fatigue. You can become an expert in your domain just by sticking around for awhile, but what about the world of technology outside your company? What if you eventually want to work somewhere else that does things completely differently? Here are four ways to not only keep up with what is happening in the rest of the world, but to stay relevant in the testing domain.
Continue reading
HOUSTON – Oct. 5, 2018 – Idera, Inc., parent company of global B2B software productivity brands, today announced the acquisition of Kiuwan, a SaaS solution for measuring and analyzing risk and security in the software development lifecycle. Kiuwan will join Idera, Inc.’s Testing Tools Business, which also includes TestRail and Ranorex Studio.
Continue reading
Teams vary in their opinion on using hardening sprints in scrum. If your team does agree on having one before your release, there may be too much to be done and varied expectations by product owner, testers and developers from it. It may also lead to slacked off work being pushed leading to accumulation of technical debt. Here are some tips on how to optimize the hardening sprint and achieve the maximum quality before release.
Continue reading
How do you feel about your software testing strategy? Is it bulletproof? If you’re anything like the majority of organizations out there, I’m betting that the answer is somewhere between “no” and a cynical, barked laugh. Even if you had the most sophisticated testing practice in the world, you’d probably not feel entirely comfortable. By combining test preparation and your testing strategy, a strategic approach can leave you much better situated. Let’s examine the holes you might have in your current testing strategy, so that you can improve your preparation.
Continue reading
I work as a software tester full time, however not all of my time is spent testing. I split my time among many activities, including meetings, answering emails, sprint reviews and retrospectives, backlog grooming, feature reviews and so on. Several activities other than testing are built into the testing role, and these activities contribute to software development in very important ways. Here are five ways skilled software testers contribute to software development outside of testing.
Continue reading
Service Mesh technologies such as Istio, LinkedD and Conduit are becoming common on the microservice landscape. A Service Mesh is a layer of architecture in the cloud native environment that handles communication between microservices. Working in the cloud has become more prevalent in the world of performance testing, so too will working with service discovery technologies such as the service registry and the service mesh.
Continue reading
Many new-to-agile teams encounter this problem: How do we use test automation when we don’t know what we need for a final tool? Instead of a top-down approach, consider an agile approach to a test automation tool: create a hypothesis, do the smallest work possible to test that hypothesis, and improve the automation bit by bit, over time.
Continue reading