Skip to content

Details

Description of the presentation:
A project with:
• 200+ defects
• 1000+ tests
• no clear architecture map
• little knowledge over the product
How can we find the most impacted areas by our developments for a milestone/service? How many tests should we run for each impacted area? If I have an automated test, shall I run a manual also? All these questions resulted in a formula that can provide us with these answers and be a guideline for creating a better test strategy.

About Victor Ionascu:
"Passionate about testing for more than 12 years where I had the chance to experiment with many approaches and fail quite often. The good part of the failure is that you have a lot of things to learn and this helped me to organize better the process around the quality topics. What I like in my job is almost everything, mainly the challenges where you need to align things that at the first glance don't fit at all. The projects that I currently work on are focused on integrating multiple products into a viable solution with a very good level of quality. Extra work I do like to share my experience with good and bad things and to increase awareness of the quality process."

See you at the meetup!
TdT Team

Members are also interested in