TestinGil - Gil Zilberfeld -Agile SW Testing Consultancy, International Keynote Speaker ’s Post

Looking at Top-Level test planning, it looks like it can be a bloated process, that you won't be able to a fit into a sprint cadence. Is it valuable with short periods of development? Yes. And in this video, I'm going through an example of what TLTP looks like in a sprint. https://lnkd.in/ewYgFNqN #Testing #TestPlanning #Automation

Looking at Top-Level test planning, it looks like it can be a bloated process, that you won't be able to a fit into a sprint cadence. Is it valuable with short periods of development? Yes. And in this video, I'm going through an example of what TLTP looks like in a sprint. https://lnkd.in/eAcG456T #Testing #TestPlanning #Automation

Defect/Bug Life Cycle : 1) Any mismatch functionality found in application is calles as Defect or Bug or Issue 2) During test execution test engineer are reporting mis-matches as defects to deveoper through templets are tools like Jira, bug jilla, clear quest etc. Defect traige : Its a kind of meeting for categorizing and prioritizing of defects Resolution Types from Developer End : 1) Accept 2) Reject 3) Duplicate 4) Enhancement 5) Need more information 6) Not reproducible 7) fixed etc.. Defect cascading : Unidentified defect can cause multiple defects.

We've talked about Top-Level test planning, and what content is there to talk about. But then come the constraints. Like deadlines, and resources. And how we should handle them. Watch the video. https://lnkd.in/eMTQgFMT #testing #automation #testautomation #apis #apitesting

Test strategy vs Test plan ............ #TestStrategy #TestPlan #SoftwareTesting #QualityAssurance #TestExecution #TestCoverage #TestManagement #TestAutomation #TestDesign #TestingProcess

We've talked about Top-Level test planning, and what content is there to talk about. But then come the constraints. Like deadlines, and resources. And how we should handle them. Watch the video. https://lnkd.in/e8ujavFB #testing #automation #testautomation #apis #apitesting

Stop adding deliberate wait times into your scripts! One of the primary issues that scripted tests sets out to address is the time it would take to conduct tests without these scripts be greatly reduced. Adding hard-coded wait times into your code only defeats the purpose of automation. The 2-5 seconds that you add here and there will eventually culminate into minutes that had no business in the scripts to begin with. In an ideal agile environment, a pipeline is expected to execute deployment, testing, and integration under an hour of pipeline execution. However, given a scenario where there are quite a volume of tests that have been written, with hardcoded or deliberate waits added, testing alone might span over an hour which forces the use of parallels when there should not be. By extension, your scripts are becoming costly. Why not intuitively wait for that specific event that you need then proceed? Have you ever considered that these hardcoded waits not only elongate test times but also is a major contributor to flakiness? Think about it.

When we're test planning, we can create a very detailed plan. All we need is a lot of information. But we don't have it. And a lot of what we know now, will change later. The more we put into the plan, we'll need to re-work later. So if we look at the math, no planning at all is the less waste we can have. That is true. At first. The problem is that without a top-level plan, everyone runs in their own direction, and the chance that everyone meets at the same point, the right point, is low. What does a top-level test plan include? How do you balance the effort now, with all the things that will change later? There's a webinar for that. Join me on Sep 11th, 10am CET, for the "Top-Level Test Planning". https://lnkd.in/eZXzbPKY #Testing #TestPlanning #Automation

From Chaos to Confidence A Test Engineer’s Game-Changing Strategy Here’s how one engineer turned testing headaches into streamlined success. - ➤ Problem: Inefficient testing caused missed bugs and delays. - ➤ Solution: Automated testing + CI/CD integration. - ➤ Result: 40% faster testing, 98% coverage, on-time releases. Is your testing process holding your team back? Solution See how a simple shift can revolutionize your QA approach. Get the full case study and take the first step toward testing Success. P.S. Don’t let outdated testing slow you down—see what works today.

Your team is now “using test automation”, but somehow the bugs don’t disappear and the team is always one step behind when it comes to testing. One of the reasons for this might be that your developers aren’t involved enough in the quality process. Bringing the team together, and making quality really everybody’s responsibility, starts with having good conversations about what you build, how you build it and how you show your stakeholders it works. In my course I cover techniques to achieve that, from story mapping for clarity to strategies how to overcome resistance for change. Sign up here: https://lnkd.in/eKT4vgww