Currently I am working with QC 9. I am looking for information on one of its component called business process Testing which we are looking forward to use in future.
I tried to search for it but could not get enough information.
- What can be done using this component ?
- Is it benefecial to have this component?
- Who are the users of this product - business users, QA group etc?
- What features does it add to QC ?
Kindly point me to the thread if this is already discussed.
I tried getting more information around BPT to explain a business partner and I also could not fing anything useful...
In any case, a very short explanation about the BPT module is as follows:
The BPT approach is in theory a solution that should "let non-technical users create automation".
The whole idea is to create reusable components like lego blocks that non-technical users will then take and create business process of business flows that will test the application.
In practice I like it more as a more structured way of automating, by making me create reusable components that should then work in conjunction with other components via the defined parameters and the ability to create loops in the flows.
Now, concretely for your questions:
- The module in QC allows you to create automated and manual tests, but the emphasis is on automation.
- The structured use of reusable components is the most valuable part of the feature. It makes you feel more efficiently on what you want to test and how.
In theory it is the way to give automation tools to BusUsers but this will depend on your BusUsers, for sure it helps the QA and it requires the hard work of your automation team (assuming you work with automation).
- It gives you full modularity in creating your tests and reusing components in them. A very good methodological feature.
The module has great potential but it also lacks some features to make it more complete, like other abstraction levels for components and tests.
My advice to you is to get your hands dirty and work with it for a couple of hours following the examples provided by HP. It is intuitive enough for people with a testing background.
Good Luck (and I hope I didn't bore you to dead with the long answer... [img]/images/graemlins/grin.gif[/img])
In our organization we are positioning it as the bridge between our more technical (coding) testers and our non-coding testers. This should allow us to expand our automation capabilities and resources from the small group that uses it now to a cross-testing area capability.
What BPT allows us to do is to have a "basic tester" submit a request for functionality that they use repeatedly, then the "technical tester" creates a business component script for that scenario. Once they have completed the scenario the "basic tester" is then able to drag-and-drop the scenario(s) created into an automation test set for a particular piece of functionality.
Seems to be going well, the main thing missing at this stage is version control, meaning that a component has to be taken "out of service" for updating. Hopefully the next version of QC has internal version control to resolve this issue.