69,998. BUY WITH CONFIDENCE Get the keys to the new Porsche sports car you've always wanted or bring your car in for professional Porsche service you can trust by visiting Herb Chambers Porsche. As a Herb Chambers Company, our Porsche dealership in Boston, MA, will always go the extra mile to ensure that you're treated to a first-class experience. Whether you're shopping for a new Porsche or have Porsche financing questions, you'll be welcomed into the Herb Chambers family with open arms! KEY FEATURES INCLUDE Leather Seats, Navigation, All Wheel Drive, Power Liftgate, Rear Air. I cant say enough about my wonderful experience buying my 1st Porsche Cayenne from my salesman, Vito. He was extremely knowledgeable and thorough. He was beyond accommodating since I live on Cape Cod, he met me in Hingam to sign the paperwork to save me a trip to the city! That is a true professional! I absolutely love my 2018 Cayenne and have no doubt there will be others purchased from him in the future!
In my view- In any Service related profession, more than anything else, the overall Value should always be upwardly mobile. Value from the testing group as such is perceived differently by different people who we work with and provide our Services. Testing (can be) for Discovery, pinpointing, Locating, determining significance, repairing, troubleshooting and testing to learn. As I mentioned in the beginning, the above description represents and close to Ideal world situation. Is it really possible to have the clear distinction between pinpointing and testing? I think No, its not possible to create that distinction especially when we consider the product from a black-box perspective. If we do White-box testing, it is possible to have some sort of clear distinction. I think more or less every good bug report has some level of Troubleshooting done. But 鈥渟ome level of troubleshooting鈥?is often not as accurate as 鈥減inpointing鈥? Pinpointing just helps the developer to reach the faulty lines of code, identify the problem and fix it.
Apparently, in a product with millions of lines of code reaching that faulty line of code is a very tedious job (sometimes a mystery!). If a tester helps a developer do that, then we have a delighted customer (i.e. if at all we treat him/her as a customer. From test perspective, it is again the amount of cost we are willing to spend to reach this level of delight. Again, it leads to the eternal question- 鈥渨hat is our mission鈥? In short, it is not possible to have that clear distinction between pinpointing and testing in our kind of test setup. Does the time-limit heuristic usually work always ? Gerald Weinberg also talks about Time-limit heuristic. According to this, the test team member sets a time limit and communicate to the Development team on how much time can they spend on the Development specific investigation. Beyond this time, the onus is on the Development team to figure out.
Since this is a heuristic and not a rule, its quite hard to define the time-limit. Only way it can work is if we make it as a rule i.e. Test team would not spend more than 1 man-day or whatever is the limit and track it accordingly. Doing so (without prior agreement) , will cause some grim repercussions including the relations with Development team. Having said this, testers don鈥檛 have endless time at their disposal. So, till the time there are a formal guidelines around this, it's good to make the Development team (requesting the pinpointing Service) aware of the extent we can help without causing the Testing schedule in Jeopardy. If the bug is reproducible, to what extent should the test team help the dev pinpoint the bug? The greater degree of conflict (regarding pinpointing) between Dev and Test arises when the bug is reproducible 100% of time. Ideally, the Dev should Investigate, debug and figure out where the bug is in the code with some help from Test team. If the bug is non-reproducible then there is even finer distinction between Bug detecting and bug pinpointing.
No comments:
Post a Comment