November 2015 Summaries

The article highlights common pain points faced by Quality Assurance (QA) managers in implementing Agile methodologies and automation tools. Despite efforts to adopt Agile and automate testing, many organizations struggle with resource constraints, company culture, and lack of management buy-in. The two QA managers interviewed, Sue and Brian, shared their experiences with varying degrees of success. They discussed challenges such as security protocols, compliance, and tedious manual testing, which can lead to morale issues. However, they also highlighted successes, including the implementation of automation tools, standardized reporting, and improved communication between teams. Ultimately, the article suggests that effective QA management requires a combination of training, mentorship, and collaboration between developers and QA engineers to foster a culture of quality and innovation.

Merging business process with continuous delivery requires a mindset shift that involves all stakeholders, including managers and executives. The traditional estimate-based approach to project planning is often at odds with the principles of Agile and Continuous Delivery, which emphasize iterative development, frequent releases, and customer feedback. To adopt this new way of working, teams must redefine their scope, prioritize features, and plan incrementally, using techniques such as backlog grooming and story mapping. Effective communication and leadership are crucial to driving this cultural change, which requires training for all team members, including product managers and executives. By embracing the Agile mindset and adopting a Continuous Delivery approach, organizations can overcome common obstacles and achieve greater agility, quality, and customer satisfaction.

The lack of consistency in development environments can lead to disparities between development and production, compromising quality and causing issues with QA teams. Ensuring consistent environments improves code quality, reduces finger-pointing, and boosts team morale. Vagrant has proven effective in building consistent and repeatable local environments by bootstrapping virtual machines within laptops/desktops and leveraging provisioners such as Chef or Puppet for setup and configuration. The combination of Vagrant and Chef ensures repeatability and consistency between local environments, making them disposable and allowing QA engineers to trust functional parity between environments. Task runners like Grunt and Guard can be used to automate unit tests and livereload, while continuous integration servers can call the same unit and browser tests before pushing builds to production.

The mobile revolution is a rapidly growing phenomenon with 85% of millennials owning smartphones. A well-planned mobile testing strategy is crucial to ensure high-quality app releases, as it influences elements such as simplicity, user understanding, performance, functionality, and shareability. A great mobile app should prioritize simplicity, know its users, handle loads efficiently, maintain a fast response time, and avoid common bugs like rotating screen issues. Testing methods, including unit tests, monkey testing, load testing, functional user interaction tests, and visual tests, are essential to identify and resolve problems before releasing the app in the wild. With rapid mobile landscape changes, regular evaluation of testing approaches is vital to ensure confidence in app releases.

Using Metrics to Discover Testing Holes` Metrics can help discover testing holes by providing valuable data on bug tracking tools. By analyzing metrics such as the source of bug tickets, it's possible to identify areas where change is needed and understand what tests are effective. Bug tickets can be triggered at various stages of a feature's development lifecycle, including automated scripts, design audits, smoke tests, and exploratory tests. A well-implemented bug tracking tool with fields like Issue Source can help track these metrics and provide insights into the effectiveness of testing practices. By using metrics, teams can determine if new processes are successful and make data-driven decisions to improve their testing strategies.

The author of the text views evangelizing quality as sharing knowledge and expertise to improve quality, rather than a traditional preaching approach. They suggest that negative experiences can trigger a focus on quality, and provide various methods to get people to think more about it, such as customer feedback, metrics, retrospectives, being vocal, competitive, and part of the solution. The author highlights two key factors in improving quality: small user stories and developing to the test. They emphasize that building a culture of quality and sharing ideas through writing, emailing, or talking to others can lead to change and improvement.