what are the benefits of BPT over the QC template
In Quality Center, If we can reuse a non reusable test script as template test, then what is the need of defining reusable test scripts?What additional functionality does Reusable test scripts add when compared to non reusable test scripts?
Tagging something as a template allows you to easily differentiate in reports real tests from templates.
BPT has a number of advantages over templates. Two of them are
1. An easy path to automation
2. If there are defects in QC/ALM, HP will likely fix them if they are related to BPT but suggest you stop using templates and use BPT if they are related to BPT
When ALM 11.0 came out the client I was at was still using templates and ALM 11.0 had numerous defects relating to templates. Getting HP to fix them was a challenge.
Thanks for the Info.My problem is if I have present a comparative analysis between using a template and moving to a BPT , how can I show advantages at very basic level to people who just know and work with templates and think that reusability is the only advantage of BPT which can be achieved simply by using a template.Would really appreciate if you can elaborate some points in regard.
Have a look through the doco that comes with QC/ALM I'd be suprised if there wasn't something in there that strongly encourages BPT and discourages template use given how insistent HP were that my previous client should be using BPT and not templates and that they'd (HP) really prefer not to bother fixing defects with the template functionality.
At the end of the day though, other than possibly perfomance issues which HP claim to have fixed in later versions (I'm stuck with 9.2 with the current client which hurts), there isn't really that much difference from a manual point of view between templates and components. I don't quite understand why components are frightening to template users. And if there are plans to automate later, a manual component is easy to convert to an automated component but can still be run manually if you really want to. Converting a template to an automated template requires writing a driver script which is a little more work but was a common approach prior to BPT and even still now where there is a reluctance to use BPT. If the team do decide to go with templates though I'm pretty sure that QC provided functionality to convert templates into components anyway.
Hi, thanks for the info could you please add advantages in a built points, no matter it is related to automation or Manual