As an advocate for quality, you look at the product, take into account time, budget, and other business constraints, and recommend fixes to ship a product with the best possible quality. ... And the businesspeople in production don’t want to fix it. How can you communicate bugs and risk to people who don't want to listen? Instead of getting frustrated, you need to frame issues in a meaningful way—and, if you have to, let people fail.
Most modern testing, especially in a DevOps model, uses a lot of telemetry to evaluate and monitor quality of experience for apps and services. In this interconnected world, there is power and risk in data. Ken Johnston will share his personal experiences dealing with US and European Union privacy regulations and the methods he and his team have implemented to mitigate the potential of significant penalties for the misuse of data. He will cover privacy-preserving techniques such as differential privacy and private enclave, what constitutes primary versus secondary uses of data, and how you should handle personally identifiable information (PII). You'll leave with a better understanding of how to keep data private and secured, as well as how to keep your team adhering to privacy best practices and regulations.
I'm currently building out a Test PMO for an insurance company. We have a long term, fixed-price contract with a vendor using a waterfall model. I'm currently working on KPIs and metrics which I will use to tell the testing story, which means both technical and business comsumers will need to find value in them. I'm conducting targeted interviews atm but am interested in hearing if any of you have had experience in this arena.
What kinds KPIs / metrics have you found valuable?
What kinds of chatring / mapping have you found to be confusing?
There are a lot of advantages to behavior-driven development, but there are also a lot of challenges you can encounter during the implementation. Knowing is half the battle, so be aware of these eleven common stumbling blocks to BDD adoption and outline plans to mitigate them beforehand, and you’ll be able to start reaping the benefits of BDD sooner.
Testing has changed a lot in the last ten years. Although some traditional techniques are still useful, many testing activities are being done by developers, users, and other nonprofessional testers. Consequently, the role of test manager has changed into more of a test assurance officer and coach. The way this new role is implemented can differ from situation to situation. Here’s how it can be useful.
Serverless cloud applications are rapidly moving into the mainstream. In this model, teams focus on developing and deploying code on a known technology stack and runtime, with fixed interfaces for application, database, and network.
A test manager has to perform in multiple dimensions, using a variety of professional and interpersonal skills daily. With all these career facets, there are lots of different areas that can pose a problem. Here are the most common (and most annoying) things a test manager typically hears on a regular basis, as well as some strategies for how to deal with them.
In this interview, Adam Satterfield, director of testing and quality at Anthem, discusses the core components that testers need to understand in order to create a test strategy in an agile environment. He also talks about the need to build better communication skills through active listening. And Adam offers advice on sharing the things you have learned through blogging, writing for sites like the TechWell community sites, or becoming a presenter at a conference, as well as the benefits you can gain from that.