Awesome!!I'm already creating my test project to get familiar with all the features...
i cant access test anylytics. can you please help me?
Great was really looking forward to this day!Was already building an ACC excel version based on the presentations...
Thanks for sharing the great tool. I will give a try.
how to import the test details? iam not clear
How large a product does this get used on? Yes, I know that google has some big products, but how big and complex is this tool used on?How does this relate to requirements, or is this intended to supplement requirements?Crazy question, but is this something that could be run inside a companies firewall instead of on Google App Engine?
I like this idea because it looks like it will make developing a rich coverage list fast. And the summary/reporting information you can generate looks useful too. And no long paragraphs are required.Where do you deal with issues like;- what test data will be needed- what test equipment will be needed e.g. mobile handsets, TV's, browser combos- estimates of how long testing will take- what you need to do to put together an integrated test environment - say you have legacy systems you need to integrate with etcWould you deal with these issues in another document?
Do you have any documentation on how to deploy this code to a tomcat installation or to your own appspot? What configuration or manual work is needed?
I strongly agree that traditional way to create test plan is a big waste of testing resource. The best usage of that is help tester to thinking about test cases in a structured way. In terms of increasing test coverage, an aftermath test case review works better than reviewing a plan that not really last (due to the consistent spec changes through the developing process).However, the breakdown of the attributes here appeared really arbitrary to me. How we ensure the breakdown is logical and efficient is a big question. That is an inevitable problem when we are planing our test efforts. I do not really understand the risk part. The association of actual test cases to the matrix is kind of questionable in lots of cases. And how many test cases should we run to gain enough confidence for a box in the matrix is also vague. It is more like another nice looking "Fake" test coverage representation to me.But nevertheless. I think it is a nice tool.
In James Whittaker webinar More Bang For Your Testing Buck you can see alot of cool graphs used in "Testify". Why is that not included in Google Test Analytics?
Me thinks, well er .. can it be? Say it not so. Even some at Google have gotten RISK wrong. Risk is: Likelihood times Consequence. Independent of each other. And independent of mitigation and test plans. As presented here, "Risk" appears to be more like a combination of "Likelihood" reduced by testing. It is a very common mistake; e.g: flying is less risky than driving. What the ACC needs is a third axis or quantifier for "Consequence", which can help prioritize the test plans. Just my humble 2c since every organization outside of NASA seems to have their own way of defining and managing Risk.
Awesome.Thanks for sharing
All the images are broken! Could you guys fix it?
Image links are busted
The images in the post appear to be broken. Cheers.
Thanks, the images are now fixed.
Nice information & with updated images it looks nice & more informative.
May anybody explain me how can I export data from Test Analytics?
The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.