Saturday, September 4, 2010

While tomato came out, green chili did not.

This post has investigation report on probable cause of problem I witnessed in restaurants with sauce container. The report can be found here. Oracles and Heuristics used to learn probable cause of problem are:
  • Tomato sauce container.
  • Tomato sauce.
  • Size of sauce container's knob.
  • Air circulated around sauce container.
  • Warm water.
  • Allowing blocking contents to dry and time.
  • Dried and wet sauce content.


  1. Hey

    U took 8 months to make this document public? Chap I adore your strengths and the way you swam last 10 months. Between continue your writing.

    Pradad B

  2. @Prasad,

    Yes I took 8 months. Working on few things is making to keep all writings in draft.


  3. Ravi,

    You curiosity is getting strong every time since I saw you. Did you provide any solution for the sauce bottle problem?


  4. @Bill,

    No. I did not.Myself was able to refute all my conjectures, in several ways.

    Finding how I can fail or how I can go wrong with my observations & inferences, saw several scenarios where I can fail.


  5. LOL!

    Where did you assure quality from testing story you told?

    I don't see you saying what to be done for fixing problems. For this you tested and wasted my time to read complete document. Funny!!

  6. @Anonymous

    Thanks for lovely comment. I liked it. Probably one of the good comments I have got. Hopefully, I know who are you; may be I'm wrong if you are not the one who I think you are.

    Question: Where did you assure quality from testing story you told?

    Me: Would like to know what you understand for below is same for what I have understood till now. May be what I have understood can change if I come to know, it can be different in some other contexts which I have not thought of yet.

    a) What is testing? Who is a tester?
    b) Why testing is done? Why testing should not be done?
    c) For whom testing is done? What is expected from testing by person(s) who asked for testing?
    d) Do tester have authority to change whatever (s)he wishes from testing result?
    e) What is quality? Who expects quality? How they expect quality? When do they expect quality? Does anybody exist who does not want quality? Why they expect quality? Who can give quality? Who cannot give quality? Who can assure quality? Who cannot assure quality? What happens if over quality is given? What happens if under quality is given? What happens if no quality is given? What happens if it is hard to understand for person(s), whether the quality exist or not? Is assuring quality making a decision? Who can make a decision and what all can have influence on making a decision?

    Make minimum 15 points in favor and against the questions asked above. If possible to make more than 15 points go ahead and do it. Try to find when each of the points you wrote can work and cannot work. And write them as comment. I'm eager to read them.

    Question: I don't see you saying what to be done for fixing problems.

    Me: I leaned every fix is a way for new fix. I was able to find myself that fix what I thought of, will not work in several ways. More importantly I believe, my job as tester will be more focused on informing (probable/potential) concerns to stakeholders rather than just making suggestions or recommendations. I'm not decision maker of business, but testing information can have influence on business.

    Anonymous: For this you tested and wasted my time to read complete document. Funny!!

    Me: You came to know now that you should not invest more time on any other writing of me. Hope you will not do it again. Interestingly, you discovered something about your interests which you do not know yet. As said earlier, I liked your comment.


  7. Questions sucks. Don't ask them.

    Quality is no error in software application.

  8. @Anonymous

    I do not know are you the same anonymous who commented earlier in this post.

    If "Quality is no error in software application", then what is quality in non-software systems? 'Systems' here means that is not a computer or programmed machines alone. It can be any systems you are in or not and using it or not using it. You are also one system in several other systems.

    Anonymous statement: "Quality is no error in software application"

    1) What is an 'error'?
    2) When you call anything as an 'error'?
    3) Define 'error' in minimum of 5 different ways. Try to prove that you are wrong in all the five defined ways.
    4) Who caused 'error'? What can cause 'error'? How you can identify 'error'? How you cannot identify an 'error'?
    5) Error to you is an error for other person? Or an error for other person is an error for you?
    6) Does error have different types in it? Who classified them? How did they classify them? What made them to classify? Do you agree with those classifications?
    7) Why you expect always error free systems?
    8) Does human body is error free systems? If yes, can you count those human? If no can you count them and classify such persons?
    9) Do you find an error moves by your favorite sport star? Do you find an error moves by other people favorite sport star?
    10) Do you identify the best moves by your or others favorite sport star? Does that moves will work in all case of their games?
    11) Who made/makes the error? Is it user or systems?
    12) Is there any difference between 'error', 'failure', 'fault', 'bug', 'defect', 'problem'? Will all these affect the 'quality' you said?

    a) Who defined this for quality?
    b) What else can be thought of for quality?
    c) Quality for whom and from whom?
    d) How do you know you have got quality or you have given quality? How do you know you have not got quality or have not given quality?
    e) What are the ways in which quality can be given? What are the ways in which quality cannot be given?
    f) Is quality measurable? What is the maximum measurable scale and minimum measurable scale and units for quality? As you said 'no error', looks like you should be able to help me in telling how to measure.
    g) Will quality remain same for all time? Will all like same quality?
    h) Does anybody exist who never satisfies with quality they get? Does any boy exist who are happy with no quality available?
    i) Is quality just delivering? Or is it beyond just delivering and forgetting?
    j) Does quality means guarantee or assuring or promising or supporting or negotiating or escalating or surviving or no problem for ever?
    k) What is the quality in you? How do you measure it as you say 'no error'?
    l) Do you get quality without asking or questioning for it? Did you not question before saying 'questions sucks'?
    m) Is quality 'anonymous' (like your name here) or 'onymous'?
    n) Think of your favorite sport start having high qualities (you said). Does she or he did not do any errors in their sport? Still you believe they have high quality in their sporting skill beside their errors in game, why?
    o) Who can decide quality level? Who can make quality? Who cannot decide quality? Who cannot make quality?
    p) How will you understand there is a quality problem? What are the ways in how you cannot understand quality problem?
    q) For whom the quality is?
    r) List as many possible names in which you find quality. How did you know there were of quality TO YOU?
    s) List as many possible names in which you will not find or not found quality. How did you know there was no quality TO YOU?
    t) How does one complain about quality? How do one do not complain about quality?
    u) Who will listen to the quality problem and take decision?
    v) What all quality will comprise of?

    Hope you will come back.


  9. Yoyo hahahaha. you are amazing at variations and that is why I come back. by the way did you know who Iam. LOL!


Please, do write your comment on the read information. Thank you.