Megatest

History Of Ticket e738e6ea4ae8088cd8096bc671b1ff3a272999c3
Login

Artifacts Associated With Ticket e738e6ea4ae8088cd8096bc671b1ff3a272999c3

  1. Ticket change [4b68e147e1] (rid 17151) by mrwellan on 2018-05-29 09:53:37:

    1. comment initialized to:
      Hi,
      1) Graphical representation of data will be very useful to increase productive
      2) megatest enhancement which when one runs on a functional area shows graphically checks, fails, pass waivers
      3) Then a deep dive graphical representation
      4) megatest enhancement to show diff graphically mathematically between two different runs or kits (target1 run1 , target2 run2)
      
      3) Kit health
      a. Number of waived test-items to start with. Percentage of waived testitems will be a very basic metric of kit health
      b. We should have infrastructure (some code) which will present us with Kit Health from highest level to lowest level of details for example
      i. At highest level it can give just percentage of waived
      ii. Also it can give diff wrt last kit released and improvement since then in some metric it will be nice
      iii. At lower level if we click on the graphs on waived section it should go into that part in details
      1) e.g. waived should show % wrt tests like icv_lvs icv_drc etc
      2) If we click on icv_drc it should show all tsetcases having issues
      3) Another type of click on icv_drc should also show summary of different failing sub flows
      4) All of above should be quantified
      c. This all should be done all functional areas
      i. Ofcourse many/most factors are different for all areas
      ii. I think we should have a excel sheet where users can input various factors and then use it to build graphs and , quantify results
      iii. Things should be quantified over functional areas and then over the entire kit (maths)
      iv. I think we should have a idea what we are aiming not just in English but numbers and then see where we reach what we miss
      d. Numbers will I guess make more sense over time than English
      
    2. login: "mrwellan"
    3. severity initialized to: "Important"
    4. status initialized to: "Open"
    5. title initialized to: "Enhancement request from Paritosh"
    6. type initialized to: "Feature_Request"
  2. Ticket change [9c5569a971] (rid 17152) by mrwellan on 2018-05-29 09:54:03:

    1. icomment:
      Hi,
      1) Graphical representation of data will be very useful to increase productive
      2) megatest enhancement which when one runs on a functional area shows graphically checks, fails, pass waivers
      3) Then a deep dive graphical representation
      4) megatest enhancement to show diff graphically mathematically between two different runs or kits (target1 run1 , target2 run2)
      
      3) Kit health
      a. Number of waived test-items to start with. Percentage of waived testitems will be a very basic metric of kit health
      b. We should have infrastructure (some code) which will present us with Kit Health from highest level to lowest level of details for example
      i. At highest level it can give just percentage of waived
      ii. Also it can give diff wrt last kit released and improvement since then in some metric it will be nice
      iii. At lower level if we click on the graphs on waived section it should go into that part in details
      1) e.g. waived should show % wrt tests like icv_lvs icv_drc etc
      2) If we click on icv_drc it should show all tsetcases having issues
      3) Another type of click on icv_drc should also show summary of different failing sub flows
      4) All of above should be quantified
      c. This all should be done all functional areas
      i. Ofcourse many/most factors are different for all areas
      ii. I think we should have a excel sheet where users can input various factors and then use it to build graphs and , quantify results
      iii. Things should be quantified over functional areas and then over the entire kit (maths)
      iv. I think we should have a idea what we are aiming not just in English but numbers and then see where we reach what we miss
      d. Numbers will I guess make more sense over time than English
      
    2. login: "mrwellan"
    3. mimetype: "text/plain"
    4. priority changed to: "Immediate"
    5. resolution changed to: "Open"