Thanks Curtis! So if I understand this, the methods to determine 'what' the automation is doing are (A) talk to the person that wrote it (B) look at the code / keyword test individually? This seems to be a pretty large gap in functionality. The marketing documents talk about automating manual tests which is a great idea, little did we know the two artifacts know nothing about each other. To answer the support persons question, no this doesn't help. I don't need a fancy cloud solution for the simple task of passing or failing a manual test case when a piece of automation runs. You guys just need to write a plugin which allows automation and testcases to know about each other, AND it needs to update pass / fail information. I'd imagine your devs could make something like that happen pretty quickly. This is pretty disappointing.