Topic: test & qa
One of the biggest myths in the world of agile development is that there is not enough time to do security testing. Sanjay Zalavadia shows you the most efficient and cost-effective way of performing security testing in an agile environment: by rolling it into each sprint incrementally, from day one.
Large companies have long used bug bounty programs to find vulnerabilities in their software, but these initiatives are becoming increasingly common among individual developers, too. Should a small business use a bug bounty program? And could it even replace their in-house testing? Should it?
We often attribute project delays to internal reasons, such as poor management, lack of collaboration, resource issues, and software quality, but there are often reasons that fall outside of the norm. Rajini Padmanaban provides some examples of these types of project delays and how to manage them.
The conventional approach to software automation for quality creates a losing situation for the people doing the work. When tests are reliable or take more time than first estimated, management and the rest of the team lose confidence. How can you produce consistently quick, quality information?
The misunderstanding that automation for software quality is just doing what humans do (i.e., manual testing), but faster and more often, causes business risk. Unless you’re very clear, the quality measure is incomplete. The word automation distracts from the real value: measuring quality.
Software companies are increasingly acknowledging the skills people with autism spectrum disorders bring to the workplace. These people are typically very detail-orientated and not bored by taking on repetitive tasks with a great level of precision, which makes them ideal candidates for testing.
As organizations embrace agile, requirements become a challenge because they must be considered and validated in each (short) sprint. Ideally, nonfunctional requirements should be a continuous focus throughout the project. Here are some ways to better address NFRs in an agile development lifecycle.
On one hand, testers have to keep their heads down while working to meet tight schedules. But on the other, technology is advancing at a rapid pace, and testers have to ensure they are not lagging in their skills. Testers need to constantly strike a balance between these demands to stay challenged.
In an attempt at streamlining, over the years the role of tester has changed. In some cases it's been downright eliminated, replaced by automated acceptance checks and unit tests that run constantly. The state of the traditional tester role is in flux, so it’s time to take a fresh look at testing.
The role of software testing and quality assurance is becoming increasingly important in a DevOps setup. This position has undergone a lot of change in the testing practices used, tools leveraged, and the shift in skill set and mindset of practitioners, and testers have a lot to learn from DevOps.