Development and quality assurance teams are under strict deadlines to send out deliverables and complete other tasks within a sprint. As these timeframes continue to tighten, it’s important for teams to effectively use agile testing methodologies… More
While compiling our September 2016 issue of LogiGear Magazine, we felt that we had so much content for SMAC that it was too much to keep for just one issue. Consequently, we had our December issue also focus on SMAC and decided to run a special edition this January that focuses solely on trends. In our ten year history, this is our first trends issue and you won’t want to miss it, so stay tuned!
Testing an application – whether it is designed for desktop, mobile or the Internet of Things – for security defects is more important now than ever before. This is because the stakes for a data breach have become enormous, in light of the average incident now costing the affected enterprise over $4 million to recover from.
In business, when you have more revenue flowing in than money going out, it’s a general marker of success. This is a fairly straightforward measurement to follow, but not all initiatives are this simple to monitor. The agile development process is a significant change from traditional workflows and has more fluid expectations. Although agile testing methodologies and development practices have made names for themselves, many organizations are unsure how to gauge their effectiveness. Let’s take a closer look at how to evaluate your agile practices and ensure you’re maximizing their potential advantages.
With DevOps, automated tests have become a crucial necessity. Tests need to be thorough, and their automation should be stable. In fact, tests have to meet quality and robustness criteria that are similar to the application under test, but tests seldom get the attention and investments that the applications get. Where sources and components of applications are considered products that are designed and developed, tests play a mere supporting role. In Scrum projects you will not see tests specified in the backlog. Rather, they are seen as a part of the production for the user stories.