Tester's Musings

  my answer: i use it where it matters (removing unwanted background from an image, creating voice over from text).  for testing, the current status of AI seems way too low, i haven't considered it as a partner just yet (but i'm open to be enlightened;)

 Bug Report1 (pers template) .pic (issue vs expected):  ..STR:  ..expected: ..attachments: (scene,json,etc) .vid (issue @ time, @time, vs expected): ..expected: ..attachments: (scene,json,etc) ================== .affected: ..BUILD_VER ...( Windows Native (KB/Touch), Webgl(KB/Touch), iPad, Android, portal, CLI ) .n/a, not affected: ..BUILD_VER ...( Windows Native (KB/Touch), Webgl(KB/Touch), iPad, Android, portal, CLI ) .untested, might also occur in: ..BUILD_VER ...( Windows Native (KB/Touch), Webgl(KB/Touch), iPad, Android, portal, CLI ) for fixing / triage: .Blocker,Critical,Major,Minor .Reason:

================ Test Report --------------------------- Product info: (what is it we are testing? ; complete info) Product Eval: (what can it do ; can't do ; suitable for what ; product claims vs product capabilities) Test_Map, Results: + behaviours, - behaviours, AssocRisks -- in table form Supporting_Artefacts(evidences[vids,pics,files,urls,etc])