| || |
This is not a Certify (Worksoft) apology, but….
I was asked to evaluate Certify but was not given all the details about how we came into contact with Certify or even why we are looking at a new tool.
I was told this would front-end SilkTest and we can use Certify’s mainframe piece and Segue’s web piece, this is not true. This lead to the first problem with the helpdesk, “Who are you?” and “What are you trying to do?”, this gave their helpdesk a low rating only because I was given inaccurate information.
Now that I have a contact at Certify and can get my questions answered and have even participated in some web-interactive sessions. I was asked to give a demo to a functional team that would like to use this tool, in what it can do for them.
I wish to state that Certify’s benefit, as a non-technical testing tool will be very useful for a non-technical team. Now that I (slightly) know how to use the tool I see it is very user friendly. I also see that functional team members will be able to generate there own test scripts and even maintain and update them very easy. Looking at the tool from a functional side I see the benefit of not waiting for the testing team to test when they can start now.
I have been informed that you can enhance the functionality of the tool but I will wait until training. Being a programmer I don’t like options in a list box I like to make up my own options.
I know this sounds like an apology but I really do use the work ‘junk’ all the time, I did not mean the company, or even the software. I was given the limited time to look at a new tool with no training, that is what prompted my frustration.
I do look forward to a relationship with Worksoft,
Re: This is not a Certify (Worksoft) apology, but….
This was last year... how did it work out?